public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: reichelt@igpm.rwth-aachen.de
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, liviub@azothcorp.net,
nobody@gcc.gnu.org
Subject: Re: c/9317: Gcc 3.2 compiling long switch-case error
Date: Wed, 15 Jan 2003 13:41:00 -0000 [thread overview]
Message-ID: <20030115134111.28155.qmail@sources.redhat.com> (raw)
Synopsis: Gcc 3.2 compiling long switch-case error
State-Changed-From-To: open->feedback
State-Changed-By: reichelt
State-Changed-When: Wed Jan 15 05:41:10 2003
State-Changed-Why:
As Falk already wrote:
You did not mention the actual problem with this source. Do you get an
internal compiler error? If so, please include the error message.
Which compiler switches are you using?
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9317
next reply other threads:[~2003-01-15 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 13:41 reichelt [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-15 14:17 reichelt
2003-01-15 9:46 Falk Hueffner
2003-01-15 7:56 liviub
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=20030115134111.28155.qmail@sources.redhat.com \
--to=reichelt@igpm.rwth-aachen.de \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=liviub@azothcorp.net \
--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).