This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Problem w/PIC and C++ exceptions in 2.95 on IA-32
- To: jbuck at synopsys dot COM
- Subject: Re: Problem w/PIC and C++ exceptions in 2.95 on IA-32
- From: Marc Espie <espie at quatramaran dot ens dot fr>
- Date: Thu, 20 Jan 2000 19:35:44 +0100
- Cc: egcs at egcs dot cygnus dot com
- Organization: Ecole Normale Superieure de Paris
- References: <20000120100408.E1547@cygnus.com>
In article <867j5t$hh2$1@clipper.ens.fr> you write:
>> > > 2000-01-03 Anthony Green <green@cygnus.com>
>> > >
>> > > * config/i386/i386.md (builtin_setjmp_receiver): New pattern.
>> > > Restore the pic register if required.
>On Thu, Jan 20, 2000 at 09:37:25AM -0800, David O'Brien wrote:
>> > Would it *PLEASE* :-)) be possible to commit it to the 2.95 branch?
>Richard Henderson writes:
>> Done.
>This only matters if we plan on issuing 2.95.3. Do we have sufficient
>minor bugs to justify that?
I can understand not wanting to ship `release of the day', but this
single bug does look obnoxious enough to justify 2.95.3.
Of course, this does depend heavily on what plans there are to go ahead
and manufacture a new release in the reasonable future... so far, I haven't
seen any hint that things are going to stabilize over the next three months.
Upgrades should go like this, in my opinion: decide on a minimum interval
between releases (say, two months).
Each time the interval has elapsed, if you've got any real bugs, then you
should crank out a new release.
I don't know about you, but a bug which thoroughly breaks any real world
C++ application on any i386 platform with sj-lj exceptions is real enough.