[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tinycc-devel] Support for hidden symbols?

From: Michael Matz
Subject: Re: [Tinycc-devel] Support for hidden symbols?
Date: Thu, 17 Apr 2014 17:17:01 +0200 (CEST)
User-agent: Alpine 2.00 (LNX 1167 2008-08-23)


On Sun, 13 Apr 2014, Austin English wrote:

> I expected that wine wouldn't immediately work, I'm doing it for the
> curiosity factor.

Okay :)

> The next problem is:
> make[1]: Entering directory `/home/austin/src/wine-tcc/dlls/acledit'
> /home/austin/tcc/bin/i386-linux-gnu-tcc -m32 -c -I. -I. -I../../include
> -I../../include  -D__WINESRC__  -D_REENTRANT -fPIC   -g  -o main.o main.c
> ../../tools/winegcc/winegcc -m32 -B../../tools/winebuild --sysroot=../..
> -shared ./acledit.spec main.o           -o acledit.dll.so
> ../../libs/port/libwine_port.a
> acledit.UgAqPb.s:14: error: unknown assembler directive
> '.L__wine_spec_rva_base'

Yep, tccasm doesn't currently accept the AT&T syntax of local labels.  
Well, I could add that as well, but the question will be where to stop?  
wine emits assembler code for an AT&T (e.g. the GNU) assembler, and tccasm 
is not such one.  There will be many more things missing.  All the .cfi 
directives, section markers, the special syntax for marking operands with 
certain relocations.  It would be easier if you would force wine to use 
the GNU assembler at least for assembler input.  The C sources can then 
still be compiled with TCC (and presumably that's where your couriosity 


reply via email to

[Prev in Thread] Current Thread [Next in Thread]