On 11/26/07, KHMan <[EMAIL PROTECTED]> wrote:
> Joshua Phillips wrote:
> > Oughtn't tcc be broken into multiple source files?
>
> I tried studying the sources over the weekend, and it looks like a
While you're at it, feel free to dump notes to http://tcc.wikidot.com/
-gregg
On 11/2/07, KHMan <[EMAIL PROTECTED]> wrote:
> grischka wrote:
> > Do you think it is possible and/or makes sense to extract all
> > changesets from Rob's repo into single patches first, with an
> > automatic script or something?
In case you're not aware of it, check out Mercurial Queues
(http://h
On 10/31/07, Joshua Phillips <[EMAIL PROTECTED]> wrote:
> SourceForge supports Mercurial
>
Not according to their documentation. Do you have a link?
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-d
On 9/21/07, Peter Lund <[EMAIL PROTECTED]> wrote:
> On Thu, 2007-09-20 at 23:38 -0500, Rob Landley wrote:
>
> > You've mentioned Harbison and Steele more than once, but otherwise I've
> > never
> > heard of them.
>
> It's the standard work that everybody uses instead of reading the
> standard ;)
>
On 9/20/07, Rob Landley <[EMAIL PROTECTED]> wrote:
> > "static" => eternal life + local scope (block, file, etc.)
> > "extern" => eternal life + proselytizing (projection to containing
> > scope, either file/TU or global)
>
> The local scope is inherent in the {}, static overrides the lifespan of
On 9/20/07, Rob Landley <[EMAIL PROTECTED]> wrote:
> > Vars with no explicit storage
> > class default to extern, which implies static. (5th ed., 4.6.1)
>
> extern implies static?
>
> Hang on, so if I say "extern int thingy;" in a header, and declare a
> global "int thingy;" in a .c file, I can't
On 9/20/07, Rob Landley <[EMAIL PROTECTED]> wrote:
>
> I'm wondering if there's some circumstance under which it _should_ generate
> code that runs before "main", and if so how I'd go about it. (The "no, it
> should enver do this" is the easy case to fix, but I'm unsure whether or not
> that's the
On 9/20/07, Rob Landley <[EMAIL PROTECTED]> wrote:
>
> The constant propagation thing is relatively straightforward, the "int
> thingy=printf();" thing I'm not 100% sure about, is that allowed in c99? I
> know c++ has constructors that run before main() does, can you do something
> equivalent in C
On 13 Sep 2007 11:48:31 +0300, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> However, would it not be good if someone tried to make a simple set of
> standard extensions?
Got D? http://www.digitalmars.com/d/
___
Tinycc-devel mailing list
Tinycc-dev
On 9/10/07, David A. Wheeler <[EMAIL PROTECTED]> wrote:
>
> I'm trying to figure out what problem is being solved.
>
> If the problem is that "the names are hideously unclear and thus making
> maintenance difficult", then trading one mysterious abbreviation for another
> mysterious abbreviation
On 9/8/07, Rob Landley <[EMAIL PROTECTED]> wrote:
>
> > In fact, it's pretty much guaranteed to
> > confuse, since the notion of a lookahead ("following char = fch?") is
> > part of the domain knowledge. I'm afraid I don't like fch much at
> > all. Sorry.
>
> Would you like me to revert the commi
I submitted some documentation to Rob offlist, which lead to a
discussion that really should be onlist, so here goes:
The topic is naming conventions. There are two specific issues:
tcc uses global vars with names like ch, file, tok for the most
recently handled thingee. This is not so good, si
Howdy folks,
I started writing a HACKING file and then realized it was looking like
a brutal hack, so I created a wiki to use as a workspace/scratchpad
for creating documentation on tcc. It's at http://tcc.wikidot.com/.
Feel free to contribute. Scratch that; /please/ add/correct
information on t
On 9/6/07, Basile STARYNKEVITCH <[EMAIL PROTECTED]> wrote:
>
> If you consider starting TCC from scratch you might look into other
> small open source compilers like http://sourceforge.net/projects/nwcc/
>
Good Lord, it never ends. Just what I need, another interesting
little project to lead me do
On 9/5/07, Simon 'corecode' Schubert <[EMAIL PROTECTED]> wrote:
>
> Nevertheless I wonder if it might be a nice educational experience to
> write a new tcc (or however it would be called) from scratch, using nice
> function and variable names, a sane scoping (not everything as globals)
> and broken
On 9/5/07, Rob Landley <[EMAIL PROTECTED]> wrote:
> On Wednesday 05 September 2007 1:02:03 am Dave Dodge wrote:
> > > I fixed the "ptr || ptr" bit not working (check hg), and I just made it
> > > stop warning me about "comparison between pointer and int" for && and ||,
> > > but now it's saying "in
On 8/29/07, Rob Landley <[EMAIL PROTECTED]> wrote:
> > Ok, I have a patch, but it's a bit more ambitious. I have:
> >
> > * stripped Makefile and configure to the bare minimum necessary to
> > make it go on cygwin
>
> Does this impact any other platforms?
At the moment, yes. I'm tossing the c
On 8/28/07, Rob Landley <[EMAIL PROTECTED]> wrote:
> I just yanked the ucontext.h include. Let me know when you've got a patch for
> the other two...
Ok, I have a patch, but it's a bit more ambitious. I have:
* stripped Makefile and configure to the bare minimum necessary to
make it go on cyg
On 8/28/07, Rob Landley <[EMAIL PROTECTED]> wrote:
...
> Building the entire project, including all cross compiler targets, the build
> currently does this:
>
> cc -O2 -g -Wall -fsigned-char -Os -mpreferred-stack-boundary=2 -m386 \
> -malign-functions=0 -o tcc tcc.c -lm -ldl
> cc -O2 -g -Wa
On 8/28/07, Jakob Eriksson <[EMAIL PROTECTED]> wrote:
> Shawn Rutledge wrote:
> > I'd suggest having a look at cmake. It seems to have worked well for
> > Chicken Scheme. The configuration is user-friendly (ncurses menus
> > rather than having to pass in a lot of --options to ./configure),
> >
>
Well, that was a lot easier than I expected. It'll be a while before
I get a decent Makefile built, but it took about 20 minutes to get it
to build on cygwin. Three problems:
* __malloc_hooks isn't supported by cygwin, which uses the redhat
newlib (http://sourceware.org/newlib/) instead of gl
I just noticed a license conflict. The COPYING file says LGPL, but
bcheck.c says GPL. Presumably this is an oversight, but it would
probably be good to replace the licensing language in the individual
files with references to COPYING.
-gregg
___
Tiny
On 8/26/07, Ivo <[EMAIL PROTECTED]> wrote:
> > > I forsee Checking for Fortran compiler... etc..
> >
> > I don't know what kind of traumas you suffered in your early
> > development, but I had nothing to do with them.
>
> Insulting people doesn't make you look smarter.
Lighten up, Ivo. It was a
On 8/26/07, Ivo <[EMAIL PROTECTED]> wrote:
> On Sunday 26 August 2007 12:56, Gregg Reynolds wrote:
> > Anybody out there willing to help test an autotoolized version? I've
> > been doing a lot of work with autoconf and friends lately, so I'm
> > thinking abo
Hi,
Just found tcc/tinycc recently. I'd like to use it under cygwin, osx,
and opendbsd. However, its config/make system is a little weak. I
had to hack it up just to get it to compile on mingw, and there are
still problems.
Anybody out there willing to help test an autotoolized version? I've
25 matches
Mail list logo
