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/55887] [OOP][F2008] ICE with CLASS and data-target pointer association in (default) initialization Date: Sat, 26 Jan 2013 21:10:00 -0000 [thread overview] Message-ID: <bug-55887-4-Bmb4oI67S0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55887-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55887 janus at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2013-01-26 CC| |janus at gcc dot gnu.org Ever Confirmed|0 |1 --- Comment #2 from janus at gcc dot gnu.org 2013-01-26 21:10:15 UTC --- The type(t) version ... type t end type t type(t), target :: x type(t), pointer :: ptr2 => x if (.not. same_type_as (ptr2, x)) call abort() end ... is rejected by 4.7 with (note the wrong locus): type t 1 Error: Pointer initialization target at (1) must have the SAVE attribute but trunk gives yet another ICE: internal compiler error: in symtab_get_node, at symtab.c:277 I think the error message of 4.7 is not triggered on trunk, because 'x' gets the SAVE_IMPLICIT attribute. The ICE goes away when giving 'x' the SAVE attribute explicitly.
next prev parent reply other threads:[~2013-01-26 21:10 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-06 14:53 [Bug fortran/55887] New: " burnus at gcc dot gnu.org 2013-01-24 19:16 ` [Bug fortran/55887] " tilo@tilo-schwarz.de 2013-01-26 21:10 ` janus at gcc dot gnu.org [this message] 2013-01-26 21:21 ` janus at gcc dot gnu.org 2013-07-31 13:09 ` [Bug fortran/55887] [OOP][F08] " janus at gcc dot gnu.org 2013-07-31 13:10 ` janus at gcc dot gnu.org 2013-08-09 8:34 ` janus at gcc dot gnu.org 2014-03-15 11:12 ` dominiq at lps dot ens.fr
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-55887-4-Bmb4oI67S0@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: 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).