From: Carlos O'Donell <carlos@systemhalted.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: tausq@debian.org, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: Non-inline math, and inline math broken, GCC to blame? (1 hppa tls toolchain regression).
Date: Sat, 16 Jul 2005 14:38:28 -0400 [thread overview]
Message-ID: <20050716183827.GF5314@systemhalted.org> (raw)
In-Reply-To: <200507160154.j6G1sPI0006203@hiauly1.hia.nrc.ca>
On Fri, Jul 15, 2005 at 09:54:25PM -0400, John David Anglin wrote:
> > I think gcc is to blame, or the constraints in the assembly?
> >
> > --- GCC 4.0 ---
> >
> > 0x40349890 <feclearexcept+0>: ldo 40(sp),sp
> > 0x40349894 <feclearexcept+4>: ldo -38(sp),ret0
> > 0x40349898 <feclearexcept+8>: stw r19,-20(,sp)
> > 0x4034989c <feclearexcept+12>: fstd fr0,0(,ret0)
> > 0x403498a0 <feclearexcept+16>: fldd 0(,ret0),fr0
> > 0x403498a4 <feclearexcept+20>: ldi 0,ret0
> > 0x403498a8 <feclearexcept+24>: bv r0(rp)
> > 0x403498ac <feclearexcept+28>: ldo -40(sp),sp
>
> PR time. Please add danglin@gcc.gnu.org to the CC list.
>
> > Notice that it thinks the argument is on the stack? Are the assembly
> > constraints confusing gcc?
>
> Probably, but its not clear at the moment. I think the asm's need
> the volatile keyword as they have side effects that aren't known to
> gcc (i.e., scheduling might move a floating point operation past
> the asm's should the functions be inlined.
I hadn't considered the effects of rescheduling. I guess this can happen
to any code between the asm statements.
c.
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2005-07-16 18:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-15 14:26 [parisc-linux] TLS toolchain update (6 regressions left) Carlos O'Donell
2005-07-15 23:44 ` [parisc-linux] Non-inline math, and inline math broken, GCC to blame? (1 hppa tls toolchain regression) Carlos O'Donell
2005-07-16 0:08 ` [parisc-linux] " John David Anglin
2005-07-16 0:57 ` Carlos O'Donell
2005-07-16 1:14 ` Carlos O'Donell
2005-07-16 1:54 ` John David Anglin
2005-07-16 18:38 ` Carlos O'Donell [this message]
2005-07-16 19:15 ` John David Anglin
2005-07-16 19:16 ` Carlos O'Donell
2005-07-16 19:48 ` John David Anglin
2005-07-16 20:13 ` Carlos O'Donell
2005-07-16 20:29 ` John David Anglin
2005-07-16 21:18 ` Carlos O'Donell
2005-07-16 22:55 ` John David Anglin
2005-07-17 16:21 ` [parisc-linux] TLS toolchain update (6 regressions left) Carlos O'Donell
[not found] <no.id>
2005-07-16 2:55 ` [parisc-linux] Re: Non-inline math, and inline math broken, GCC to blame? (1 hppa tls toolchain regression) John David Anglin
2005-07-16 16:16 ` Carlos O'Donell
2005-07-16 17:37 ` John David Anglin
2005-07-16 17:54 ` John David Anglin
2005-07-16 19:41 ` Carlos O'Donell
2005-07-16 19:56 ` John David Anglin
2005-07-16 19:15 ` Carlos O'Donell
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=20050716183827.GF5314@systemhalted.org \
--to=carlos@systemhalted.org \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=tausq@debian.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox