public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/41399] [4.5 Regression] Internal error compiling fortran/intrinsic.c
Date: Wed, 02 Dec 2009 16:07:00 -0000	[thread overview]
Message-ID: <20091202160716.13978.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41399-276@http.gcc.gnu.org/bugzilla/>



------- Comment #11 from dave at hiauly1 dot hia dot nrc dot ca  2009-12-02 16:07 -------
Subject: Re:  [4.5 Regression] Internal error compiling fortran/intrinsic.c

> Why is this a regression?  Does it work with 4.4 and checking enabled?
> Does it work with current trunk and release checking?

The problem was marked as a regression as it was introduced specifically
by revision 151348.

The problem still occurs with current trunk and release checking.

Will check 4.4 with checking enabled.

Dave


-- 


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


  parent reply	other threads:[~2009-12-02 16:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-18 14:02 [Bug bootstrap/41399] New: " danglin at gcc dot gnu dot org
2009-09-18 21:00 ` [Bug bootstrap/41399] " ramana at gcc dot gnu dot org
2009-09-18 21:52 ` dave at hiauly1 dot hia dot nrc dot ca
2009-09-20 20:58 ` pinskia at gcc dot gnu dot org
2009-09-21  8:47 ` ramana at gcc dot gnu dot org
2009-09-22 14:12 ` dave at hiauly1 dot hia dot nrc dot ca
2009-10-07 15:09 ` dave at hiauly1 dot hia dot nrc dot ca
2009-10-09 17:22 ` danglin at gcc dot gnu dot org
2009-10-23 20:39 ` danglin at gcc dot gnu dot org
2009-10-24 11:54 ` rguenth at gcc dot gnu dot org
2009-11-02 14:15 ` dave at hiauly1 dot hia dot nrc dot ca
2009-11-17  0:20 ` danglin at gcc dot gnu dot org
2009-11-27 11:10 ` rguenth at gcc dot gnu dot org
2009-12-02 16:07 ` dave at hiauly1 dot hia dot nrc dot ca [this message]
2009-12-07 16:02 ` dave at hiauly1 dot hia dot nrc dot ca
2009-12-07 17:01 ` ramana at gcc dot gnu dot org
2009-12-08 11:47 ` ramana at gcc dot gnu dot org
2009-12-08 11:54 ` [Bug target/41399] " rguenth at gcc dot gnu dot org
2009-12-11  9:54 ` ramana at gcc dot gnu dot org
2010-01-28 21:55 ` steven at gcc dot gnu dot org
2010-01-28 23:04 ` steven at gcc dot gnu dot org
2010-01-28 23:23 ` steven at gcc dot gnu dot org
2010-01-28 23:48 ` [Bug target/41399] [4.5 Regression] Scheduler gives huge dependence graph compiling fortran/intrinsic.c on ARM steven at gcc dot gnu dot org
2010-01-29 10:19 ` rearnsha at gcc dot gnu dot org
2010-01-29 21:54 ` vmakarov at redhat dot com
2010-01-29 22:47 ` steven at gcc dot gnu dot org
2010-02-01 19:53 ` vmakarov at gcc dot gnu dot org
2010-02-01 22:14 ` steven 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=20091202160716.13978.qmail@sourceware.org \
    --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).