public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/61964] [4.8/4.9 regression] krb5 database propagation enters infinite loop; reduced test case Date: Mon, 18 Aug 2014 08:38:00 -0000 [thread overview] Message-ID: <bug-61964-4-I3lafqWjlM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61964-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61964 Bug 61964 depends on bug 62030, which changed state. Bug 62030 Summary: wrong code due to ifcvt merging two stores which have different aliasing sets https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62030 What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED
prev parent reply other threads:[~2014-08-18 8:38 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-30 13:21 [Bug tree-optimization/61964] New: [4.8 " andersk at mit dot edu 2014-07-30 14:31 ` [Bug tree-optimization/61964] " ghudson at mit dot edu 2014-07-30 20:21 ` andersk at mit dot edu 2014-07-31 4:20 ` andersk at mit dot edu 2014-07-31 9:29 ` mikpelinux at gmail dot com 2014-07-31 9:48 ` schwab@linux-m68k.org 2014-07-31 10:05 ` [Bug tree-optimization/61964] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org 2014-07-31 12:20 ` vries at gcc dot gnu.org 2014-07-31 12:24 ` rguenther at suse dot de 2014-07-31 14:07 ` rguenth at gcc dot gnu.org 2014-07-31 14:10 ` [Bug tree-optimization/61964] [4.8/4.9 " rguenth at gcc dot gnu.org 2014-07-31 17:09 ` vries at gcc dot gnu.org 2014-08-01 7:32 ` rguenth at gcc dot gnu.org 2014-08-01 7:36 ` rguenth at gcc dot gnu.org 2014-08-01 7:40 ` rguenth at gcc dot gnu.org 2014-08-01 8:17 ` rguenth at gcc dot gnu.org 2014-08-01 8:18 ` andersk at mit dot edu 2014-08-04 0:25 ` vries at gcc dot gnu.org 2014-08-18 8:38 ` vries at gcc dot gnu.org [this message]
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-61964-4-I3lafqWjlM@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).