public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/41227] COMMON block, BIND(C) and LTO interoperability issues Date: Thu, 05 Jan 2012 13:38:00 -0000 [thread overview] Message-ID: <bug-41227-4-iySF4Eruyn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-41227-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41227 --- Comment #9 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-01-05 13:37:09 UTC --- This is still not fixed (at least by design - bind_c_coms.f90/bind_c_coms_driver.c passes with -flto now). Can somebody produce a reduced testcase pair that just has a bind-C named common with a single int so I can experiment a bit? Thx.
next parent reply other threads:[~2012-01-05 13:38 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-41227-4@http.gcc.gnu.org/bugzilla/> 2012-01-05 13:38 ` rguenth at gcc dot gnu.org [this message] 2014-06-08 16:53 ` fxcoudert at gcc dot gnu.org 2014-06-10 13:06 ` rguenth at gcc dot gnu.org 2014-07-14 10:21 ` fxcoudert at gcc dot gnu.org 2014-07-14 10:36 ` rguenther at suse dot de 2014-07-14 10:45 ` fxcoudert at gcc dot gnu.org 2014-07-14 11:09 ` rguenth at gcc dot gnu.org 2014-07-14 11:20 ` fxcoudert at gcc dot gnu.org 2014-07-14 11:36 ` burnus at gcc dot gnu.org 2014-07-14 11:46 ` rguenther at suse dot de 2014-07-14 12:05 ` tobi at gcc dot gnu.org 2014-07-14 13:33 ` burnus at gcc dot gnu.org 2015-05-27 23:55 ` hubicka at gcc dot gnu.org 2009-09-02 14:26 [Bug fortran/41227] New: " burnus at gcc dot gnu dot org 2009-09-14 21:05 ` [Bug fortran/41227] " burnus at gcc dot gnu dot org 2009-09-28 19:59 ` tobi at gcc dot gnu dot org 2010-01-29 17:46 ` burnus at gcc dot gnu dot org 2010-02-02 10:29 ` burnus at gcc dot gnu dot org 2010-02-11 16:29 ` burnus at gcc dot gnu dot org 2010-02-23 9:08 ` burnus at gcc dot gnu dot org 2010-02-23 9:33 ` rguenther at suse dot de 2010-06-03 13:49 ` rguenth at gcc dot gnu dot 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-41227-4-iySF4Eruyn@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).