Hello On Sat, Jul 15, 2017 at 9:53 AM, grischka <[email protected]> wrote: > uso ewin wrote: >> >> >> Hello, >> >> Sorry if I take time to answer, >> So actually it's not a test issue, because gcc can do difference >> between a 'char *' a 'signed char *', and a 'unsigned char *', >> gcc doesn't consider int and a typedef of an int as the same type, >> and most important it will find the good match to a long. >> >> grischka seems to have fix char * problem, >> I've just push a fix for the long on my github, >> but it does refactor how VT_LONG is handle so I’m not very confident >> on pushing it now on mob without a review >> (this is why it take me time to answer). >> >> I've also fix all type. I mean fix all typo
>> >> for the typedef, I guess it might work, but I didn't check further yet. > > > Does it work with "_Generic(i + 1L, ...)" ? > I didn't test it yet sorry, Apparently patches on my github have break some tests, which I try to fix at first, then I'll try to fix "_Generic(i + 1L, ...)" (I guess it doesn't work as untested) I'll notify again here once everything are fix. Should I push typo fix on mob now ? _______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
