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/40873] -fwhole-file -fwhole-program: Wrong decls cause too much to be optimized away Date: Sun, 25 Jul 2010 10:03:00 -0000 [thread overview] Message-ID: <20100725100340.20569.qmail@sourceware.org> (raw) In-Reply-To: <bug-40873-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #21 from dominiq at lps dot ens dot fr 2010-07-25 10:03 ------- With the patch in comment #18, I see all the failures reported in comment #19, plus FAIL: gfortran.dg/whole_file_9.f90 -O (internal compiler error) FAIL: gfortran.dg/g77/13037.f -O3 -g (internal compiler error) With -fwhole-program -O3 -g, most of the polyhedron tests fail either with "internal compiler error: in output_die, at dwarf2out.c:11046" or with a segmentation fault. In addition without any option, I see several failures for codes with recursive functions, such as (from pr27613): program test interface function bad_stuff(n) integer :: bad_stuff (2) integer :: n(2) end function bad_stuff recursive function rec_stuff(n) result (tmp) integer :: n(2), tmp(2) end function rec_stuff end interface integer :: res(2) res = bad_stuff((/-19,-30/)) print *, res if (any (res .ne. (/25,25/))) call abort () if (any (rec_stuff((/-19,-30/)) .ne. (/25,25/))) call abort () end program test recursive function bad_stuff(n) integer :: bad_stuff (2) integer :: n(2), tmp(2) bad_stuff = rec_stuff (n) if((maxval (n)>0).and.(maxval (n) < 2)) then bad_stuff = bad_stuff + bad_stuff (maxval (n)+1) endif entry rec_stuff(n) result (tmp) tmp=1 if(maxval (n) < 5) then tmp = tmp + rec_stuff (n+1) endif end function bad_stuff -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40873
next prev parent reply other threads:[~2010-07-25 10:03 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-07-27 13:57 [Bug fortran/40873] New: " burnus at gcc dot gnu dot org 2009-07-27 14:47 ` [Bug fortran/40873] " burnus at gcc dot gnu dot org 2009-07-28 13:12 ` rguenth at gcc dot gnu dot org 2009-09-22 15:34 ` rguenth at gcc dot gnu dot org 2009-09-22 15:42 ` rguenth at gcc dot gnu dot org 2010-05-15 19:54 ` dominiq at lps dot ens dot fr 2010-05-16 10:53 ` rguenth at gcc dot gnu dot org 2010-05-16 11:01 ` dominiq at lps dot ens dot fr 2010-05-16 11:04 ` rguenther at suse dot de 2010-05-16 11:17 ` dominiq at lps dot ens dot fr 2010-05-16 11:21 ` rguenther at suse dot de 2010-05-20 13:51 ` pault at gcc dot gnu dot org 2010-05-24 12:32 ` pault at gcc dot gnu dot org 2010-05-26 14:28 ` burnus at gcc dot gnu dot org 2010-05-26 14:41 ` dominiq at lps dot ens dot fr 2010-05-26 14:46 ` burnus at gcc dot gnu dot org 2010-06-09 22:10 ` fxcoudert at gcc dot gnu dot org 2010-07-24 18:15 ` jv244 at cam dot ac dot uk 2010-07-24 19:13 ` burnus at gcc dot gnu dot org 2010-07-24 20:16 ` burnus at gcc dot gnu dot org 2010-07-24 22:05 ` burnus at gcc dot gnu dot org 2010-07-25 10:03 ` dominiq at lps dot ens dot fr [this message] 2010-07-25 10:14 ` burnus at gcc dot gnu dot org 2010-07-26 13:25 ` burnus at gcc dot gnu dot org 2010-07-26 17:02 ` dominiq at lps dot ens dot fr 2010-07-26 17:04 ` burnus at gcc dot gnu dot org 2010-07-26 21:00 ` dominiq at lps dot ens dot fr 2010-07-27 8:44 ` burnus at gcc dot gnu dot org 2010-07-27 8:46 ` burnus 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=20100725100340.20569.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: 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).