public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mircea.namolaru at inria dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/56145] [4.8/4.9 Regression] Use of too much optimizations -O2 -ffast-math -floop-parallelize-all
Date: Tue, 24 Feb 2015 16:22:00 -0000	[thread overview]
Message-ID: <bug-56145-4-gTh2HVAp1g@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56145-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56145

--- Comment #16 from Mircea Namolaru <mircea.namolaru at inria dot fr> ---
Right, the NULL check fixed this for previous versions of GCC.

For the current version, it works without these NULL checks (the NULL paths are
not followed). The relevant scop fields are always initialized to empty maps,
so they are never NULL. The problematic call to compute_deps where the NULL
problem occured was from parallelization check code
(compute_loop_level_carries_dependencies), code no longer in GCC.


  parent reply	other threads:[~2015-02-24 15:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-30  5:28 [Bug tree-optimization/56145] New: [4.8.0 ICE] " vchou79 at gmail dot com
2013-01-31 13:41 ` [Bug tree-optimization/56145] " vchou79 at gmail dot com
2013-02-08 15:47 ` [Bug tree-optimization/56145] [4.8 Regression] " rguenth at gcc dot gnu.org
2013-02-08 18:29 ` vchou79 at gmail dot com
2013-02-09  0:37 ` vchou79 at gmail dot com
2013-03-03  5:00 ` vchou79 at gmail dot com
2013-03-22 14:44 ` [Bug tree-optimization/56145] [4.8/4.9 " jakub at gcc dot gnu.org
2013-05-31 11:03 ` jakub at gcc dot gnu.org
2013-10-16  9:49 ` jakub at gcc dot gnu.org
2013-10-25 12:23 ` rguenth at gcc dot gnu.org
2013-10-25 12:30 ` rguenth at gcc dot gnu.org
2014-05-22  9:04 ` [Bug tree-optimization/56145] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:27 ` [Bug tree-optimization/56145] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-02-24 11:28 ` jakub at gcc dot gnu.org
2015-02-24 14:33 ` mircea.namolaru at inria dot fr
2015-02-24 14:36 ` [Bug tree-optimization/56145] [4.8/4.9 " rguenth at gcc dot gnu.org
2015-02-24 16:22 ` mircea.namolaru at inria dot fr [this message]
2015-06-23  8:18 ` rguenth at gcc dot gnu.org
2015-06-26 19:54 ` [Bug tree-optimization/56145] [4.9 " jakub at gcc dot gnu.org
2015-06-26 20:27 ` 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-56145-4-gTh2HVAp1g@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: link
Be 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).