public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jakub@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
pmassimi@ilog.fr, skal@planet-d.net
Subject: Re: optimization/6647: -O2 (or above) invalid optimization
Date: Tue, 14 May 2002 08:11:00 -0000 [thread overview]
Message-ID: <20020514151144.23838.qmail@sources.redhat.com> (raw)
Synopsis: -O2 (or above) invalid optimization
State-Changed-From-To: open->analyzed
State-Changed-By: jakub
State-Changed-When: Tue May 14 08:11:43 2002
State-Changed-Why:
The optimization is valid, the source is not.
The code does illegal type punning, see info gcc on
-fstrict-aliasing for details.
Either rewrite the code using unions, or use -fno-strict-aliasing.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6647
next reply other threads:[~2002-05-14 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 8:11 jakub [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-16 18:56 rth
2002-05-13 8:26 skal
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=20020514151144.23838.qmail@sources.redhat.com \
--to=jakub@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
--cc=pmassimi@ilog.fr \
--cc=skal@planet-d.net \
/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).