From: Geoff Keating <geoffk@geoffk.org>
To: Arnaud Charlet <charlet@ACT-Europe.FR>
Cc: Geert Bosch <bosch@gnat.com>,
Rainer Orth <ro@techfak.uni-bielefeld.de>,
Robert Dewar <dewar@gnat.com>, Richard Henderson <rth@redhat.com>,
gcc List <gcc@gcc.gnu.org>
Subject: Re: proposal: drop support for ada on tru64-alpha
Date: Tue, 31 Aug 2004 21:54:00 -0000 [thread overview]
Message-ID: <5CBA8236-FB92-11D8-8DFD-000A95B1F520@geoffk.org> (raw)
In-Reply-To: <20040831114232.A22733@dublin.act-europe.fr>
[-- Attachment #1: Type: text/plain, Size: 1632 bytes --]
On 31/08/2004, at 2:42 AM, Arnaud Charlet wrote:
>> My proposal is to disable Ada in the toplevel configure for
>> tru64-alpha, and fix the bug. I would do this in mainline; Mark may
>> choose to do this in 3.4 as well, since the bug is targeted at 3.4.3.
>>
>> Any objections? If you do have objections, are you willing and able
>> to
>> debug the problem? If so, when would you expect to be able to do it?
>
> I must say I can't find from the bugzilla comments what is the
> relationship
> between this PR and Ada builds, in particular since this PR seems to
> be g++ specific.
>
> In any case, if the issue is related to PCH on alpha-tru64, then we
> should
> disable pch on alpha-tru64, and not Ada.
No, the problem is not related to PCH on Alpha-tru64. I don't know if
PCH even works on that platform. I would characterise the problem as
"I made some change to GCC and it triggered a latent bug on
Alpha-tru64."
> In general I would object to disabling Ada on alpha-tru64 on these
> grounds,
> this will only give this PR an even lower priority.
>
> Now, I feel that I do not all the information at hand, so more
> justification
> would be needed here to help me understand the issue at hand (and once
> I understand the issue better, I'd guess there will be better
> solutions than
> simply disabling Ada).
The problem is that when you apply the patch from bugzilla, which is
not specific to either Ada, C++, or Tru64, the bootstrap failure
described in 13750 appears, a miscompare in Ada.
So, Arnaud, do you have access to an Alpha-tru64 system with Ada?
Would you be willing to investigate this bug?
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2410 bytes --]
next prev parent reply other threads:[~2004-08-31 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 18:02 Geoff Keating
2004-08-30 18:38 ` Richard Henderson
2004-08-31 10:24 ` Arnaud Charlet
2004-08-31 18:34 ` James E Wilson
2004-08-31 21:54 ` Geoff Keating [this message]
2004-09-01 7:58 ` Arnaud Charlet
2004-08-31 18:44 Richard Kenner
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=5CBA8236-FB92-11D8-8DFD-000A95B1F520@geoffk.org \
--to=geoffk@geoffk.org \
--cc=bosch@gnat.com \
--cc=charlet@ACT-Europe.FR \
--cc=dewar@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=ro@techfak.uni-bielefeld.de \
--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).