Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
X-Authentication-Warning:	mercury.xraylith.wisc.edu: khan owned process doing -bs
Date:	Tue, 15 Jun 1999 15:22:13 -0500 (CDT)
From:	Mumit Khan <khan AT xraylith DOT wisc DOT EDU>
To:	cygwin AT sourceware DOT cygnus DOT com
Subject:	-fpic/PIC clarification [Re: as.exe: bfd assertion fail... ]
In-Reply-To:	<199906151721.MAA09768@mercury.xraylith.wisc.edu>
Message-ID:	<Pine.LNX.3.96.990615151501.10360M-100000@mercury.xraylith.wisc.edu>
MIME-Version:	1.0

On Tue, 15 Jun 1999, Mumit Khan wrote:

> This was a bug caused by -fPIC, which is unnecessary on x86-win32 where 
> all code is position independent. This has been fixed for a while now
> (I released egcs-1.1.2 Cygwin/Mingw binaries March 17), so I suggest 
> you upgrade your compiler. Quite a few other problems found in egcs-1.1 
> are fixed 1.1.2 as well.
>   
>   http://www.xraylith.wisc.edu/~khan/software/gnu-win32/
> 

Donn Terry just sent me a note pointing out my incorrect statement. What 
I meant to say was that -fPIC/pic in the usual sense conflicts with the 
MS DLL design, and makes no sense on x86-win32 (except perhaps on Interix).
It involves the issue about static vs dynamic fixup of shared libraries
and so on. Recent GCC versions simply ignore the flag, along with a 
warning, instead of silently creating bad code.

To recap, DO NOT use -fPIC/pic with egcs-1.1 if you don't want bad code.
With egcs-1.1.2 and newer, GCC will ignore this flag, ie, no bad code, 
and tell you that it's being ignored.

Apologies about the confusion.

Regards,
Mumit



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -