Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Kjeld Borch Egevang <kjelde@mips.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Error in gcc version 2.96 20000731
Date: Thu, 13 Sep 2001 08:10:40 -0700	[thread overview]
Message-ID: <20010913081040.A24910@lucon.org> (raw)
In-Reply-To: <3BA0BF6E.2010300@mips.com>; from kjelde@mips.com on Thu, Sep 13, 2001 at 04:15:10PM +0200

On Thu, Sep 13, 2001 at 04:15:10PM +0200, Kjeld Borch Egevang wrote:
> Hi all.
> 
> I discovered an optimization error in the current gcc for MIPS.
> 
> When I compile the code below with -O2 it clears the code-field just 
> after setting it. The instructions are mixed up. It works fine with -O1 
> and -O0.
> 
> If the "//" is removed in front of the first printf, it works too.
> 

The code isn't ISO C. You cannot declare something as short and then
access it as int. On x86:

# gcc alias.c -O
put_code after, code=5 5
gen_rtx, code=5
# gcc alias.c -O2
put_code after, code=5 0
gen_rtx, code=0

On mips,

# gcc alias.c -O
put_code after, code=5 5
gen_rtx, code=5
# gcc alias.c -O2
put_code after, code=5 5
gen_rtx, code=0

You can fix the code or add -fno-strict-aliasing

# gcc alias.c -O2 -fno-strict-aliasing
put_code after, code=5 5
gen_rtx, code=5



H.J.

  reply	other threads:[~2001-09-13 15:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-13 14:15 Error in gcc version 2.96 20000731 Kjeld Borch Egevang
2001-09-13 15:10 ` H . J . Lu [this message]
2001-09-13 21:09   ` Kjeld Borch Egevang
2001-09-13 21:09     ` Kjeld Borch Egevang
2001-09-13 21:14     ` H . J . Lu
2001-09-13 21:22       ` Kjeld Borch Egevang
2001-09-13 21:22         ` Kjeld Borch Egevang
2001-09-13 21:26         ` H . J . Lu
2001-09-13 15:14 ` Maciej W. Rozycki
2001-09-13 15:16   ` H . J . Lu
2001-09-13 20:47   ` Kjeld Borch Egevang
2001-09-13 20:47     ` Kjeld Borch Egevang
2001-09-14 14:42     ` 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=20010913081040.A24910@lucon.org \
    --to=hjl@lucon.org \
    --cc=kjelde@mips.com \
    --cc=linux-mips@oss.sgi.com \
    /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