public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/20957] Error while compiling kernel
Date: Mon, 11 Apr 2005 21:34:00 -0000 [thread overview]
Message-ID: <20050411213402.360.qmail@sourceware.org> (raw)
In-Reply-To: <20050411212950.20957.jp.pozzi@izzop.net>
--
What |Removed |Added
----------------------------------------------------------------------------
Severity|critical |normal
Component|c |target
Keywords| |ice-on-valid-code
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20957
next prev parent reply other threads:[~2005-04-11 21:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-11 21:29 [Bug c/20957] New: " jp dot pozzi at izzop dot net
2005-04-11 21:34 ` pinskia at gcc dot gnu dot org [this message]
2005-04-11 21:42 ` [Bug target/20957] " pinskia at gcc dot gnu dot org
2005-07-01 19:30 ` pinskia at gcc dot gnu dot org
2005-07-01 21:53 ` jp dot pozzi at izzop dot net
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=20050411213402.360.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).