Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 04 Jan 2015 20:26:35 +0100
From: Jens Gustedt <>
Subject: Re: Re: [Pcc] pcc i386 -fPIC compiler error on

Am Sonntag, den 04.01.2015, 13:01 -0500 schrieb Rich Felker:
> On Sun, Jan 04, 2015 at 05:47:24PM +0000, Iain Hibbert wrote:
> > it will likely be something inside that function that does not show up
> > until the function is being emitted. STCALL is something to do with
> > structure arguments, which some kinds of floating point are big enough to
> > be considered.. so I guess some kind of double or long double arguments?
> I would guess it's treating complex floating point objects like
> structures. However...
> > > I can't really isolate the error in question, I'm afraid.
> > 
> > maybe if you post the function, somebody else would be able to?
> ...the function where the error is reported is not using any complex
> objects:

You are refering to _redupif?

This is a `static` function that is used exactly once. Perhaps the
compiler "augments" it to `float complex` return type, because the
context where it is used is of that type. It would be interesting to
see if the error disappears if the return value is first stored in a
`volatile float`, and only then assigned to `w`.


:: INRIA Nancy Grand Est ::: AlGorille ::: ICube/ICPS :::
:: ::::::::::::::: office Strasbourg : +33 368854536   ::
:: :::::::::::::::::::::: gsm France : +33 651400183   ::
:: ::::::::::::::: gsm international : +49 15737185122 ::
:: ::

Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.