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/51266] [F08] Pointer initialization in PARAMETER Date: Tue, 22 Nov 2011 15:48:00 -0000 [thread overview] Message-ID: <bug-51266-4-JbqzWe9VZi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51266-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51266 --- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-11-22 15:44:34 UTC --- Hmm, I somehow have the feeling that encountered this bug already. See the thread starting at http://j3-fortran.org/pipermail/j3/2011-November/004840.html I think I concur with Malcolm that the code of comment 0 cannot be implemented (at least not without combining the linker with the front-end compiler, something no one wants to do): http://j3-fortran.org/pipermail/j3/2011-November/004851.html On the other hand, I think Bob right at http://j3-fortran.org/pipermail/j3/2011-November/004857.html that the current standard seems to have a loop hole. I probably should have realized the discussion earlier - on the other hand, Bob seems to insist (cf. link above) that the program is not only valid but should also be valid - otherwise, I presume, he wouldn't have posted it at comp.lang.fortran. (A PR might already exist for this thread.)
next prev parent reply other threads:[~2011-11-22 15:45 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-22 10:19 [Bug fortran/51266] New: " burnus at gcc dot gnu.org 2011-11-22 15:48 ` burnus at gcc dot gnu.org [this message] 2012-04-15 19:55 ` [Bug fortran/51266] [F08] " janus at gcc dot gnu.org 2012-04-15 20:04 ` janus at gcc dot gnu.org 2015-08-30 10:14 ` dominiq at lps dot ens.fr 2015-08-30 10:16 ` dominiq at lps dot ens.fr 2015-10-09 8:50 ` 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-51266-4-JbqzWe9VZi@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).