X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <49FEE832.2030806@gmail.com>
Date: Mon, 04 May 2009 14:05:54 +0100
From: Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] [1.7] pl-0.10.2-1 - the Parma Polyhedra Library
References: <announce DOT 49F9A229 DOT 1070908 AT gmail DOT com> <49FBF62E DOT 3060904 AT cs DOT unipr DOT it> <49FC71B7 DOT 3030000 AT cwilson DOT fastmail DOT fm> <49FC7EF9 DOT 4050908 AT gmail DOT com> <49FCACE6 DOT 4000104 AT cwilson DOT fastmail DOT fm> <49FCE65C DOT 7040409 AT gmail DOT com> <49FCE88D DOT 6040709 AT cwilson DOT fastmail DOT fm> <49FD6393 DOT 5040801 AT gmail DOT com> <49FDD3FF DOT 7020007 AT cwilson DOT fastmail DOT fm>
In-Reply-To: <49FDD3FF.7020007@cwilson.fastmail.fm>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Charles Wilson wrote:
> Dave Korn wrote:
> 
>>   I'm not sure.  It's the compiler that knows what it needs, which is the same
>> regardless of binutils' preferences, I'm leaning toward the idea that it
>> should be in the linker specs for the benefit of anyone using older binutils.
> 
> The only reason the compiler NEEDS auto-import is to link against the
> shared runtime libraries, since they are not declspec(dllimport)
> decorated, right?  

  That's the only reason the compiler would need auto-import itself, but there
are an awful lot of user libraries out there that need it too, and it does
seem to be very common that that warning flies past in someone's build log and
they don't notice it.

> However, if you're linking against the static
> runtimes, then the compiler doesn't care, and it should be up to the user.
> 
> However, if the compiler unconditionally forces enable-auto-import in
> the specs file, then the end-user has no choice (or, MIGHT have no
> choice depending on the vagarious/order-of-precedence of argument parsing).
> 
> Maybe the right compromise here is for gcc-4's specs to force
> enable-auto-import when linking against the shared runtimes, but to
> leave it up to the default binutils behavior for static?

  Hmm, you raise a point.  We should probably only enable it by default in ld
when -Bdynamic.  And yes, for the compiler's specs that would equate to
passing it down when using shared runtimes.

    cheers,
      DaveK

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/