It's another long and obscure patch with zero discussions about the
approach upfront and no explanation whatsoever what the patch does and how
it solves the problem.
I really really dislike where tcc is going and I no longer trust it as our
C compiler backend.
On Fri, Aug 1, 2014 at 10:37 AM,
, and helping jiang produce a patch
that includes a discussion, meaningful comments, and many small commits.
I fail to see how this direction for tcc is a bad one. :-)
David
On Fri, Aug 1, 2014 at 5:28 AM, Sia Lang silverlangu...@gmail.com wrote:
It's another long and obscure patch with zero
On Fri, Aug 1, 2014 at 5:10 PM, jiang 30155...@qq.com wrote:
I would like you to explain my patch.
I vstore () in bitfield values on the right match, with gen_cast (dt) to
achieve.
[...]
Could you please repost your explanation in english?
Thanks,
Sia
I just wanted to add that I agree with everything Thomas said. I use tcc as
an embedded compiler, and it's already the case that it's *just* fast
enough. So I'd like to see patches making tcc even faster :) Correctness
first, of course, but I don't need tcc holding my hand.
- Sia
On Sat, Jun 7,
jiang,
My suggestion:
1. Learn english properly, it's very hard to understand your comments
2. Learn the tcc code base properly, then ask for small patch reviews to
get things started
- Sia
On Wed, Jun 4, 2014 at 4:09 PM, jiang 30155...@qq.com wrote:
Hey Thomas Preud'homme
Thank you.
The troll alarm went off really hard. I would never trust this guys
patches, but, hey, that's just me... hopefully the breaking patches are
moved to another repo so that I can more easily ignore any pull requests :)
Anyone else working on TCC right now?
-Sia
On Thu, May 29, 2014 at 3:14 PM,
We've come to depend on TCC as an embedded C compiler and are quite frankly
a bit discouraged by the latest developments.
The home page says bellard is no longer working on tcc, but there is
fortunately some traffic in the git repo
However, I have a couple of concerns:
1. Lately, a large amount
