public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/51993] Erroneous type component initialization leads to internal compiler error Date: Wed, 25 Jan 2012 11:14:00 -0000 [thread overview] Message-ID: <bug-51993-4-PPAwvjyZTX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51993-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51993 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |accepts-invalid, | |diagnostic, | |ice-on-invalid-code CC| |burnus at gcc dot gnu.org Version|fortran-dev |4.7.0 --- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-01-25 11:01:39 UTC --- I can reproduce the ICE. It compiles with GCC 4.1 (without further diagnostic) but it crashes with 4.3 to 4.7. (If one uses the DT without specifying an initialization, GCC 4.1 prints an error.) There are also other variants, which crash, e.g. type :: mytyp character(len=.true.) :: a = '3' end type mytyp which diagnoses the error without the initializer "= '3'". No error but nevertheless invalid: Initialization of a scalar with an array type :: mytyp character(len=4) :: a = ['a','3'] end type mytyp
next prev parent reply other threads:[~2012-01-25 11:02 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-25 10:28 [Bug fortran/51993] New: " bardeau at iram dot fr 2012-01-25 11:14 ` burnus at gcc dot gnu.org [this message] 2013-02-27 15:56 ` [Bug fortran/51993] " dominiq at lps dot ens.fr 2015-10-29 10:54 ` dominiq at lps dot ens.fr 2015-10-29 12:34 ` dominiq at lps dot ens.fr 2015-10-30 17:55 ` kargl at gcc dot gnu.org 2015-10-30 18:14 ` kargl at gcc dot gnu.org 2015-10-30 18:27 ` kargl at gcc dot gnu.org 2015-10-30 18:35 ` kargl at gcc dot gnu.org 2015-10-30 18:36 ` kargl 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-51993-4-PPAwvjyZTX@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).