From: Jan Hubicka <jh@suse.cz>
To: Mark Mitchell <mark@codesourcery.com>
Cc: Zack Weinberg <zack@codesourcery.com>,
Geert Bosch <bosch@gnat.com>, Roger Sayle <roger@eyesopen.com>,
Arnaud Charlet <charlet@ACT-Europe.FR>,
gcc@gcc.gnu.org, Jan Hubicka <jh@suse.cz>
Subject: Re: Ada updates frozen
Date: Mon, 03 Nov 2003 09:07:00 -0000 [thread overview]
Message-ID: <20031103090705.GI13705@kam.mff.cuni.cz> (raw)
In-Reply-To: <1067810604.28119.34.camel@doubledemon.codesourcery.com>
> On Sun, 2003-11-02 at 11:40, Zack Weinberg wrote:
> > Geert Bosch <bosch@gnat.com> writes:
> >
> > > On Nov 2, 2003, at 9:11 AM, Roger Sayle wrote:
> > >> I think you are well within your rights to invoke the "patch reversion"
> > >> rule and start the 48-hour clock ticking. If x86/IA-64 bootstrap can't
> > >> be restored on mainline by Tuesday the patches should be pulled, or the
> > >> problematic aspects temporarily disabled.
> > >
> > > Given the significant problems this patch introduces, I would
> > > appreciate it if Jan would revert this patch, until the regressions
> > > are resolved.
> > >
> > > Richard Kenner already implemented the required changes for gigi
> > > (the Ada front end/back end interface), but these are on hold now.
> > > It will be a few days before the remaining front end work is
> > > finished.
> >
> > I am presently testing a patch which reverts GET_MODE_BITSIZE to its
> > original meaning (i.e. GET_MODE_SIZE * BITS_PER_UNIT) and introduces
> > a new macro GET_MODE_PRECISION which is used in a very few places
> > (notably mode_for_size). I think this should be an adequate bandage
> > to restore Ada bootstrap so that work can go forward on the complete
> > solution. However, there are still some issues with the patch, so I
> > cannot provide it just yet, but I intend to have them worked out by
> > the end of the day.
>
> I'm too far behind on email to understand what the reference to Jan's
> patch is. I do know about Zack's patch. So, this email refers to
> Zack's patch, but not Jan's patch.
My patch does exactly the same Zack did for IA-64. x86-64 has exactly
symetric behaviour wrt long double and __float128 as IA-64 ABI has. I
really hope that if Zack works out the issues with Ada, it will
automatically fix the x86-64 part too. I can do any help with fixing
the bug if Zack figure out how to make me involved in his effort.
Honza
next prev parent reply other threads:[~2003-11-03 9:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-02 11:44 Arnaud Charlet
2003-11-02 14:17 ` Roger Sayle
2003-11-02 18:28 ` Geert Bosch
2003-11-02 19:40 ` Zack Weinberg
2003-11-02 22:03 ` Mark Mitchell
2003-11-03 9:07 ` Jan Hubicka [this message]
2003-11-03 9:11 ` Zack Weinberg
2003-11-03 11:52 ` Jan Hubicka
2003-11-03 12:02 ` Jan Hubicka
2003-11-03 14:48 ` Jan Hubicka
2003-11-02 18:12 Robert Dewar
2003-11-02 19:41 Richard Kenner
2003-11-02 19:47 ` Zack Weinberg
2003-11-02 20:09 Richard Kenner
2003-11-02 21:40 ` Zack Weinberg
2003-11-03 0:56 Richard Kenner
2003-11-03 1:42 ` Zack Weinberg
2003-11-03 7:59 ` Arnaud Charlet
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=20031103090705.GI13705@kam.mff.cuni.cz \
--to=jh@suse.cz \
--cc=bosch@gnat.com \
--cc=charlet@ACT-Europe.FR \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=roger@eyesopen.com \
--cc=zack@codesourcery.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).