Re: g++.eh/unwind1.C

[Franz Sirl <Franz.Sirl-kernel@lauterbach.com>]

At 16:53 27.04.99 , Andrew Macleod wrote:
>>> >
>>> >Shortly after we branch the new release of egcs I think. There's no real
>>> >reason it can't go in. Have you had to make any changes to it, or
>>> >has it been working fine?
>>>
>>> Hmm, I thought this was scheduled for 1.2? At least Jeff had it on the 
>>> list
>>> he posted on the egcs mailinglist. The snapshot you sent me works fine 
>>> with
>>> both 1.1.2 and the current mainline, this means noone has reported a
>>> problem related to it (and egcs-1.1.2) for the whole redhat-6.0 stuff +
>>> some big extra packages like mozilla, ddd, etc. If it's too late for 1.2
>>> now, I would appreciate if you could send me a new snapshot of your EH 
>>> stuff
>
>Hmm, this would be my fault since I didn't realize it was on the
>list and needed to go in. I haven't actually looked at it since I gave it to
>you (I've been sidetracked from EH stuff for a while now).
>
>I guess its Jeffs call on whether its too late, it seems to be pretty
>heavily used by you guys, so its reasonably tested... If he does want
>it to go it, your probably in a better spot to check it in since
>you actively use it.  (And you may have had to add to it)

Damned :-), that's just the situation I wanted to avoid with egcs-1.2. Jeff 
probably won't checkin this patch now that feature freeze is announced. 
This means I have to maintain it as an extra patch again during the whole 
1.2.x cycle :-(.
All the other stuff I have pending for 1.2 are some minor bugfixes in the 
rs6000 backend I will post soon and a solution for the varargs problem on PPC.

Franz.