[Top][All Lists]

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

Re: [Tinycc-devel] Feature request: Implementing asm directives .set and

From: Thomas Preud'homme
Subject: Re: [Tinycc-devel] Feature request: Implementing asm directives .set and .equ
Date: Mon, 26 Aug 2013 23:04:18 +0200
User-agent: KMail/4.10.5 (Linux/3.10-2-amd64; KDE/4.10.5; x86_64; ; )

Le lundi 26 août 2013 22:50:33 Jens Nyberg a écrit :
> 2013/8/26 Thomas Preud'homme <address@hidden>:
> > Le lundi 26 août 2013 13:07:37 Jens Nyberg a écrit :
> >> Hi!
> >> 
> >> I think implementing .set and .equ which are both functionally
> >> equivalent would be a easy task unless someone is already working on
> >> this?
> >> 
> >> If I implement it myself I assume what they do would be to define a
> >> symbol with a value and that's it. Or am I missing something?
> >> 
> >> And also, there is no reason for why these are not supported besides
> >> lack of time?
> > 
> > As most (all?) FLOSS project, there is difinitely a lack of time /
> > manpower to work on TinyCC. The number of feature request and bug report
> > is currently increasing and there seem to be no progress so far. There is
> > a few bugs and improvement I'd like to work on myself for a long time but
> > don't have time to work on for various reason.
> > 
> > If you feel you can do it then please go ahead and feel free to ask
> > questions. Help is more than welcome :)
> I'll see what I can do. =) I've actually spent a couple of weeks now
> almost every day just trying to straighten up the whole tcc codebase
> for a project of mine where I've removed all use of global variables
> (most of them ended up in the tcc_state struct which in turn is passed
> around).

That's great news. Would the result allow to compile several program in 
parallel? If yes, the contribution could be interesting.

> It was one hell of a job and I've now reached the point where
> I am actually trying to compile another project of mine using it and
> this is where I noticed these missing directives. The point of the
> whole project is to create a non-posix freestanding i386/x86 compiler
> so most changes I've done does not apply to tcc directly but the ones
> that do (like this one) will be shared back to the community after
> being ported back to tcc properly.

Great, thanks :)


Attachment: signature.asc
Description: This is a digitally signed message part.

reply via email to

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