From: | arnold@skeeve.com (Aharon Robbins) |
Newsgroups: | comp.compilers |
Date: | Thu, 29 Sep 2016 02:55:20 -0000 (UTC) |
Organization: | A noiseless patient Spider |
References: | 16-09-001 16-09-033 16-09-034 16-09-036 |
Injection-Info: | miucha.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="94886"; mail-complaints-to="abuse@iecc.com" |
Keywords: | C, practice |
Posted-Date: | 29 Sep 2016 21:33:51 EDT |
In article 16-09-036,
George Neuner <gneuner2@comcast.net> wrote:
>The i5 has 4 non-HT cores.
Works for me. :-)
>If you really have plenty of RAM, why not create a ramdisk? Or put
>in an SSD for the tmp filesystem?
I spent enough $$ for the laptop and it's fast enough in general. I
don't want to buy an SSD or move my work directory off the hard disk
in case of power failures or whatever.
>>Since I originally posted, someone suggested that I just fix tcc on
>>my own. I was able to do this with less than 2 hours work so now
>>I'm back to being fat, dumb and happy. :-)
>
>As long as you don't expect the same level of optimization. TCC is
>nice for quick development turn-around, but it doesn't produce the
>fastest code.
I am exactly interestsed in "quick development turn-around". :-)
Thanks,
Arnold
--
Aharon (Arnold) Robbins arnold AT skeeve DOT com
Return to the
comp.compilers page.
Search the
comp.compilers archives again.