public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/57381] [4.8 Regression] array of volatile pointers hangs gcc Date: Thu, 23 May 2013 10:09:00 -0000 [thread overview] Message-ID: <bug-57381-4-ZwYUSFcyjk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57381-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57381 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |4.9.0 Target Milestone|4.8.1 |4.8.2 Summary|[4.8/4.9 Regression] array |[4.8 Regression] array of |of volatile pointers hangs |volatile pointers hangs gcc |gcc | Known to fail| |4.8.1 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- Author: rguenth Date: Thu May 23 10:08:33 2013 New Revision: 199240 URL: http://gcc.gnu.org/viewcvs?rev=199240&root=gcc&view=rev Log: 2013-05-23 Richard Biener <rguenther@suse.de> PR middle-end/57381 * fold-const.c (operand_equal_p): Compare FIELD_DECLs with OEP_CONSTANT_ADDRESS_OF retained. * gcc.dg/torture/pr57381.c: New testcase. Added: trunk/gcc/testsuite/gcc.dg/torture/pr57381.c Modified: trunk/gcc/ChangeLog trunk/gcc/fold-const.c trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2013-05-23 10:09 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-22 21:49 [Bug rtl-optimization/57381] New: " dhazeghi at yahoo dot com 2013-05-23 8:05 ` [Bug rtl-optimization/57381] [4.8/4.9 Regression] " rguenth at gcc dot gnu.org 2013-05-23 10:09 ` rguenth at gcc dot gnu.org [this message] 2013-08-29 13:15 ` [Bug rtl-optimization/57381] [4.8 " jakub at gcc dot gnu.org 2013-08-29 13:18 ` jakub 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-57381-4-ZwYUSFcyjk@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).