Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Greg Lindahl <lindahl@keyresearch.com>
To: MAKE FUN PRANK CALLS <linux-mips@linux-mips.org>
Subject: Re: GCC -O2 failure for mipsel
Date: Thu, 1 May 2003 01:50:18 -0700	[thread overview]
Message-ID: <20030501085018.GA1885@greglaptop.attbi.com> (raw)
In-Reply-To: <16048.57054.224964.883062@cuddles.redhat.com>

On Thu, May 01, 2003 at 09:46:22AM +0100, Andrew Haley wrote:
> Fuxin Zhang writes:
>  >  Thanks, -fno-strict-aliasing works.
>  > --The actual code can't be changed: because it is part of spec cpu2000:)
> 
> Perhaps SPEC need to have ISO C explained to them...

It's just there so you can't turn on aliasing for reasonable base
options. It's all a conspiracy, I tell you...

greg

  reply	other threads:[~2003-05-01  8:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-01  5:39 GCC -O2 failure for mipsel Fuxin Zhang
2003-05-01  8:27 ` Andrew Haley
2003-05-01  8:41   ` Fuxin Zhang
2003-05-01  8:46     ` Andrew Haley
2003-05-01  8:50       ` Greg Lindahl [this message]
2003-05-09  2:05         ` Problem of cross-mipsel-compiler GLIBC-2.3.X smills_ho
2003-05-09  2:05           ` smills_ho
2003-05-09  7:21           ` Eric Christopher
2003-05-09  7:29             ` Kumba
2003-05-09  8:15               ` smills_ho
2003-05-09  8:15                 ` smills_ho
2003-05-09  8:30                 ` Kumba
2003-05-09  9:40                   ` smills_ho
2003-05-09  9:40                     ` smills_ho
2003-05-09 11:20                   ` Guido Guenther
2003-05-09  8:10             ` smills_ho
2003-05-09  8:10               ` smills_ho
2003-05-09 17:13               ` Eric Christopher
2003-05-01 11:00       ` GCC -O2 failure for mipsel Andrew Pinski

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=20030501085018.GA1885@greglaptop.attbi.com \
    --to=lindahl@keyresearch.com \
    --cc=linux-mips@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