X-Authentication-Warning:	delorie.com: mail set sender to djgpp-workers-bounces using -f
Date:	Fri, 1 Jun 2007 20:08:16 -0400
Message-Id:	<200706020008.l5208GDU000561@envy.delorie.com>
From:	DJ Delorie <dj AT delorie DOT com>
To:	djgpp-workers AT delorie DOT com
In-reply-to:	<200706012331.l51NVlVt021989@brother.ludd.ltu.se> (message from
	Martin Str|mberg on Sat, 2 Jun 2007 01:31:47 +0200 (MEST))
Subject:	Re: BUGs
References:	<200706012331 DOT l51NVlVt021989 AT brother DOT ludd DOT ltu DOT se>
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> Bug 000386:

Might be the usual XP issues, requiring 2.04.

> Bug 000377:

If the COFF header is valid, it's a UPX bug.  But that doesn't mean
the header *is* valid.

> Bug 000385:
> Bug 000379:
> Bug 000378:
> Bug 000373:
> Sounds like a grx bug. I''ll close soon, if no opposition.

With a polite comment, of course.  It's not a bug, it's just that gcc
4 is more strict than gcc 3.

> Bug 000375:
> Seems to be user error. Mixing 16-bit and 32-bit code.  I''ll close
> soon, if no opposition.

Even if the user is doing something wrong, it does look like the
linker is doing something wrong also.

> Bug 000374:
> Bug in gcc.  I''ll close soon, if no opposition.

Actually, it's not a bug - it's intentional.  libstdc++ uses
i486-specific instructions to implement atomic operations, so we
(djgpp) have to decide if we're going to continue supporting i386
platforms by default.  If so, someone needs to tweak the libstdc++
configury.

- Raw text -