public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/46755] ICE: in calc_dfs_tree, at dominance.c:395 with -O
Date: Wed, 01 Dec 2010 23:02:00 -0000	[thread overview]
Message-ID: <bug-46755-4-55Tc90eiXa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46755-4@http.gcc.gnu.org/bugzilla/>

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

Zdenek Sojka <zsojka at seznam dot cz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |ice-on-valid-code

--- Comment #1 from Zdenek Sojka <zsojka at seznam dot cz> 2010-12-01 23:02:46 UTC ---
It crashes with -std=legacy as well:

$ gfortran -O pr46755.f -std=legacy
pr46755.f: In function 'MAIN__':
pr46755.f:28:0: internal compiler error: in calc_dfs_tree, at dominance.c:395
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.


  reply	other threads:[~2010-12-01 23:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 22:46 [Bug rtl-optimization/46755] New: " zsojka at seznam dot cz
2010-12-01 23:02 ` zsojka at seznam dot cz [this message]
2010-12-01 23:09 ` [Bug rtl-optimization/46755] " steven at gcc dot gnu.org
2010-12-03  8:25 ` zsojka at seznam dot cz
2010-12-17 20:40 ` steven at gcc dot gnu.org
2010-12-21 14:55 ` steven at gcc dot gnu.org
2010-12-21 20:17 ` jakub at gcc dot gnu.org
2010-12-21 20:55 ` steven at gcc dot gnu.org
2011-01-02 20:48 ` regehr at cs dot utah.edu
2011-01-02 23:13 ` hjl.tools at gmail dot com
2011-01-03 10:19 ` jakub 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-46755-4-55Tc90eiXa@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).