public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikpe at it dot uu.se" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/50078] [4.6.1+ SVN 2011-08-13] ARM wrong code: volatile accesses optimized out Date: Sun, 14 Aug 2011 09:24:00 -0000 [thread overview] Message-ID: <bug-50078-4-6ehOyip9IE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50078-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50078 Mikael Pettersson <mikpe at it dot uu.se> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mikpe at it dot uu.se --- Comment #1 from Mikael Pettersson <mikpe at it dot uu.se> 2011-08-14 09:22:01 UTC --- Not ARM-specific, also happens on i686-linux.
next prev parent reply other threads:[~2011-08-14 9:22 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-14 0:57 [Bug c/50078] New: " khc at pm dot waw.pl 2011-08-14 9:24 ` mikpe at it dot uu.se [this message] 2011-08-14 9:39 ` [Bug c/50078] " rguenth at gcc dot gnu.org 2011-08-15 9:14 ` [Bug rtl-optimization/50078] [4.6/4.7 Regression] combine " rguenth at gcc dot gnu.org 2011-08-15 9:16 ` rguenth at gcc dot gnu.org 2011-08-17 21:28 ` jsm28 at gcc dot gnu.org 2011-09-05 11:49 ` steven at gcc dot gnu.org 2011-09-11 15:18 ` steven at gcc dot gnu.org 2011-09-11 15:26 ` steven at gcc dot gnu.org 2011-09-11 15:44 ` steven at gcc dot gnu.org 2011-09-11 16:28 ` steven at gcc dot gnu.org 2011-10-26 17:58 ` jakub at gcc dot gnu.org 2011-11-28 9:49 ` [Bug tree-optimization/50078] " jakub at gcc dot gnu.org 2011-11-28 21:10 ` jakub at gcc dot gnu.org 2011-11-28 21:11 ` [Bug tree-optimization/50078] [4.6 " jakub at gcc dot gnu.org 2011-12-09 11:34 ` jakub at gcc dot gnu.org 2011-12-10 16:40 ` mikpe at it dot uu.se 2011-12-12 17:38 ` jakub at gcc dot gnu.org 2012-06-11 9:51 ` xguo at gcc dot gnu.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=bug-50078-4-6ehOyip9IE@http.gcc.gnu.org/bugzilla/ \ --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).