From: kevin diggs <diggskevin38@gmail.com>
To: Jeff Kenton <jkenton@tilera.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: hail marry (booting PowerMac 8600)
Date: Wed, 02 Feb 2011 21:06:00 -0000 [thread overview]
Message-ID: <AANLkTinuob168+ebKbf2FY_Aro_aYAyFuhSN11yqdn4k@mail.gmail.com> (raw)
In-Reply-To: <4D49B8C2.3030409@tilera.com>
Hi,
Is that different from -fno-strict-aliasing, which is already being
passed according to the .mesh.o.cmd file from the build system?
kevin
On Wed, Feb 2, 2011 at 2:04 PM, Jeff Kenton <jkenton@tilera.com> wrote:
>
> strict-aliasing? Try building with -fnostrict-aliasing and see if it helps.
>
next prev parent reply other threads:[~2011-02-02 21:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 2:10 kevin diggs
2011-01-22 2:36 ` Ian Lance Taylor
2011-01-25 4:16 ` kevin diggs
2011-02-02 19:41 ` kevin diggs
2011-02-02 20:04 ` Jeff Kenton
2011-02-02 21:06 ` kevin diggs [this message]
2011-02-02 22:07 ` Ian Lance Taylor
2011-02-02 22:23 ` kevin diggs
2011-02-02 22:36 ` Ian Lance Taylor
2011-02-03 0:03 ` kevin diggs
2011-02-03 0:13 ` Ian Lance Taylor
2011-02-03 0:59 ` kevin diggs
2011-02-03 1:58 ` Ian Lance Taylor
2011-02-03 8:39 ` VAUGHAN Jay
2011-02-03 21:10 ` kevin diggs
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=AANLkTinuob168+ebKbf2FY_Aro_aYAyFuhSN11yqdn4k@mail.gmail.com \
--to=diggskevin38@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jkenton@tilera.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).