public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: jakub@gcc.gnu.org To: er@openoffice.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, mh@openoffice.org, nobody@gcc.gnu.org Subject: Re: optimization/4922: gcc-3.0.1 and 3.0.2 generate wrong code with -O2 Date: Thu, 21 Feb 2002 08:26:00 -0000 [thread overview] Message-ID: <20020221161113.24717.qmail@sources.redhat.com> (raw) Synopsis: gcc-3.0.1 and 3.0.2 generate wrong code with -O2 State-Changed-From-To: open->closed State-Changed-By: jakub State-Changed-When: Thu Feb 21 08:11:12 2002 State-Changed-Why: This is not a bug in gcc, but in your code. Code like: inline UINT16* RowPos() { return (UINT16*) &nAddress; } *RowPos() = (UINT16) nRow; does not obey aliasing rules (the code is accessing nAddress both as 32-bit integer and 16-bit integer). Please read info gcc about -fstrict-aliasing. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4922
next reply other threads:[~2002-02-21 16:11 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-02-21 8:26 jakub [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-11-16 23:46 er
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=20020221161113.24717.qmail@sources.redhat.com \ --to=jakub@gcc.gnu.org \ --cc=er@openoffice.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=mh@openoffice.org \ --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).