From: Marc Espie <espie@schutzenberger.liafa.jussieu.fr>
To: Bernd Schmidt <bernds@redhat.com>
Cc: Artur Grabowski <art@openbsd.org>,
Jakub Jelinek <jakub@redhat.com>,
gcc@gcc.gnu.org
Subject: Re: [jakub@redhat.com: Re: 2.95.4, sparc64 issues ?]
Date: Mon, 10 Sep 2001 09:45:00 -0000 [thread overview]
Message-ID: <20010910184528.A10185@schutzenberger.liafa.jussieu.fr> (raw)
In-Reply-To: <Pine.LNX.4.33.0109101655330.16107-100000@host140.cambridge.redhat.com>
On Mon, Sep 10, 2001 at 04:58:55PM +0100, Bernd Schmidt wrote:
> Well, a justification of "Seems to allow libstdc++ to at least compile"
> doesn't make me confident that there has been much thought put into issues
> like, "will it actually work", or "could it be harmful on other targets".
> That makes it unacceptable for a stable branch.
The `could it be harmful on other targets' part is OBVIOUS.
I mean, adding a test to handle some unhandled case RIGHT IN FRONT OF AN
abort() is a complete NO-BRAINER.
As for the rest, yep, I think I want discussion about that.
Specifically, if we need some other sparc64 patch, what is that sub-reg
patch. Where can I get a version that does more or less apply to 2.95.3 ?
I am quite willing to do some testing on OpenBSD targets, and to release
a compiler that would work for us, even if it includes non-standard
patches.
Currently, gcc 3.0.1 is not an option. A gcc 3.x will probably be an option
in a year time, when it becomes somewhat usable.
We can't ship a compiler that miscompiles kde. We can't ship a compiler
that doesn't even compile OpenBSD i386 pic code correctly (no news on my
GOT/GOTOFF problems, rth ?).
next prev parent reply other threads:[~2001-09-10 9:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010910155832.A12662@schutzenberger.liafa.jussieu.fr>
2001-09-10 8:48 ` Artur Grabowski
2001-09-10 8:59 ` Bernd Schmidt
2001-09-10 9:45 ` Marc Espie [this message]
2001-09-10 9:53 ` Jakub Jelinek
2001-09-10 9:58 ` Marc Espie
2001-09-10 10:01 ` Jakub Jelinek
2001-09-10 10:07 ` Marc Espie
2001-09-10 10:12 ` Jakub Jelinek
2001-09-10 10:02 ` David Edelsohn
2001-09-10 14:23 ` Artur Grabowski
2001-09-10 18:18 ` openbsd gotoff workaround Richard Henderson
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=20010910184528.A10185@schutzenberger.liafa.jussieu.fr \
--to=espie@schutzenberger.liafa.jussieu.fr \
--cc=art@openbsd.org \
--cc=bernds@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@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).