Re: [Tinycc-devel] Annoying new warning

Hi, On Sat, 6 May 2017, Christian Jullien wrote: Using your advice, I added #if !defined(TCC_TARGET_ARM) around all code directly or indirectly using ldouble_long which solved warning. But you now also ifdefed out __fixunsdfdi and __fixdfdi. That can't work, they are called from the

Re: [Tinycc-devel] Annoying new warning

Hi Grischka, Using your advice, I added #if !defined(TCC_TARGET_ARM) around all code directly or indirectly using ldouble_long which solved warning. If you agree, I'll push this change on mod but IMHO it should be done the other way, #if defined() jullien@sims3:~/tinycc $ git diff diff --git

Re: [Tinycc-devel] Possible release schedule?

I have found 9.26 (current stable) to be riddled with bugs, and the latest git to be much more stable. I would like to see a new release just because of that. When I tried TCC 9.26 a couple of months back I was stuck in a hole of misleading compiler messages, strange crashes and executables

Re: [Tinycc-devel] This (incorrect) code crashes the compiler

Hi, On Thu, 4 May 2017, Tony Papadimitriou wrote: char xxx()[] {}   Specifically, it’s the (wrong) use of [] that causes the crash. Fixed in mob (the crash, not implementing full support for this extension of returning arrays from functions; it's regarded as returning a pointer to char).

[Tinycc-devel] Possible release schedule?

I've been lurking here and there, but haven't seen any rabbling about a new release? It's been several years and I really like the current mainline for my projects. I'm hoping to use TCC in a rash of upcoming projects. Any word if I might be able to direct people to 0.9.27? The latest I can see

Re: [Tinycc-devel] Annoying new warning

Christian JULLIEN wrote: Grischka, it was my first attempt with fprintf+exit(0) but I found that none was available in libtcc. I vote for _xxx_abort(const char* msg); Christian Nope. Just #ifdef out the entire function. --- grischka ___

Re: [Tinycc-devel] [Tinycc-dev] Some question about tinycc in macOS

Ok, i go get some informations about the Mach-O file format, and see whether i can make it. -- Haoran Wang On Fri, May 05, 2017 at 02:17:00PM +0300, Andrei Warkentin wrote: > I don't think anyone is actively adding Mach-O support. You're welcome to > work on it. It's hard to qualify and quantify

Re: [Tinycc-devel] [Tinycc-dev] Some question about tinycc in macOS

I don't think anyone is actively adding Mach-O support. You're welcome to work on it. It's hard to qualify and quantify the work since I don't know much beyond the very basics of the Mach-O and fat binary format. I'd start with a fixed address statically linked binary if that's possible in OSX

Re: [Tinycc-devel] Annoying new warning

On 2017-05-05 13:02:05 +0200, grischka wrote: > Vincent Lefevre wrote: > > But this can hide bugs, e.g. if in the future this function is called > > by the ARM backend. It would be better either not to define this > > function at all (best solution at it doesn't make sense on the ARM, > > and

Re: [Tinycc-devel] Annoying new warning

Grischka, it was my first attempt with fprintf+exit(0) but I found that none was available in libtcc. I vote for _xxx_abort(const char* msg); Christian Le :05 mai 2017 à 12:02 (GMT +02:00) De :"grischka" gris...@gmx.de À :"tinycc-devel@nongnu.org" tinycc-devel@nongnu.org Objet :Re:

Re: [Tinycc-devel] Annoying new warning

On 2017-05-05 17:29:22 +1000, William Hales wrote: > This is his message, copied and pasted: > > > Hi Vincent, > > > > return 666; works equally well as it should not be called by ARM backend. > > > > This is a workaround to remove warning. But this can hide bugs, e.g. if in the future this

Re: [Tinycc-devel] [Tinycc-dev] Some question about tinycc in macOS

Thanks a lot, i was wondering whether some one is doing such staff to add Mach-O supoort, or this function is not needed in tinycc project? And i am not sure how hard this work would be, if i want do it as my hobby project? -- haoran wang On Fri, May 05, 2017 at 10:29:54AM +0300, Andrei Warkentin

Re: [Tinycc-devel] Annoying new warning

___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Re: [Tinycc-devel] Annoying new warning

I can see his message on my (HTML) client A little investigation: it seems that Christian's email came in two forms (HTML and plaintext), but only one of them contains his message: --=_Part_3272_615315037.1493968868262 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding:

Re: [Tinycc-devel] [Tinycc-dev] Some question about tinycc in macOS

Hi Haoran, A native tinycc compiler can only be used in script mode today (i.e. with -run). There is no Mach-O generation at the moment. I imagine that when Mach-O is added it would be done similar to the PE-COFF support, where the intermediate (object) format is still ELF. A > 5 мая 2017 г.,

Re: [Tinycc-devel] Annoying new warning

On 2017-05-05 09:21:08 +0200, Christian JULLIEN wrote: > ___ > Tinycc-devel mailing list > Tinycc-devel@nongnu.org > https://lists.nongnu.org/mailman/listinfo/tinycc-devel Your message is empty. -- Vincent Lefèvre - Web:

Re: [Tinycc-devel] Annoying new warning

___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Re: [Tinycc-devel] Annoying new warning

On 2017-05-05 06:46:27 +0200, Christian Jullien wrote: > Ok, I tried this patch which allowed me to run my complete non-regression > test suite without problem on ARM. > > Do you agree I push this patch in mob? > > diff --git a/lib/libtcc1.c b/lib/libtcc1.c > index 9195489..bcdfb0b 100644 > ---