public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/62113] [graphite] ICE using -floop-parallelize-all Date: Thu, 14 Aug 2014 13:14:00 -0000 [thread overview] Message-ID: <bug-62113-4-WDRTGk72iO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-62113-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62113 ktkachov at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |compile-time-hog, | |memory-hog Target| |arm, aarch64, x86_64 Status|UNCONFIRMED |NEW Last reconfirmed| |2014-08-14 CC| |ktkachov at gcc dot gnu.org Ever confirmed|0 |1 Known to fail| |4.8.4, 4.9.1, 5.0 --- Comment #2 from ktkachov at gcc dot gnu.org --- Confirmed on 4.9.1 and current trunk on arm and aarch64. Didn't try 4.8
next prev parent reply other threads:[~2014-08-14 13:14 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-12 20:22 [Bug c/62113] New: " drfiemost at email dot it 2014-08-14 12:55 ` [Bug tree-optimization/62113] " drfiemost at email dot it 2014-08-14 13:14 ` ktkachov at gcc dot gnu.org [this message] 2015-10-09 16:32 ` spop 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-62113-4-WDRTGk72iO@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).