public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/35475] [4.2 Regression] gfortran fails to compile valid code with ICE erro in fold-const.c
Date: Wed, 05 Mar 2008 17:55:00 -0000	[thread overview]
Message-ID: <20080305175501.9866.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35475-15854@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from burnus at gcc dot gnu dot org  2008-03-05 17:55 -------
Thanks for the report.  I can reproduce the problem with 4.2.3, however, it
seems to be fixed in GCC/gfortran 4.3.0rc2 (and 4.4.0) - and as Daniel noted it
used to worked with 4.1.3.

GCC 4.3.0 is supposted to be released at the end of this week (currently, we
have release candidate 2). Any chance that you could upgrade your GCC and try
again? Despite being a regression, I'm not sure it will be fixed soon as we
need to find the fix first.

Binaries and a description how to build GCC from source can be found at
http://gcc.gnu.org/wiki/GFortranBinaries Depending on your Linux distribution,
they might have already experimental GCC 4.3.0 packages somewhere.
Changelog: http://gcc.gnu.org/gcc-4.3/changes.html


-- 

burnus at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to fail|4.2.4                       |4.1.3 4.2.2
      Known to work|4.1.2 4.3.0 4.4.0           |4.3.0 4.4.0


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


  parent reply	other threads:[~2008-03-05 17:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05 17:26 [Bug fortran/35475] New: gfortran fails to compile valid code with ICE segfault s dot binnie at ucl dot ac dot uk
2008-03-05 17:27 ` [Bug fortran/35475] " s dot binnie at ucl dot ac dot uk
2008-03-05 17:34 ` [Bug fortran/35475] gfortran fails to compile valid code with ICE erro in fold-const.c s dot binnie at ucl dot ac dot uk
2008-03-05 17:52 ` [Bug fortran/35475] [4.2 Regression] " dfranke at gcc dot gnu dot org
2008-03-05 17:55 ` burnus at gcc dot gnu dot org [this message]
2008-03-05 18:00 ` pinskia at gcc dot gnu dot org
2008-03-05 21:43 ` pault at gcc dot gnu dot org
2008-03-11 10:52 ` fxcoudert at gcc dot gnu dot org
2008-03-11 12:04 ` pinskia at gcc dot gnu dot org
2008-03-12  4:12 ` jvdelisle at gcc dot gnu dot org
2008-03-14  3:14 ` jvdelisle at gcc dot gnu dot org
2008-03-14  3:18 ` jvdelisle 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=20080305175501.9866.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).