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/51605] internal compiler error gfc_trans_block_construct, at fortran/trans-stmt.c:984 Date: Sun, 18 Dec 2011 10:08:00 -0000 [thread overview] Message-ID: <bug-51605-4-Oy5nJ5MgtC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51605-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51605 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org --- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-12-18 10:01:13 UTC --- With the current GCC 4.7 I get for the original example (comment 0, attachment 26126) but also for Steve's reduced test case in comment 3 the error: integer_ptr => symbol_ptr 1 Error: Pointer assignment target is neither TARGET nor POINTER at (1) [Cf. comment 2, PR 48887] I believe the error message is correct due to (F2008, 16.5.1.6 Construct association): "If the selector has the POINTER attribute, it shall be associated; the associate name is associated with the target of the pointer and does not have the POINTER attribute." And due to the error message, the code part which ICEs cannot be reached. Dan: You wrote: "Compiles with fort 12.1, nagfor has a different problem." Do you believe the code is valid, if so, why doesn't 16.5.1.6 apply? If it applies, can you construct a valid example which still fails? Dan, Stave: If possible, please also update your GCC to 2011-12-11 or newer - at least if you use OOP/polymorphism features. (You might be able to get a newer binary from http://gcc.gnu.org/wiki/GFortranBinaries )
next prev parent reply other threads:[~2011-12-18 10:01 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-17 22:46 [Bug fortran/51605] New: " danlnagle at me dot com 2011-12-17 23:26 ` [Bug fortran/51605] " danlnagle at me dot com 2011-12-17 23:48 ` dominiq at lps dot ens.fr 2011-12-18 9:24 ` kargl at gcc dot gnu.org 2011-12-18 10:08 ` burnus at gcc dot gnu.org [this message] 2011-12-18 13:55 ` danlnagle at me dot com 2011-12-18 14:15 ` burnus at gcc dot gnu.org 2011-12-18 16:57 ` sgk at troutmask dot apl.washington.edu 2011-12-19 11:52 ` burnus at gcc dot gnu.org 2011-12-19 13:19 ` burnus at gcc dot gnu.org 2011-12-19 15:32 ` burnus at gcc dot gnu.org 2011-12-19 15:54 ` danlnagle at me dot com 2011-12-19 18:56 ` burnus at gcc dot gnu.org 2011-12-19 20:26 ` burnus at gcc dot gnu.org 2011-12-19 20:30 ` burnus at gcc dot gnu.org 2013-12-14 20:15 ` dominiq at lps dot ens.fr 2013-12-14 22:25 ` janus at gcc dot gnu.org 2023-03-06 17:18 ` anlauf 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-51605-4-Oy5nJ5MgtC@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).