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/53478] gfortran segfaults when module name clashes with C binding name of procedure
Date: Mon, 15 Apr 2013 11:01:00 -0000 [thread overview]
Message-ID: <bug-53478-4-816GRm0Am8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53478-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53478
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #6 from Tobias Burnus <burnus at gcc dot gnu.org> 2013-04-15 11:01:10 UTC ---
(In reply to comment #4)
> I have the patch in comment #2 in my tree since some time now and it works as
> advertised without regression. However, If I have understood Ian Harvey's
> answer in comp.lang.fortran
> https://groups.google.com/forum/?fromgroups#!topic/comp.lang.fortran/o_hapvMHxIE
> the test in comment #3 is invalid. Is this correct?
The test case in comment 0 and comment 3 are invalid in Fortran 2003; I think
they are valid in Fortran 2008 (cf. PR 48858 comment 9). However, I need a
quiet moment to disentangle the standard speak and to create a patch.
next prev parent reply other threads:[~2013-04-15 11:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 17:08 [Bug fortran/53478] New: " solomon.gibbs.lists at gmail dot com
2012-05-24 17:45 ` [Bug fortran/53478] " kargl at gcc dot gnu.org
2012-05-24 18:06 ` sgk at troutmask dot apl.washington.edu
2012-05-24 18:53 ` sgk at troutmask dot apl.washington.edu
2012-06-25 12:06 ` dominiq at lps dot ens.fr
2013-04-15 10:06 ` aron at ahmadia dot net
2013-04-15 11:01 ` burnus at gcc dot gnu.org [this message]
2013-05-20 20:14 ` burnus 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-53478-4-816GRm0Am8@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).