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 fortran/40873] -fwhole-file -fwhole-program: Wrong decls cause too much to be optimized away
Date: Sat, 24 Jul 2010 20:16:00 -0000 [thread overview]
Message-ID: <20100724201615.15771.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40873-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #19 from burnus at gcc dot gnu dot org 2010-07-24 20:16 -------
And of course the patch won't work out of the box:
$ gfortran -O2 -g gfortran.dg/entry_array_specs_2.f && ./a.out
gfortran.dg/entry_array_specs_2.f:16:0: internal compiler error: in output_die,
at dwarf2out.c:11046
Ditto for gfortran.dg/pr25603.f, gfortran.dg/proc_decl_2.f90,
gfortran.fortran-torture/execute/mystery_proc.f90,
gfortran.fortran-torture/execute/procarg.f90,
gfortran.dg/loc_1.f90, gfortran.dg/value_test.f90,
gfortran.dg/value_tests_f03.f90.
Probably something is wrong with the "current_function_decl = NULL_TREE;" -
hopefully, it is easily fixable and does not require a completely different
approach.
But at least:
(In reply to comment #0)
> the following Polyhedron testcases fail
> ac, aermod, doduc, gas_dyn, linpk, mdbx, rnflow and test_fpu
Using -march=native -ffast-math -funroll-loops -ftree-loop-linear -O3
-fwhole-program -fwhole-file,
*ALMOST ALL* the polyhedron tests succeed - except for gas_dyn and test_fpu
(for which there are still undefined references).
[Using "-g" one also gets issues with polyhedron tests.]
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40873
next prev parent reply other threads:[~2010-07-24 20:16 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 [this message]
2010-07-24 22:05 ` burnus at gcc dot gnu dot org
2010-07-25 10:03 ` dominiq at lps dot ens dot fr
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=20100724201615.15771.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).