Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Dave Korn" To: Subject: RE: Assembler problem while trying to integrate D iompiler in GCC suite Date: Tue, 7 Jun 2005 18:54:41 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <42A57DF4.3030705@familiehaase.de> Message-ID: ----Original Message---- >From: Gerrit P. Haase >Sent: 07 June 2005 11:59 > Hi all, > > I'm trying to integrate the D frontend for GCC in the GCC 3.4.4 release, > What is new in the source regarding this problem is this patch which > gives me the error cited below: > diff -cr d-0.12/d-codegen.cc d-0.12.1/d-codegen.cc > + #if D_GCC_VER >= 34 > + #ifdef ASM_OUTPUT_DEF > + static int thunk_labelno; > + > + /* Create a static alias to function. */ > + > + static tree > + make_alias_for_thunk (tree function) > + { > + tree alias; > + char buf[256]; > + > + #if defined (TARGET_IS_PE_COFF) > + if (DECL_ONE_ONLY (function)) > + return function; > + #endif > + > + ASM_GENERATE_INTERNAL_LABEL (buf, "LTHUNK", thunk_labelno); > Gives me this error now: > > $ /gcc/gcc-3.4.4/gcc-3.4.4-1/.build/gcc/gdc -save-temps > -B/gcc/gcc-3.4.4/gcc-3.4.4-1/.build/gcc/ -B/usr/i686-pc-cygwin/bin/ > -B/usr/i686-pc-cy> > gdc: warning: -pipe ignored because -save-temps specified > socketstream.s: Assembler messages: > socketstream.s:1416: Error: Local symbol `LTHUNK0' can't be equated to > undefined symbol `__D3std6stream6Stream9readExactFPvkZv' So what happens if you use a label that doesn't begin with an 'L'? Frex > + ASM_GENERATE_INTERNAL_LABEL (buf, "__LTHUNK", thunk_labelno); cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/