public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/43796] [4.5/4.6 Regression] ICE in is_overflow_infinity (tree-vrp.c:184) with gfortran -fcheck=bounds -O2
Date: Mon, 19 Apr 2010 11:40:00 -0000	[thread overview]
Message-ID: <20100419114001.26050.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43796-12935@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from burnus at gcc dot gnu dot org  2010-04-19 11:39 -------
Confirm. It fails with 4.5 and 4.6 using the option -fbounds-check (==
-fcheck-bounds), but only with -O2 and higher and for some reasons only with
-m32 and not with -m64 on x86_64-unknown-linux-gnu.

It works with GCC 4.1/4.2/4.3/4.4.

Valgrind shows:

==2634== Invalid read of size 2
==2634==    at 0x9643CA: is_overflow_infinity (tree-vrp.c:184)
==2634==    by 0x96447D: usable_range_p (tree-vrp.c:797)
==2634==    by 0x96A3DD: compare_ranges (tree-vrp.c:3388)
==2634==    by 0x96B083: vrp_evaluate_conditional_warnv_with_ops
(tree-vrp.c:5669)
==2634==    by 0x96B91F: vrp_evaluate_conditional (tree-vrp.c:5710)
==2634==    by 0x9309DE: thread_across_edge (tree-ssa-threadedge.c:537)
==2634==    by 0x9765ED: execute_vrp (tree-vrp.c:7214)
==2634==    by 0x785B9A: execute_one_pass (passes.c:1569)
==2634==    by 0x785E24: execute_pass_list (passes.c:1624)
==2634==    by 0x785E36: execute_pass_list (passes.c:1625)
==2634==    by 0x87AB34: tree_rest_of_compilation (tree-optimize.c:413)
==2634==    by 0x9FCA60: cgraph_expand_function (cgraphunit.c:1548)
==2634==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==2634==
test.f90: In function 'f06fkfn':
test.f90:1:0: internal compiler error: Segmentation fault
Please submit a full bug report,


-- 

burnus at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |burnus at gcc dot gnu dot
                   |                            |org
          Component|fortran                     |middle-end
 GCC target triplet|                            |i386-unknown-linux-gnu
           Keywords|                            |ice-on-valid-code
      Known to fail|                            |4.5.0 4.6.0
      Known to work|                            |4.4.4
            Summary|ICE with -fcheck=all        |[4.5/4.6 Regression] ICE in
                   |                            |is_overflow_infinity (tree-
                   |                            |vrp.c:184) with gfortran -
                   |                            |fcheck=bounds -O2


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43796


  parent reply	other threads:[~2010-04-19 11:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19 10:11 [Bug fortran/43796] New: ICE with -fcheck=all mathewc at nag dot co dot uk
2010-04-19 10:56 ` [Bug fortran/43796] " dominiq at lps dot ens dot fr
2010-04-19 11:40 ` burnus at gcc dot gnu dot org [this message]
2010-04-19 12:26 ` [Bug middle-end/43796] [4.5/4.6 Regression] ICE in is_overflow_infinity (tree-vrp.c:184) with gfortran -fcheck=bounds -O2 rguenth at gcc dot gnu dot org
2010-04-19 15:17 ` rguenth at gcc dot gnu dot org
2010-04-19 15:21 ` [Bug middle-end/43796] [4.5 " rguenth at gcc dot gnu dot org
2010-04-20  9:04 ` rguenth at gcc dot gnu dot org
2010-04-20  9:06 ` rguenth at gcc dot gnu dot 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=20100419114001.26050.qmail@sourceware.org \
    --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).