[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Tinycc-devel] Could -v be more verbose?
From: |
Christian Jullien |
Subject: |
RE: [Tinycc-devel] Could -v be more verbose? |
Date: |
Sun, 20 Dec 2009 14:19:52 +0100 |
You can achieve this in tcc.c with:
if (0 == s->verbose++) {
printf("tcc version %s\n", TCC_VERSION);
#if defined(TCC_TARGET_I386)
printf("Target: i386\n");
#elif defined(TCC_TARGET_X86_64)
printf("Target: x86_64\n");
#elif defined(TCC_TARGET_ARM)
printf("Target: arm\n");
#elif defined(TCC_TARGET_C67)
printf("Target: C67\n");
#else
printf("Target: Unknown\n");
#endif
}
You may also want to add more valuable details like constants from config.h
(PE, COFF, ...)
Christian
-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf Of
Christian Jullien
Sent: dimanche 20 décembre 2009 12:55
To: address@hidden
Subject: [Tinycc-devel] Could -v be more verbose?
On my system, I have two tcc, one for i386 and one x64_86 but
tcc -v only reports
tcc version 0.9.25
I think it should at least report the backend processor it generates code
for.
tcc version 0.9.25 for i386
tcc version 0.9.25 for x86_64
Or, as gcc if you like
tcc version 0.9.25
Target: i386
tcc version 0.9.25
Target: x86_64
_______________________________________________
Tinycc-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
----------------------------------------------------------------------------
-----------
Orange vous informe que cet e-mail a ete controle par l'anti-virus mail.
Aucun virus connu a ce jour par nos services n'a ete detecte.