Hi Ben,
is this still a probkem with gij 3.4 or 4.0? If so, could you try to
prepare a test case so we can forward it upstream?
--
Falk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> well, I still could reenable building gij-3.2 / gcj-3.2, if that's
> necessary for the sarge release.
I don't have any reason to believe that this bug is new to gcj-3.3 - the
only reason it wasn't spotted until now was kaffe+jython used to be
broken for other reasons. So it's entirely possible
Hi.
> Ben, please could you update the status regarding newer gcj-3.3 /
> gcc-snapshot packages?
Still broken with both gcj 4:3.3.2-2 and gcc-snapshot 20040118-1.
Ben.
> Ben, please could you update the status regarding newer gcj-3.3 /
> gcc-snapshot packages?
Yep, sorry - got quite a bit busy these last few weeks. I will get to
it.
b.
Ben, please could you update the status regarding newer gcj-3.3 /
gcc-snapshot packages?
Ben Burton writes:
>
> Hi.
>
> > please could you provide a reduced testcase and/or name the file
> > beeing miscompiled?
>
> This might or might not be an easy thing, and I'm about to leave for two
> weeks where I will quite probably be down to email and nothing more. So
> I can do this but it
Hi.
> please could you provide a reduced testcase and/or name the file
> beeing miscompiled?
This might or might not be an easy thing, and I'm about to leave for two
weeks where I will quite probably be down to email and nothing more. So
I can do this but it might be some time.
> what's the st
Ben,
please could you provide a reduced testcase and/or name the file
beeing miscompiled?
what's the status using gcc-3.2 and gcc-snapshot regarding the
miscompilation?
8 matches
Mail list logo
