public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/54874] [OOP] polymorphic allocation with SOURCE
Date: Tue, 09 Oct 2012 22:11:00 -0000 [thread overview]
Message-ID: <bug-54874-4-fJ2lc0p5g2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54874-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54874
--- Comment #12 from janus at gcc dot gnu.org 2012-10-09 22:10:59 UTC ---
(In reply to comment #10)
> All three cleanly compile comment 0, while only the 4.7 version fails to
> compile commment 1 with some ICE:
>
> c1.f90: In Funktion »testsource«:
> c1.f90:58:0: interner Compiler-Fehler: Segmentation fault: 11
This goes away when updating to
gcc-Version 4.7.3 20121009 (prerelease) [gcc-4_7-branch revision 192273] (GCC)
just as the runtime error in comment 11.
next prev parent reply other threads:[~2012-10-09 22:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 9:58 [Bug fortran/54874] New: OOP: " sfilippone at uniroma2 dot it
2012-10-09 10:02 ` [Bug fortran/54874] " sfilippone at uniroma2 dot it
2012-10-09 10:37 ` sfilippone at uniroma2 dot it
2012-10-09 10:48 ` dominiq at lps dot ens.fr
2012-10-09 11:03 ` sfilippone at uniroma2 dot it
2012-10-09 14:43 ` [Bug fortran/54874] [OOP] " janus at gcc dot gnu.org
2012-10-09 14:46 ` sfilippone at uniroma2 dot it
2012-10-09 14:47 ` janus at gcc dot gnu.org
2012-10-09 16:02 ` sfilippone at uniroma2 dot it
2012-10-09 16:15 ` janus at gcc dot gnu.org
2012-10-09 17:13 ` janus at gcc dot gnu.org
2012-10-09 19:42 ` janus at gcc dot gnu.org
2012-10-09 22:11 ` janus at gcc dot gnu.org [this message]
2012-10-10 10:29 ` janus at gcc dot gnu.org
2012-10-10 11:37 ` sfilippone at uniroma2 dot it
2012-10-10 11:49 ` janus 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-54874-4-fJ2lc0p5g2@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).