public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/56490] [4.7/4.8 Regression] -Wall triggering infinite loop Date: Fri, 21 Feb 2014 10:00:00 -0000 [thread overview] Message-ID: <bug-56490-4-q3TtHkA9RD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56490-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56490 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |4.9.0 Summary|[4.7/4.8/4.9 Regression] |[4.7/4.8 Regression] -Wall |-Wall triggering infinite |triggering infinite loop |loop | --- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Hopefully fixed/worked around on the trunk.
next prev parent reply other threads:[~2014-02-21 10:00 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-01 9:24 [Bug fortran/56490] New: [4.6/4.7 " o.flebbe@science-computing.de 2013-03-01 12:10 ` [Bug middle-end/56490] [4.6/4.7/4.8 " rguenth at gcc dot gnu.org 2013-03-01 22:46 ` xinliangli at gmail dot com 2013-03-08 15:52 ` [Bug tree-optimization/56490] [4.6/4.7 " rguenth at gcc dot gnu.org 2013-03-08 16:04 ` [Bug tree-optimization/56490] [4.6/4.7/4.8 " rguenth at gcc dot gnu.org 2013-03-08 16:22 ` xinliangli at gmail dot com 2013-04-12 15:16 ` [Bug tree-optimization/56490] [4.7/4.8/4.9 " jakub at gcc dot gnu.org 2014-02-20 17:14 ` jakub at gcc dot gnu.org 2014-02-20 19:04 ` jakub at gcc dot gnu.org 2014-02-21 9:54 ` jakub at gcc dot gnu.org 2014-02-21 10:00 ` jakub at gcc dot gnu.org [this message] 2014-03-06 8:12 ` [Bug tree-optimization/56490] [4.7/4.8 " jakub at gcc dot gnu.org 2014-06-12 13:25 ` [Bug tree-optimization/56490] [4.7 " rguenth 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-56490-4-q3TtHkA9RD@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).