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/48112] [4.6/4.7 Regression] generic interface to external function in module Date: Tue, 26 Apr 2011 09:24:00 -0000 [thread overview] Message-ID: <bug-48112-4-swrtvp1DRa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48112-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48112 --- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-04-26 09:18:31 UTC --- Seems as if the regression has been introduced in by one of the 16 commits between: Working: 2010-05-13-r159362 Failing: 2010-05-18-r159523 Janus, I have the feeling that it is caused either by Rev. 159506 or by Rev. 159476 (PR 44044); both are your commits. I quickly scanned the commits (all 16) but nothing looked suspicious. I think, one should start a regression hunt to narrow it down to a single commit.
next prev parent reply other threads:[~2011-04-26 9:24 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-14 13:45 [Bug fortran/48112] New: " mhp77 at gmx dot at 2011-03-15 15:13 ` [Bug fortran/48112] [4.6/4.7 Regression] " janus at gcc dot gnu.org 2011-03-17 15:43 ` rguenth at gcc dot gnu.org 2011-03-17 16:41 ` jakub at gcc dot gnu.org 2011-03-25 20:00 ` jakub at gcc dot gnu.org 2011-04-26 9:24 ` burnus at gcc dot gnu.org [this message] 2011-04-26 10:19 ` burnus at gcc dot gnu.org 2011-04-26 13:51 ` burnus at gcc dot gnu.org 2011-04-28 5:48 ` burnus at gcc dot gnu.org 2011-04-28 18:49 ` burnus at gcc dot gnu.org 2011-04-28 18:52 ` 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-48112-4-swrtvp1DRa@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).