public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ebotcazou@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gennadi.f@corigin.com, nobody@gcc.gnu.org Subject: Re: c/9902: optimization level -O2/3 doesn't work correctly. Date: Fri, 14 Mar 2003 15:48:00 -0000 [thread overview] Message-ID: <20030314154830.25610.qmail@sources.redhat.com> (raw) Synopsis: optimization level -O2/3 doesn't work correctly. State-Changed-From-To: open->closed State-Changed-By: ebotcazou State-Changed-When: Fri Mar 14 15:48:30 2003 State-Changed-Why: Not a bug. Your code breaks the ISO C aliasing rules. GCC automatically turns on -fstrict-aliasing at -O2 so you need to fix your code or compile it with -fno-strict-aliasing. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9902
next reply other threads:[~2003-03-14 15:48 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-14 15:48 ebotcazou [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-02 17:03 paolo 2003-03-02 16:43 paolo 2003-03-02 16:26 gennadi.f
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=20030314154830.25610.qmail@sources.redhat.com \ --to=ebotcazou@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=gennadi.f@corigin.com \ --cc=nobody@gcc.gnu.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: linkBe 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).