Re: [Tinycc-devel] Request push

2014-06-29 Thread Thomas Preud'homme
Le dimanche 29 juin 2014, 12:32:57 大熊猫 a écrit : Thank you Thomas, I hope you agree with my request. Sure, as I said, provided that a testcase is added I'd be happy for you to commit the patch. I'll change it a warning message, and then add some tests, along with a push up! Great. Not

Re: [Tinycc-devel] To document -l option clearer

2014-06-29 Thread Thomas Preud'homme
Le dimanche 29 juin 2014, 04:56:59 YX Hao a écrit : Hi, Usage: tcc [options...] [-o outfile] [-c] infile(s)... Is -l option must follow the infile(s)? Yes! I tried different positions. Before, undefined symbol error; behind, ok. Because of I had forgotten it. Usually, a library is

Re: [Tinycc-devel] State of the tcc project

2014-06-29 Thread Thomas Preud'homme
Le dimanche 01 juin 2014, 00:04:27 mobi phil a écrit : Why tinyCC didn't use a hierarchical code review, with people who follows the project and have a good overview (Thomas Preud'homme, grischka, Daniel Glöckner for ARM) ? Thanks, I also got dizzy by those useless patches.

Re: [Tinycc-devel] Why missing #includes don't cause warning/fail?

2014-06-29 Thread Thomas Preud'homme
Le samedi 31 mai 2014, 16:27:32 David Mertens a écrit : I have encountered this behavior before as well. I am pretty sure that the compiler is making a guess as to the form of the function based on how it's called. Then, it links to libc by default, so it is able to link against those

Re: [Tinycc-devel] incorrect/missing license files

2014-06-29 Thread Vincent Lefevre
On 2014-06-28 19:32:38 +0800, Thomas Preud'homme wrote: Le vendredi 27 juin 2014, 20:45:55 Vincent Lefevre a écrit : I'm not sure, due to the GPL system library exception. There is some disagreement over what that exception means. As far as I know, it only applies if the software is usually

Re: [Tinycc-devel] Request push

2014-06-29 Thread jiang
I have other patches, but their ideas are not very mature, and later pushed to give you. jiang 于 2014年06月29日 16:56, Thomas Preud'homme 写道: Le dimanche 29 juin 2014, 12:32:57 大熊猫 a écrit : Thank you Thomas, I hope you agree with my request. Sure, as I said, provided that a testcase is added

Re: [Tinycc-devel] incorrect/missing license files

2014-06-29 Thread Thomas Preud'homme
Le dimanche 29 juin 2014, 12:40:04 Vincent Lefevre a écrit : On 2014-06-28 19:32:38 +0800, Thomas Preud'homme wrote: Le vendredi 27 juin 2014, 20:45:55 Vincent Lefevre a écrit : I'm not sure, due to the GPL system library exception. There is some disagreement over what that exception

Re: [Tinycc-devel] Crosscompiling

2014-06-29 Thread Markus Bergholz
On Sat, Jun 28, 2014 at 6:44 PM, Michael Matz matz@frakked.de wrote: On Fri, 27 Jun 2014, Markus Bergholz wrote: Make it clear where “mexPrintf” is defined and why it is not effective. mexPrintf is defined in /usr/include/octave-3.8.1/octave/mexproto.h afaiu. That's

Re: [Tinycc-devel] Crosscompiling

2014-06-29 Thread grischka
Markus Bergholz wrote: However, both end up with Mex file entry point it missing. __declspec(dllexport) Mex file entry point -- gr Thanks in advanced, Markus ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org

Re: [Tinycc-devel] incorrect/missing license files

2014-06-29 Thread grischka
Thomas Preud'homme wrote: It should yes. Grischka, Shinichiro, James: do you agree to relicense your contributions to lib/libtcc1.c under the BSD variants in RELICENSING file? Is not that what people listed in RELICENSING already did agree to? If both of you answer yes, could you commit the

Re: [Tinycc-devel] incorrect/missing license files

2014-06-29 Thread Vincent Lefevre
On 2014-06-29 23:57:08 +0200, grischka wrote: Change the FSF header in lib/libtcc1.c? I'm not sure they would agree. However it allows being linked into any program anyway. How about *adding* the BSD copyright notice to this header? i.e. any future commit should be done under these two

[Tinycc-devel] Problem using alloca

2014-06-29 Thread Carlos Montiers
Hello. I requesting memory from the stack using the function alloca. I know that the use of it is discourage, but I want use it anyways. I write a code for windows that use it and I tested ok, but only when I compile with gcc. Compiling it with tiny c fails, the program crash. Maybe is a bug of

[Tinycc-devel] isxdigit conversion inconsistency with widechar

2014-06-29 Thread Carlos Montiers
Hello. Currently, in the last version (from git) of tiny c, when you use the function: isxdigit it produce this call: isxdigit but when you use the widechar version: iswxdigit : iswxdigit produce this call: iswctype(d, _HEX) Then, when you use isxdigit tiny c would be generate the call to: