public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "felix-gcc at fefe dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/32856] Invalid optimization in the face of aliasing Date: Sun, 22 Jul 2007 17:12:00 -0000 [thread overview] Message-ID: <20070722171242.22062.qmail@sourceware.org> (raw) In-Reply-To: <bug-32856-3511@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from felix-gcc at fefe dot de 2007-07-22 17:12 ------- FWIW, the C compilers from Intel and Sun do reload n->next. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32856
next prev parent reply other threads:[~2007-07-22 17:12 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-22 17:06 [Bug c/32856] New: " felix-gcc at fefe dot de 2007-07-22 17:09 ` [Bug c/32856] " felix-gcc at fefe dot de 2007-07-22 17:12 ` felix-gcc at fefe dot de [this message] 2007-07-22 19:27 ` [Bug middle-end/32856] " pinskia at gcc dot gnu dot org 2007-07-22 23:01 ` falk at debian dot org 2007-07-22 23:08 ` felix-gcc at fefe dot de 2007-07-22 23:19 ` falk at debian dot org 2007-07-23 10:09 ` vogel at pi2 dot physik dot uni-erlangen dot de 2007-07-23 14:17 ` falk at debian dot org 2007-07-24 12:09 ` rguenth at gcc dot gnu dot org 2007-07-25 8:24 ` falk at debian dot org
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=20070722171242.22062.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).