[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Tinycc-devel] x86-64 port
From: |
shinichiro . h |
Subject: |
Re: [Tinycc-devel] x86-64 port |
Date: |
Tue, 02 Dec 2008 03:52:17 +0900 |
User-agent: |
Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (Gojō) APEL/10.7 Emacs/22.2 (x86_64-pc-linux-gnu) MULE/5.0 (SAKAKI) |
Hi,
I pushed all of my patch into mob branch.
Most patches are trivial. Replacing Elf32 to ElfW or int to long or using
sizeof(ElfW(Dyn)) instead of 8 or something. The main change, which introduces
x86-64 support, is the following change. This change is mostly done inside
TCC_TARGET_X86_64. So, I think it doesn't make sense to split this change into
smaller pieces.
http://repo.or.cz/w/tinycc.git?a=commit;h=fa7159be0a14f713fffa1fcc692b87e69c318060
Another change I should mention is the following change. This change introduces
__builtin_frame_address(0), which is one of GCC extension. I think introducing
this extension is the simplest way to implement stdarg.h (in GCC x86-64 ABI,
integers and floating point values are passed by registers, and the address of
the last argument isn't sufficient). I think this extension is useful (e.g.,
obtain stack trace) and the change is relatively small. So, I didn't enclose
this change with #ifdef TCC_TARGET_X86_64.
http://repo.or.cz/w/tinycc.git?a=commit;h=44753fd383ba22a330d837538c237bf176b9c84f
Please tell me if there are something wrong, and I'll fix them.
Thanks,
- Re: [Tinycc-devel] x86-64 port,
shinichiro . h <=