Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3BA936C1.5000406@ece.gatech.edu>
Date: Wed, 19 Sep 2001 20:22:25 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713
X-Accept-Language: en-us
MIME-Version: 1.0
To: Danny Smith <danny_r_smith_2001 AT yahoo DOT co DOT nz>
CC: cygwin AT cygwin DOT com
Subject: Re: binutils.README
References: <20010920000226 DOT 64316 DOT qmail AT web14505 DOT mail DOT yahoo DOT com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Danny Smith wrote:


> One omission in the KNOWN ISSUE #0 ("variable '<var>' can't be
> auto-imported.") is that [unsigned] long long variables can't be
> auto-imported, as reported here:
> 
> http://sources.redhat.com/ml/cygwin/2001-09/msg00843.html
> 
> To see the problem, change global_int_var in dll-helpers-0.2.8/c to
> long long and look at the assembler code for printf-ing the variable.  
>  

The original reporter provided so few details in that "report" that I 
tossed the "report" in the bit bucket.  It wasn't worth my time to 
investigate it.  You have provided slightly more information, but not 
much more.  You know, there's no law against putting some of that 
assembler code in your message, rather than telling me to go 
edit/recompile some file somewhere....

Somebody (and it ain't gonna be me) needs to investigate
   a) why long long is treated as a complex data type (if that is indeed 
the case)
   b) if so, then how "this" bug is the same as the other one.  Paul 
squashed that other bug at the source -- "if a .o file contains an 
assembler instruction in which there is a nonzero addend for a 
dll-auto-imported variable, then throw an error".  Either (a) "long 
long" is a totally diferent bug, or (b) somehow Paul's check for this 
explicit error condition is being fooled.  Why? How?


--Chuck



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/