From: Randolph Chung <randolph@tausq.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] gcc-3.3 and c++
Date: Tue, 13 May 2003 11:18:05 -0700 [thread overview]
Message-ID: <20030513181805.GF548@tausq.org> (raw)
In-Reply-To: <200305131753.h4DHrmPJ007374@hiauly1.hia.nrc.ca>
> As I mentioned, the 3.2 branch is closed for bug fixes. The failure
> doesn't occur with 3.3. It has a number of -march=2.0 fixes. The
> problem could be C++ related as well. There are a huge number of C++
> fixes in 3.3 relative to 3.3.
Reading this inspired us to try compiling the 'menu' debian package
with g++-3.3. Historically this package has been very problematic on
hppa because of its use of exceptions. It's been broken for a very long
time (couple years?).... but with latest g++-3.3 it actually compiles
and works!!
Dave, many many thanks again for all your work on gcc.
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next prev parent reply other threads:[~2003-05-13 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 16:53 [parisc-linux] gcc and -march=2.0 flag bug Guy Martin
2003-05-13 17:53 ` John David Anglin
2003-05-13 18:03 ` Guy Martin
2003-05-13 18:18 ` Randolph Chung [this message]
2003-05-13 19:16 ` [parisc-linux] gcc-3.3 and c++ John David Anglin
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=20030513181805.GF548@tausq.org \
--to=randolph@tausq.org \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@lists.parisc-linux.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.