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/45087] -fwhole-program: Miscompiled due to wrong decls
Date: Wed, 28 Jul 2010 13:52:00 -0000 [thread overview]
Message-ID: <20100728135151.14946.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45087-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from burnus at gcc dot gnu dot org 2010-07-28 13:51 -------
(In reply to comment #3)
> Minimal test case, compile with:
There is something odd: If one has the order
subroutine VALUE()
subroutine NEXT
it actually works; one then goes
gfc_create_function_decl for VALUE
gfc_get_extern_function_decl for NEXT
call gfc_create_function_decl for NEXT
while for the opposite order it fails:
gfc_create_function_decl for NEXT
gfc_create_function_decl for VALUE
gfc_get_extern_function_decl for NEXT
In both cases the backend_decl is used in gfc_get_extern_function_decl. And in
all cases it seems as if the the module's next's gsym->...->backend_decl ==
NULL.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45087
next prev parent reply other threads:[~2010-07-28 13:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 17:27 [Bug fortran/45087] New: " burnus at gcc dot gnu dot org
2010-07-26 21:04 ` [Bug fortran/45087] " burnus at gcc dot gnu dot org
2010-07-28 9:32 ` burnus at gcc dot gnu dot org
2010-07-28 12:35 ` burnus at gcc dot gnu dot org
2010-07-28 13:14 ` burnus at gcc dot gnu dot org
2010-07-28 13:52 ` burnus at gcc dot gnu dot org [this message]
2010-07-28 20:34 ` burnus at gcc dot gnu dot org
2010-07-29 10:26 ` mikael at gcc dot gnu dot org
2010-07-29 21:08 ` burnus at gcc dot gnu dot org
2010-07-29 21:08 ` 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=20100728135151.14946.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).