From: nathan@gcc.gnu.org
To: debian-gcc@lists.debian.org, gcc-bugs@gcc.gnu.org,
gcc-prs@gcc.gnu.org, nathan@gcc.gnu.org, nobody@gcc.gnu.org,
parisc-linux@lists.parisc-linux.org, tausq@debian.org
Subject: [parisc-linux] Re: c++/10438: [3.3 regression] [hppa] Segfault when building jade
Date: 20 Apr 2003 17:49:24 -0000 [thread overview]
Message-ID: <20030420174924.30228.qmail@sources.redhat.com> (raw)
Synopsis: [3.3 regression] [hppa] Segfault when building jade
Responsible-Changed-From-To: unassigned->nathan
Responsible-Changed-By: nathan
Responsible-Changed-When: Sun Apr 20 17:49:23 2003
Responsible-Changed-Why:
fixed
State-Changed-From-To: open->closed
State-Changed-By: nathan
State-Changed-When: Sun Apr 20 17:49:23 2003
State-Changed-Why:
dup of 10405
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10438
next reply other threads:[~2003-04-20 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-20 17:49 nathan [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-20 17:49 [parisc-linux] Re: c++/10438: [3.3 regression] [hppa] Segfault when building jade nathan
2003-04-19 15:05 Giovanni Bajo
2003-04-19 15:05 Giovanni Bajo
2003-04-19 15:30 ` Randolph Chung
2003-04-19 15:30 ` Randolph Chung
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=20030420174924.30228.qmail@sources.redhat.com \
--to=nathan@gcc.gnu.org \
--cc=debian-gcc@lists.debian.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=tausq@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.