tinycc-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Tinycc-devel] Re: TinyCC CVS, Rob's fork, the future (was: [PATCH 5/5]


From: Daniel Glöckner
Subject: [Tinycc-devel] Re: TinyCC CVS, Rob's fork, the future (was: [PATCH 5/5] Fix gv for long longs)
Date: Sun, 7 Sep 2008 19:50:58 +0200
User-agent: Mutt/1.4.2.1i

Hi Rob,
not trying to defend CVS, but somewhere in the tinycc CVS void between
October 2006 and October 2007 Savannah switched to a version that logs
commit IDs with each change. This allows to regroup changes in several
files to changesets.

Today I wrote a shell script that parses the output of "cvs log" and
generates a diff for every commit. It prepends the log message and a
list of affected files. There were 47 commits after your automated
import to Mercurial. If one day you feel like syncing your fork, you
can use the attached script or just use the tar ball of the diffs at
http://www.stud.uni-hannover.de/~daniel/tcc/tcccvs-20060220-20080907.tar.bz2
(I can only guarantee for this homepage to exist for the next two months.)


> It's a question of KILLING OFF THE CVS ARCHIVE, which will never happen.

Well, Savannah does have Subversion, Git, and Mercurial.
If we bug the right people, the repository might get converted.

> Nobody but me seems to be working on an x86-64 target, or even an x86-64 
> _host_.

x86-64 as a target might be problematic because tinycc expects long
longs to be distributed over two registers. It's similar to the issue
I have with supporting soft float on ARM. I need doubles to be kept
in two integer registers.

> (Tried building running the x86 code generator on arm? 
> Segfault, unaligned access...)

We could add a function/macro that reads unaligned ints.
grep "(.*\* *)" *c should list all relevant (and some irrelevant) lines.

> Your version is still missing rather a lot of work I've done.  But I 
> can't change it, and nobody here wants to, so I'll stop bothering you now.

Even if there was someone who wants to change it, we can't because of
the license. Can you change the license back to LGPL after having accepted
patches from other people?

> Daniel's work isn't based on my fork.  Nobody else's is.  Instead, what work 
> they do is based on the CVS version.

I started working on tinycc before there was a fork and since patches
for your version can not be used by Fabrice's version (because of the
license, renaming, and a new directory structure), I'll stay here.
If this project switches away from CVS, I will as well, as will everyone
else.

Btw., my last patches were based on 0.9.24, not on CVS.

  Daniel

Attachment: parselog
Description: Text document


reply via email to

[Prev in Thread] Current Thread [Next in Thread]