From: Andi Kleen <ak@suse.de>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: jh@suse.cz, echristo@redhat.com, hubicka@ucw.cz,
eager@mvista.com, gcc@gcc.gnu.org, linux-mips@linux-mips.org
Subject: Re: GCC-3.4 reorders asm() with -O2
Date: Sun, 25 Jan 2004 20:28:07 +0100 [thread overview]
Message-ID: <20040125202807.2d786115.ak@suse.de> (raw)
In-Reply-To: <20040125182643.GA25020@linux-mips.org>
On Sun, 25 Jan 2004 19:26:43 +0100
Ralf Baechle <ralf@linux-mips.org> wrote:
> On Sun, Jan 25, 2004 at 12:03:51PM -0500, Daniel Jacobowitz wrote:
>
> > It is. Ralf already knows about the problem, I think - we leave
> > markers outside of functions which define an entry point, save some
> > additional registers to the stack, and try to fall through to the
> > following function. If the function gets emitted elsewhere, obviously,
> > we've lost :)
> >
> > [This is save_static_function...]
>
> I only recently fixed the problem with the save_static() inline function
> which of course was fragile, speculating on the compiler doing the
> right thing ... I'll cook up a fix ...
You can always use __attribute__((noinline))
-Andi
next prev parent reply other threads:[~2004-01-25 19:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4011C72C.613E25@mvista.com>
[not found] ` <20040124011955.GA12040@nevyn.them.org>
[not found] ` <20040124012303.GJ32288@atrey.karlin.mff.cuni.cz>
[not found] ` <20040124050849.GB14951@nevyn.them.org>
[not found] ` <1075009125.3649.0.camel@dzur.sfbay.redhat.com>
[not found] ` <20040125100514.GA8810@kam.mff.cuni.cz>
[not found] ` <20040125164758.79373419.ak@suse.de>
2004-01-25 17:03 ` GCC-3.4 reorders asm() with -O2 Daniel Jacobowitz
2004-01-25 18:26 ` Ralf Baechle
2004-01-25 19:28 ` Andi Kleen [this message]
2004-01-26 8:36 ` Ralf Baechle
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=20040125202807.2d786115.ak@suse.de \
--to=ak@suse.de \
--cc=eager@mvista.com \
--cc=echristo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=jh@suse.cz \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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