Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: linux-mips@linux-mips.org
Subject: Re: [patch] Prevent dead code/data removal with gcc 3.4
Date: Fri, 13 Feb 2004 15:53:16 +0100	[thread overview]
Message-ID: <20040213145316.GA23810@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.55.0402131453360.15042@jurand.ds.pg.gda.pl>

On Fri, Feb 13, 2004 at 03:20:27PM +0100, Maciej W. Rozycki wrote:

> 2. It changes inline-assembly function prologues to be embedded within the
> functions, which makes them a bit safer as they can now explicitly refer
> to the "regs" struct and assures the code won't be removed or reordered.

It is possible that gcc changes one of the registers before save_static
and I can't imagine there's a reliable way to fix this in the inline
version.

  Ralf

  reply	other threads:[~2004-02-13 14:54 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 [this message]
2004-02-13 17:51   ` Jun Sun
2004-02-13 18:35     ` Maciej W. Rozycki
2004-02-13 22:07       ` Ralf Baechle
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=20040213145316.GA23810@linux-mips.org \
    --to=ralf@linux-mips.org \
    --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