public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/55935] [OOP] Fortran fronted has ADDR_EXPRs of FUNCTION_DECLs with bogus BLOCK
Date: Thu, 10 Jan 2013 16:01:00 -0000 [thread overview]
Message-ID: <bug-55935-4-5meMB4lQO6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55935-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55935
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2013-01-10
Ever Confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2013-01-10 16:00:46 UTC ---
> I assume that that relates to the __copy function.
It looks likely: with the patch at
http://gcc.gnu.org/ml/gcc-patches/2013-01/msg00547.html, I get
[macbook] f90/bug% gfc
/opt/gcc/work/gcc/testsuite/gfortran.dg/class_array_15.f03
/opt/gcc/work/gcc/testsuite/gfortran.dg/class_array_15.f03: In function
'pr54992':
/opt/gcc/work/gcc/testsuite/gfortran.dg/class_array_15.f03:97:0: error:
location references block not in block tree
subroutine pr54992 ! This test remains as the original.
^
__copy_g_nodes_Ncbhstd
_22 = __copy_g_nodes_Ncbhstd;
/opt/gcc/work/gcc/testsuite/gfortran.dg/class_array_15.f03:97:0: internal
compiler error: verify_gimple failed
and so on for the other failing tests.
next prev parent reply other threads:[~2013-01-10 16:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 15:37 [Bug fortran/55935] New: " burnus at gcc dot gnu.org
2013-01-10 16:01 ` dominiq at lps dot ens.fr [this message]
2013-01-10 16:25 ` [Bug fortran/55935] " dominiq at lps dot ens.fr
2013-01-10 16:29 ` jakub at gcc dot gnu.org
2013-01-10 17:35 ` dominiq at lps dot ens.fr
2013-01-10 22:35 ` dominiq at lps dot ens.fr
2013-01-10 23:11 ` dominiq at lps dot ens.fr
2013-01-11 9:19 ` jakub at gcc dot gnu.org
2013-01-11 10:03 ` jakub at gcc dot gnu.org
2013-01-11 13:36 ` dominiq at lps dot ens.fr
2013-01-11 13:44 ` rguenth at gcc dot gnu.org
2013-01-11 14:06 ` rguenth at gcc dot gnu.org
2013-01-11 14:31 ` rguenth at gcc dot gnu.org
2013-01-11 14:41 ` jakub at gcc dot gnu.org
2013-01-11 14:54 ` rguenth at gcc dot gnu.org
2013-01-11 14:56 ` rguenth at gcc dot gnu.org
2013-01-13 12:34 ` jakub at gcc dot gnu.org
2013-01-13 16:54 ` jakub at gcc dot gnu.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=bug-55935-4-5meMB4lQO6@http.gcc.gnu.org/bugzilla/ \
--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).