Update, error comes from cast.
Using
res = (p != 0x12345678ABCD000F );
return res;
prints a warning but returns correct result.
-Original Message-
From: tinycc-devel-bounces+eligis=wanadoo...@nongnu.org
[mailto:tinycc-devel-bounces+eligis=wanadoo...@nongnu.org] On Behal
Thanks for your advice, I checked with objdump:
#include
int
main(int argc, char *argv[])
{
char *p = (char *)0x12345678ABCD000F;
int res;
res = (p != (char *)0x12345678ABCD000F );
return res;
}
Compiles to:
foo.o: file format elf64-x86-64
Disassembly of
k1w1 wrote:
My question is about other platforms. I am trying to get TCC working
completely (including bounds checking) under cygwin. So I am trying to
understand how it works on other platforms so I can do it correctly. It
appeared to me that on any platform except Windows bcheck.o is compiled
Ah, I understand now why this makes it not a priority.
Of course I can probably get it working, but at what cost to the tiny
C codebase.
I'll have to think carefully before I dive in.
Bill.
2009/12/7 grischka :
> Bill Hart wrote:
>>
>> Yasm runs on linux and Windows and is becoming more popular
On Mon, Dec 7, 2009 at 2:13 PM, grischka wrote:
> k1w1 wrote:
>
>>On windows, all objects that tcc wants to use must be compiled
>>with tcc itself. In particular not with mingw-gcc.
>>
>> How about on other platforms. I was observing this behavior under Cygwin
>> which is more linux-like
Bill Hart wrote:
Yasm runs on linux and Windows and is becoming more popular. If tcc
also happens to assemble yasm code, then that is another way to
support both projects, no?
The main reason it would be useful to me is that the Windows 64
assembler code in MPIR is in yasm format.
Anyhow if it
k1w1 wrote:
On windows, all objects that tcc wants to use must be compiled
with tcc itself. In particular not with mingw-gcc.
How about on other platforms. I was observing this behavior under Cygwin
which is more linux-like than anything else.
Cygwin is not supported, neither by the
On Sun, Dec 6, 2009 at 11:02 AM, grischka wrote:
> k1w1 wrote:
>
>> Hi,
>>
>> I am trying to understand the Makefile. It seems to me that bcheck.o needs
>> to be built with tcc since it will be linked with the rest of the user code
>> built with tcc. However I can't see in the makefile how this h
Change
http://repo.or.cz/w/tinycc.git/commitdiff/dd70d19267ac343adae7bf15fe15c08fa6
04e5e1?hp=5dadff3de553b0dae46cca233c751ed8b6853da4
Is exactly what I proposed few months ago.
You probably may want to notify
mailto:predef-contrib...@lists.sourceforge.net
to update http://predef.sourceforge.net
Christian Jullien wrote:
Q. how can I see the .s output (as generally using -S on most compilers) ?
TCC outputs machine code, not assembler.
You can disassemble it though:
$ tcc -c x.c
$ objdump -D x.o
on win64:
$ x86_64-pc-mingw32-objdump -D x.o
--- grischka
___
10 matches
Mail list logo
