public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/63602] [5/6 Regression] Wrong code w/ -O2 -ftree-loop-linear Date: Wed, 19 Aug 2015 12:28:00 -0000 [thread overview] Message-ID: <bug-63602-4-RUipOTyPED@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63602-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63602 Bernd Edlinger <bernd.edlinger at hotmail dot de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bernd.edlinger at hotmail dot de --- Comment #3 from Bernd Edlinger <bernd.edlinger at hotmail dot de> --- BTW: same results for gcc-5.1.0 with isl-0.12.2: gcc -floop-block -O2 pr63602.c gcc -floop-interchange -O2 pr63602.c gcc -floop-parallelize-all -O2 pr63602.c gcc -floop-strip-mine -O2 pr63602.c even worse: gcc -floop-unroll-and-jam -O2 pr63602.c ../../gcc-5.1.0/isl/isl_ctx.c:172: isl_ctx freed, but some objects still reference it pr63602.c: In function 'main': pr63602.c:7:1: internal compiler error: Aborted main(void) ^ Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions.
next prev parent reply other threads:[~2015-08-19 12:28 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-20 11:30 [Bug tree-optimization/63602] New: " asolokha at gmx dot com 2014-10-21 4:58 ` [Bug tree-optimization/63602] " asolokha at gmx dot com 2015-05-13 10:54 ` [Bug tree-optimization/63602] [5/6 Regression] " asolokha at gmx dot com 2015-08-19 12:28 ` bernd.edlinger at hotmail dot de [this message] 2015-10-16 8:28 ` 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-63602-4-RUipOTyPED@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).