Le lundi 28 mai 2012 07:19:34, Pedro A ARANDA a écrit :
> > Subject: Re: [Tinycc-devel] include more options in configure to be
> >
> > able to build tinycc with debian
> >
> > Message-ID: <201205252045.44099.robo...@celest.fr>
> > Content-Type: text/plain; charset="utf-8"
> >
> > Le vendred
Thomas Preud'homme wrote:
Grishka, would the following patch be fine with you? I saw you add the
change to error out on unknown option.
Sure. I've added that because I want some feedback when I mistype stuff.
Maybe just to be similar to other formats it should be
configure: WARNING: unr
Le lundi 28 mai 2012 20:50:27, grischka a écrit :
> Thomas Preud'homme wrote:
> > Grishka, would the following patch be fine with you? I saw you add the
> > change to error out on unknown option.
>
> Sure. I've added that because I want some feedback when I mistype stuff.
>
> Maybe just to be si
Hi,
> > If one changes anything at all then it only makes sense to change
> > it so as to be layout compatible with GCC. A third layout (GCC,
> > TCC-old, TCC-new) wouldn't help. Although the rules of GCC are
> > relatively obscure and complex in corner cases.
>
> Actually I have to correct mys
Hi Paulo,
FYI, I am not one of the main contributors, but you raised my interest when
you mentioned Mac. In short I would like to know more about what you are
doing, as your changes seem extensive.
tcc already works on Mac, but only to interactively run apps. Did you make
any progress for tcc to
Yes, I made some changes for it to produce native binary files on Mac. And the
C11 updates are pretty much to be approved and used.I made this changes because
I don't want my compiler project to have any dependencies, so I want to
encourage the use of TCC as bootstrapper compiler when needed. G
Hello,
I really enjoy your efforts to implement C11 features in tcc which is of
course a good decision.
IMHO, C11 additions should be only available using a compiler flag. Gcc uses
for example -std=xxx to specify the C level you want to support.
For C11, gcc uses -std=c11 and -std=iso9899:201
This reminds me of something... I've added reference variables too (like in
C++), should I post here a patch for that too, or should I remove it too before
posting any patches?
From: eli...@orange.fr
To: tinycc-devel@nongnu.org
Date: Tue, 29 May 2012 06:00:07 +0200
Subject: Re: [Tinycc-deve
Paulo,
I'm not tcc maintainer and I only speak for myself, reference falls in the
same category: incompatible C extensions.
This a debate that sooner than later comes for C implementations: should we
extend the language to make a better C?
There is already a better C which is called C++, i
You know guys, you can remove the irrelevant parts of what you're replying to...
> Date: Tue, 29 May 2012 02:52:13 +
> From: Paulo Henrique Torrens
> To:
> Subject: [Tinycc-devel] Extension to C language
> Message-ID:
> Content-Type: text/plain; charset="iso-8859-1"
>
>
> Hi,
> I'm working
Hi,
I'm working on a compiler suite project (black.nongnu.org), and made several
updates to TCC in order to incentive it's use as bootstrapper compiler and for
"publicity", including port to Mac OS X and the Open/Free/Net BSDs (and
planning on fixing for Android), the C11 _Atomic, _Alignas and
11 matches
Mail list logo
