public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/38324] Wrong lbound given to allocatable components
Date: Mon, 01 Dec 2008 13:55:00 -0000	[thread overview]
Message-ID: <20081201135421.32735.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38324-10374@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from dominiq at lps dot ens dot fr  2008-12-01 13:54 -------
AFAICT this pr is the cause of half of the failures of
gfortran.dg/alloc_comp_constructor_1.f90 on i686-apple-darwin9 with
-fdefault-integer-8:

FAIL: gfortran.dg/alloc_comp_constructor_1.f90  -O0  execution test
FAIL: gfortran.dg/alloc_comp_constructor_1.f90  -O0  scan-tree-dump-times
original "builtin_free" 21
FAIL: gfortran.dg/alloc_comp_constructor_1.f90  -O1  execution test
FAIL: gfortran.dg/alloc_comp_constructor_1.f90  -O1  scan-tree-dump-times
original "builtin_free" 21
FAIL: gfortran.dg/alloc_comp_constructor_1.f90  -O2  execution test
FAIL: gfortran.dg/alloc_comp_constructor_1.f90  -O2  scan-tree-dump-times
original "builtin_free" 21
FAIL: gfortran.dg/alloc_comp_constructor_1.f90  -O3 -fomit-frame-pointer 
execution test
FAIL: gfortran.dg/alloc_comp_constructor_1.f90  -O3 -fomit-frame-pointer 
scan-tree-dump-times original "builtin_free" 21
FAIL: gfortran.dg/alloc_comp_constructor_1.f90  -O3 -fomit-frame-pointer
-funroll-loops  execution test
FAIL: gfortran.dg/alloc_comp_constructor_1.f90  -O3 -fomit-frame-pointer
-funroll-loops  scan-tree-dump-times original "builtin_free" 21
FAIL: gfortran.dg/alloc_comp_constructor_1.f90  -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions  execution test
FAIL: gfortran.dg/alloc_comp_constructor_1.f90  -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions  scan-tree-dump-times original
"builtin_free" 21
FAIL: gfortran.dg/alloc_comp_constructor_1.f90  -O3 -g  execution test
FAIL: gfortran.dg/alloc_comp_constructor_1.f90  -O3 -g  scan-tree-dump-times
original "builtin_free" 21
FAIL: gfortran.dg/alloc_comp_constructor_1.f90  -Os  execution test
FAIL: gfortran.dg/alloc_comp_constructor_1.f90  -Os  scan-tree-dump-times
original "builtin_free" 21

The second half is due to 24 "builtin_free" in the "original" dump. This is the
cause of some failures of this test on powerpc-apple-darwin9 (-O0/1, I have
filled pr38347 against the middle-end for the ICE got with higher
optimizations).


-- 


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


  reply	other threads:[~2008-12-01 13:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-30  7:50 [Bug fortran/38324] New: " pault at gcc dot gnu dot org
2008-12-01 13:55 ` dominiq at lps dot ens dot fr [this message]
2008-12-17 12:22 ` [Bug fortran/38324] " pault at gcc dot gnu dot org
2009-01-29 22:03 ` mikael at gcc dot gnu dot org
2010-01-30 18:22 ` pault at gcc dot gnu dot org
2010-01-31 12:05 ` pault at gcc dot gnu dot org
2010-01-31 14:57 ` pault at gcc dot gnu dot org
2010-01-31 15:00 ` pault 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=20081201135421.32735.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).