Re: [Tinycc-devel] Trouble on x86-64, not windows, not gcc

Alright, it's been pushed to mob: http://repo.or.cz/tinycc.git/commit/0a402f6e91c284dd37cb61e726cc95de20fe895e On Wed, Aug 3, 2016 at 6:11 PM, Michael Matz wrote: > Hi, > > On Tue, 2 Aug 2016, David Mertens wrote: > > Unless I hear opposition, I'll push a fix to mob some

Re: [Tinycc-devel] Trouble on x86-64, not windows, not gcc

Hi, On Tue, 2 Aug 2016, David Mertens wrote: Unless I hear opposition, I'll push a fix to mob some time tomorrow. Also, for similar reasons, it appears that including "#define _VA_LIST_DECLARED" might help make BSD (or at least FreeBSD) happy. I am currently testing this. Does anybody have

Re: [Tinycc-devel] Trouble on x86-64, not windows, not gcc

Unless I hear opposition, I'll push a fix to mob some time tomorrow. Also, for similar reasons, it appears that including "#define _VA_LIST_DECLARED" might help make BSD (or at least FreeBSD) happy. I am currently testing this. Does anybody have experience with this, or any commentary on whether

Re: [Tinycc-devel] Trouble on x86-64, not windows, not gcc

FWIW, when I patch our copy of stdarg.h to #define _VA_LIST_T on Macs, the tests pass: http://www.cpantesters.org/cpan/report/a5fc4ca8-5788-11e6-bb69-be43cba39ea2 Amusingly, those are reported as test failures, but that's because I'm doing a straight text comparison of the output. The header

Re: [Tinycc-devel] Trouble on x86-64, not windows, not gcc

I found a copy of Apple's _va_list.h header file: http://opensource.apple.com/source/xnu/xnu-3248.20.55/bsd/sys/_types/_va_list.h The offending lines are: #ifndef _VA_LIST_T #define _VA_LIST_Ttypedef __darwin_va_list va_list; #endif /* _VA_LIST_T */ Perhaps our stdarg.h should #define

Re: [Tinycc-devel] Trouble on x86-64, not windows, not gcc

Well bother, the cpantesters site appears to be experiencing intermittent trouble at the moment. If you try to read the full report on cpantesters, you may need to hit "refresh" a few times. On Sun, Jul 10, 2016 at 3:06 PM, David Mertens wrote: > Hello Michael, > >

Re: [Tinycc-devel] Trouble on x86-64, not windows, not gcc

Hello Michael, Thanks for your reply, and for explaining things. A few points of clarification are in order. On Sun, Jul 10, 2016 at 1:21 PM, Michael Matz wrote: > On Sat, 9 Jul 2016, David Mertens wrote: > > When run on Mac systems, I get errors about "incompatible

Re: [Tinycc-devel] Trouble on x86-64, not windows, not gcc

Michael Matz wrote: (Ultimately the layout of va_list has to be compatible between compilers on the same system anyway; it's dictated by the psABI.) Which reminds me of a fix for exactly such problem on win64 (which strangely enough exists since 04/2013)

Re: [Tinycc-devel] Trouble on x86-64, not windows, not gcc

Hi, On Sun, 10 Jul 2016, Michael Matz wrote: TCC's handling of variable argument lists are spelled out in stdarg.h, with implementation in libtcc1.c. I think that for 64-bit machines, we should also check for clang, and then use clang-compatible definitions. Oh, I forgot to expand here: the

Re: [Tinycc-devel] Trouble on x86-64, not windows, not gcc

On Sat, Jul 9, 2016 at 3:10 PM, David Mertens wrote: > Hello everyone, > > When run on Mac systems, I get errors about "incompatible redefinition of > 'va_list'". Looking at the source files involved, I'm pretty sure this > occurs on x86-64 systems that are neither

[Tinycc-devel] Trouble on x86-64, not windows, not gcc

Hello everyone, When run on Mac systems, I get errors about "incompatible redefinition of 'va_list'". Looking at the source files involved, I'm pretty sure this occurs on x86-64 systems that are neither Windows nor built with gcc. Such systems include 64-bit Macs and BSDs using clang. It might