public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Falk Schramm" <falkschramm@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/6397: GCC 3.0 crashes compiling Linux kernel 2.4.18
Date: Sun, 21 Apr 2002 16:06:00 -0000 [thread overview]
Message-ID: <20020421230601.25431.qmail@sources.redhat.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]
The following reply was made to PR c/6397; it has been noted by GNATS.
From: =?iso-8859-1?q?Falk=20Schramm?= <falkschramm@yahoo.com>
To: jakub@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: c/6397: GCC 3.0 crashes compiling Linux kernel 2.4.18
Date: Mon, 22 Apr 2002 00:15:29 +0200 (CEST)
That was a fast answer!
I used the GCC 3.0 release (20010617).
Thanks a lot,
Falk
--- jakub@gcc.gnu.org schrieb:
> Synopsis: GCC 3.0 crashes compiling Linux kernel 2.4.18
>
> State-Changed-From-To: open->feedback
> State-Changed-By: jakub
> State-Changed-When: Sun Apr 21 13:50:36 2002
> State-Changed-Why:
> I can reproduce this with 3.0.2 20011002, but cannot
> reproduce it with 3.0.4 nor 3.1 20020421 (prerelease).
> By GCC 3.0 do you mean really 3.0 release, or some
> other snapshot/release from 3.0 branch? If the former,
> you should definitely upgrade.
>
>
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6397
__________________________________________________________________
Gesendet von Yahoo! Mail - http://mail.yahoo.de
Sie brauchen mehr Speicher für Ihre E-Mails? - http://premiummail.yahoo.de
next reply other threads:[~2002-04-21 23:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-21 16:06 Falk Schramm [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-24 20:15 rodrigc
2002-04-21 13:50 jakub
2002-04-21 12:46 falkschramm
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=20020421230601.25431.qmail@sources.redhat.com \
--to=falkschramm@yahoo.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).