public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rwgk@yahoo.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/10922] [Darwin] Internal error: Illegal instruction (program cc1plus)
Date: Mon, 26 May 2003 04:32:00 -0000 [thread overview]
Message-ID: <20030526042554.29164.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030522014038.10922.rwgk@yahoo.com>
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10922
------- Additional Comments From rwgk@yahoo.com 2003-05-26 04:25 -------
All the code involved is unrestricted open source. However, to reproduce the
bug you'd need to install Python 2.3b1 (also open source) as root. If that's
acceptable I'd be happy to create a self-contained source code bundle incl.
instructions. I think it would be worth it because it brings to light some
other bugs:
- Undefined symbols while linking that (sometimes) go away if the code is
rearranged.
- Segmentation faults and bus errors when using -O3 instead of -O0.
You could also use our code to verify that the gcc 3.3 optimizer is broken
under Redhat 8 (where you could use the Python that comes with the OS).
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next parent reply other threads:[~2003-05-26 4:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030522014038.10922.rwgk@yahoo.com>
2003-05-26 4:32 ` rwgk@yahoo.com [this message]
2003-05-26 6:34 ` dhazeghi@yahoo.com
2003-05-26 14:43 ` pinskia@physics.uc.edu
2003-05-27 6:27 ` rwgk@yahoo.com
2003-06-02 21:01 ` dhazeghi@yahoo.com
2003-06-02 22:55 ` bangerth@dealii.org
2003-06-03 1:34 ` bangerth@dealii.org
2003-06-03 1:36 ` bangerth@dealii.org
2003-06-22 18:55 ` pinskia at physics dot uc dot edu
2003-06-25 16:53 ` rwgk at yahoo dot com
2003-06-25 18:32 ` bangerth at dealii dot org
2003-07-02 14:40 ` nathan at gcc dot gnu dot org
2003-07-05 19:36 ` dhazeghi at yahoo dot com
2003-07-10 2:20 ` pinskia at physics dot uc dot edu
2003-05-22 14:15 bangerth@dealii.org
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=20030526042554.29164.qmail@sources.redhat.com \
--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).