public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Matthias Klose <doko@klose.in-berlin.de>
To: gcc-gnats@gcc.gnu.org, debian-gcc@lists.debian.org
Cc: "Dr. David Alan Gilbert" <gilbertd@treblig.org>
Subject: other/3998: Internal error: Segmentation fault
Date: Sat, 11 Aug 2001 00:56:00 -0000 [thread overview]
Message-ID: <E15VTUc-0001JN-00@gate.local> (raw)
>Number: 3998
>Category: other
>Synopsis: Internal error: Segmentation fault
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sat Aug 11 00:56:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: "Dr. David Alan Gilbert" <gilbertd@treblig.org>
>Release: 3.0 (Debian GNU/Linux)
>Organization:
The Debian project
>Environment:
System: Debian GNU/Linux (testing/unstable)
Architecture: alpha
host: alpha-linux
>Description:
[ Reported to the Debian BTS as report #106927.
Please CC 106927-quiet@bugs.debian.org on replies.
Log of report can be found at http://bugs.debian.org/106927 ]
gcc-3.0 -v --help
ends with:
-O[number] Set optimisation level to [number]
-Os Optimise for space rather than speed
cc1: Internal error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions.
For bug reporting instructions, please see:
<URL: http://www.gnu.org/software/gcc/bugs.html >
For Debian GNU/Linux specific bugs,
please see /usr/share/doc/debian/bug-reporting.txt.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-08-11 0:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-11 0:56 Matthias Klose [this message]
2001-08-18 9:07 rodrigc
2001-11-15 13:36 rodrigc
2001-11-15 19:56 rodrigc
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=E15VTUc-0001JN-00@gate.local \
--to=doko@klose.in-berlin.de \
--cc=debian-gcc@lists.debian.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gilbertd@treblig.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).