public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/16499] ICE with character declaration
Date: Fri, 16 Jul 2004 12:58:00 -0000	[thread overview]
Message-ID: <20040716125835.14778.qmail@sourceware.org> (raw)
In-Reply-To: <20040712155440.16499.c.lemmen@fz-juelich.de>


------- Additional Comments From reichelt at gcc dot gnu dot org  2004-07-16 12:58 -------
On 16 Jul, c dot lemmen at fz-juelich dot de wrote:
> Reopened, both testcases keep producing ICE with current gfortran:
> 
> gcc version 3.5.0 20040715 (experimental)
> 
> (am I missing something here?)

Probably ;-)

The patches for the PR went into CVS yesterday afternoon (15:02:17 UTC
to be precise). And you are using a compiler built yesterday. Are you
sure the patches really made it into your compiler?

I doubt that, since the bug is fixed for me with a compiler built tonight.
Could you please retry with a more recent built?


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |WAITING


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


  parent reply	other threads:[~2004-07-16 12:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-12 15:54 [Bug fortran/16499] New: ice-on-valid-code, seg-fault c dot lemmen at fz-juelich dot de
2004-07-12 15:56 ` [Bug fortran/16499] " c dot lemmen at fz-juelich dot de
2004-07-12 16:21 ` [Bug fortran/16499] ICE with character declaration reichelt at gcc dot gnu dot org
2004-07-12 19:30 ` pinskia at gcc dot gnu dot org
2004-07-16  9:53 ` c dot lemmen at fz-juelich dot de
2004-07-16 12:58 ` reichelt at gcc dot gnu dot org [this message]
2004-07-19  8:07 ` c dot lemmen at fz-juelich dot de

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=20040716125835.14778.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).