public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/48412] [4.7 Regression] CP2K miscompiled due to some Fortran frontend pass
Date: Sat, 02 Apr 2011 10:25:00 -0000	[thread overview]
Message-ID: <bug-48412-4-gOCL3TLiuL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48412-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48412

Steven Bosscher <steven at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |steven at gcc dot gnu.org

--- Comment #1 from Steven Bosscher <steven at gcc dot gnu.org> 2011-04-02 10:25:12 UTC ---
Joost, perhaps you can narrow it down further by using a debug counter.

You'd have to add a debug counter to dbgcnt.def, say "frontend1" 
Instead of "if (0 ...)", you would add'd do "if (dbg_cnt (frontend1) ...)".

Then compile with -fdbg-cnt=frontend1:N where N is a number, run, and see if
the bug occurs. The trick is to find the greatest value for N where the bug
occurs. This can be done with a binary search, as explained in dbgcnt.def.


  reply	other threads:[~2011-04-02 10:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-02  7:13 [Bug fortran/48412] New: " Joost.VandeVondele at pci dot uzh.ch
2011-04-02 10:25 ` steven at gcc dot gnu.org [this message]
2011-04-03 11:11 ` [Bug fortran/48412] " rguenth at gcc dot gnu.org
2011-04-03 17:28 ` tkoenig at gcc dot gnu.org
2011-04-04  9:07 ` Joost.VandeVondele at pci dot uzh.ch
2011-04-04 10:52 ` Joost.VandeVondele at pci dot uzh.ch
2011-04-04 11:53 ` Joost.VandeVondele at pci dot uzh.ch
2011-04-04 20:22 ` tkoenig at gcc dot gnu.org
2011-04-04 20:27 ` tkoenig 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-48412-4-gOCL3TLiuL@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).