Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
Message-ID: <20011215042127.43604.qmail@web14507.mail.yahoo.com>
Date: Sat, 15 Dec 2001 15:21:27 +1100 (EST)
From: =?iso-8859-1?q?Danny=20Smith?= <danny_r_smith_2001 AT yahoo DOT co DOT nz>
Subject: I386_PE_STRIP_ENCODING
To: cygwin-apps <cygwin-apps AT cygwin DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi 
Recent patch to GCC fixes one problem with asm specified names and
dllexport. However, using asm specified names with dllimport will still
create assembler error. Is the following testcase (which fails now, because
names like @i.__imp__*foo, don't get stripped properly) realistic?  I have
a patch that will fix, but  affects code in both i386_pe_mark_dllimport in
winnt.c (don't add __imp_ yet) and cygwin.h (do it in ASM_OUTPUT_LABELREF).
 But first, does failure of the following testcase represent anything to
worry about?

Danny

 /* Modified from gcc.dg/asm-fs-1.c
   Origin: <hp AT bitrange DOT com>
   Make sure we do not get spurious '*' characters in section names or
   elsewhere, with asm-specified names.
   Special test for targets supporting dllimport
*/

/* { dg-do compile } */
/* { dg-options "-ffunction-sections -fdata-sections" } */


extern int __attribute__((dllimport)) foobar asm ("_baz");

int foo(void) asm ("_bar");

int foo(void) {return foobar;}


/* { dg-final { scan-assembler-not "\\*_bar" } } */
/* { dg-final { scan-assembler-not "\\*_baz" } } */



http://greetings.yahoo.com.au - Yahoo! Greetings
- Send your festive greetings online!