mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Jens Gustedt <jens.gustedt@inria.fr>
To: musl@lists.openwall.com
Subject: Re: Re: [Pcc] pcc i386 -fPIC compiler error on src/complex/catanf.c
Date: Sun, 04 Jan 2015 20:26:35 +0100	[thread overview]
Message-ID: <1420399595.19013.7.camel@inria.fr> (raw)
In-Reply-To: <20150104180129.GD4574@brightrain.aerifal.cx>

[-- Attachment #1: Type: text/plain, Size: 1515 bytes --]

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:
> 
> http://git.musl-libc.org/cgit/musl/tree/src/complex/catanf.c?id=v1.1.5

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`.

Jens

-- 
:: INRIA Nancy Grand Est ::: AlGorille ::: ICube/ICPS :::
:: ::::::::::::::: office Strasbourg : +33 368854536   ::
:: :::::::::::::::::::::: gsm France : +33 651400183   ::
:: ::::::::::::::: gsm international : +49 15737185122 ::
:: http://icube-icps.unistra.fr/index.php/Jens_Gustedt ::



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2015-01-04 19:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-04  5:53 Isaac Dunham
2015-01-04 17:47 ` Iain Hibbert
2015-01-04 18:01   ` Re: [Pcc] " Rich Felker
2015-01-04 19:26     ` Jens Gustedt [this message]
2015-01-04 19:24   ` Anders Magnusson
2015-01-04 21:04     ` Isaac Dunham
2015-01-04 21:54       ` Isaac Dunham
2015-01-05 10:31       ` Anders Magnusson
2015-01-05 23:25         ` [Pcc] " Isaac Dunham
2015-01-06  3:27           ` Anders Magnusson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1420399595.19013.7.camel@inria.fr \
    --to=jens.gustedt@inria.fr \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).