public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/20607] [3.4 Regression] -fstrict-aliasing causes incorrect scheduling Date: Tue, 10 May 2005 03:16:00 -0000 [thread overview] Message-ID: <20050510031620.13157.qmail@sourceware.org> (raw) In-Reply-To: <20050323190354.20607.Ganesh.Sittampalam@arm.com> ------- Additional Comments From mmitchel at gcc dot gnu dot org 2005-05-10 03:16 ------- Eric -- Never mind; test results aren't looking good. It looks like those comments about offsetof were there for a reason. I'm still going to try applying the patch to mainline -- but I don't think there's going to be a good solution for 3.4.x. -- Mark -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20607
next prev parent reply other threads:[~2005-05-10 3:16 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-03-23 19:04 [Bug c++/20607] New: -fstrict-aliasing causes incorrect scheduling on Sparc Solaris Ganesh dot Sittampalam at arm dot com 2005-03-23 19:04 ` [Bug c++/20607] " Ganesh dot Sittampalam at arm dot com 2005-03-23 19:05 ` Ganesh dot Sittampalam at arm dot com 2005-03-23 21:47 ` ebotcazou at gcc dot gnu dot org 2005-03-29 19:19 ` [Bug c++/20607] [3.4 Regression] -fstrict-aliasing causes incorrect scheduling ebotcazou at gcc dot gnu dot org 2005-03-29 19:43 ` ebotcazou at gcc dot gnu dot org 2005-03-30 10:53 ` ebotcazou at gcc dot gnu dot org 2005-03-31 0:55 ` mark at codesourcery dot com 2005-03-31 6:30 ` ebotcazou at libertysurf dot fr 2005-05-10 2:49 ` mmitchel at gcc dot gnu dot org 2005-05-10 3:16 ` mmitchel at gcc dot gnu dot org [this message] 2005-05-10 3:17 ` mmitchel at gcc dot gnu 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=20050510031620.13157.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).