public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: aj@suse.de, dylan@q-games.com, gcc-bugs@gcc.gnu.org,
gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, rth@redhat.com
Subject: Re: c++/6144: segment-faults when using sse extensions and ia32 g++
Date: Thu, 12 Dec 2002 07:38:00 -0000 [thread overview]
Message-ID: <20021212153821.31855.qmail@sources.redhat.com> (raw)
Synopsis: segment-faults when using sse extensions and ia32 g++
State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Thu Dec 12 07:38:20 2002
State-Changed-Why:
I can confirm the SegFault on Linux (as have others before)
with 3.3 CVS from last week. However, I don't understand
enough of the matter so say more about this.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6144
next reply other threads:[~2002-12-12 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-12 7:38 bangerth [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-08 23:13 bangerth
2002-04-03 17:16 Dylan Cuthbert
2002-04-03 10:06 Tim Prince
2002-04-02 23:36 Dylan Cuthbert
2002-04-02 17:46 dylan
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=20021212153821.31855.qmail@sources.redhat.com \
--to=bangerth@dealii.org \
--cc=aj@suse.de \
--cc=dylan@q-games.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
--cc=rth@redhat.com \
/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).