From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Jun Sun <jsun@mvista.com>, linux-mips@linux-mips.org
Subject: Re: [patch] Prevent dead code/data removal with gcc 3.4
Date: Fri, 13 Feb 2004 23:07:25 +0100 [thread overview]
Message-ID: <20040213220725.GA31847@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.55.0402131908370.15042@jurand.ds.pg.gda.pl>
On Fri, Feb 13, 2004 at 07:35:01PM +0100, Maciej W. Rozycki wrote:
> If we want to tolerate performance loss, then it's easily doable. That
> can be done with the current setup, with a jump instruction to the
> referred function added at the end and "__attribute__((used))" or perhaps
> "asm("foo")" added to the function declaration.
>
> I can choose this path if we agree on it.
The inline version is fundemantally fragile. The outline version has
problems with getting reordered by later gcc which can be solved by
putting a jump to the C function at the end; the C function also needs
the right __attribute__s so it won't get eleminated by gcc.
Ralf
next prev parent reply other threads:[~2004-02-13 22:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 14:20 [patch] Prevent dead code/data removal with gcc 3.4 Maciej W. Rozycki
2004-02-13 14:53 ` Ralf Baechle
2004-02-13 17:51 ` Jun Sun
2004-02-13 18:35 ` Maciej W. Rozycki
2004-02-13 22:07 ` Ralf Baechle [this message]
2004-02-16 9:18 ` Maciej W. Rozycki
2004-02-13 22:22 ` Thiemo Seufer
2004-02-13 22:35 ` David Daney
2004-02-13 22:50 ` Thiemo Seufer
2004-02-14 1:15 ` Ralf Baechle
2004-02-14 1:22 ` Eric Christopher
2004-02-14 1:28 ` Thiemo Seufer
2004-02-14 1:45 ` Ralf Baechle
2004-02-14 2:17 ` Thiemo Seufer
2004-02-14 6:13 ` Jun Sun
2004-02-14 6:28 ` Thiemo Seufer
2004-02-15 1:44 ` Daniel Jacobowitz
2004-02-17 12:50 ` Maciej W. Rozycki
2004-06-28 13:12 ` Maciej W. Rozycki
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=20040213220725.GA31847@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=jsun@mvista.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
/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