About commit TILE-Gx backend to community repository and default disabled

Jiong Wang jiwang at tilera.com
Fri Mar 15 00:15:15 PDT 2013

Hi All,

As you have seen, I had sent all tilegx patches to get code review, and
thanks for all the feedbacks on coding style and simplifing the code.

So, is it OK to commit TILE-Gx backend to community master and let it
default disabled?

Tilera's recent plan about TILE-Gx backend is:

1. merge the current tilegx support to community master, so that we
could go on the next stage development with more community interaction,
including AsmParser for VLIW bundle, hardware float optimization, SIMD
support etc.
2. we will contribute a tilegx buildbot once the code merged, so that
it's good for both the community and company to monitor tilegx status.
Actually, I have verified the buildbot environment on tilegx server, all
OK, just wait for the merge, then it could svn co code from community
and build :)

if there is any important step I have missed or am wrong that block
tilegx backend committed, please feel free to point out so that I could
correct it.

thank you, looking forward to your reply.

Tilera Corporation.

More information about the cfe-commits mailing list