Linux PARISC architecture development
 help / color / mirror / Atom feed
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 17:18:35 -0400	[thread overview]
Message-ID: <20050716211835.GK5314@systemhalted.org> (raw)
In-Reply-To: <200507162029.j6GKTsGE011108@hiauly1.hia.nrc.ca>

On Sat, Jul 16, 2005 at 04:29:54PM -0400, John David Anglin wrote:
> > Will this ever happen during inlining?
> > 
> > fstd chain -> memory
> > operation 1
> > 			fstd chain -> memory
> > fldd chain -> regs
> > 			operation 2
> > 			fldd chain -> regs
> > 
> > Operation 2 could trap when expected that it couldn't because the fstd
> > had cleared the traps.
> 
> I guess clobbering all the fp registers plus r0 will stop this.

That seems like overkill, I just don't want gcc schedule between the asm
statements. The fstd chain, and fldd chain are always asm statements.

Is there no other way? Clobbering will add huge register pressure and
force gcc to spill all the fpregs and restore after the call.

c.

_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2005-07-16 21:18 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
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 [this message]
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=20050716211835.GK5314@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