search for: gettileregisternumb

...of what is required). > > thanks for pointting this out, I will add regression tests, then > re-send the patch. > before this, please feel free to give comments and suggestions on the > existed patches. You also need tests for Clang bits, too. Mechanical issues: +/// getTileRegisterNumbering - Given the enum value for some register, +/// return the number that it corresponds to. Please don't duplicate function and class name in comments. Existing code does this, but current style guidelines advise not to. http://llvm.org/docs/CodingStandards.html#doxygen-use-in-documentatio...

On 03/02/2013 04:50 AM, Dmitri Gribenko wrote: > You also need tests for Clang bits, too. > > Mechanical issues: > > +/// getTileRegisterNumbering - Given the enum value for some register, > +/// return the number that it corresponds to. > > Please don't duplicate function and class name in comments. Existing > code does this, but current style guidelines advise not to. > > http://llvm.org/docs/CodingStandards.html...

On 03/01/2013 10:42 PM, Hal Finkel wrote: > > As some of the llvm modules are in active development, for example MC > Layer, we want to return code to community repository first, so that > it will be easy to keep pace with llvm main tree. > I think this makes sense; but my impression is that the community will want a clear idea that this will be maintained and improved for the

...ut as tilegx gcc, most of them are about float precision issue) --- Regards, Jiong Tilera Corporation 于 2013/3/2 9:19, Jiong Wang 写道: > On 03/02/2013 04:50 AM, Dmitri Gribenko wrote: >> You also need tests for Clang bits, too. >> >> Mechanical issues: >> >> +/// getTileRegisterNumbering - Given the enum value for some register, >> +/// return the number that it corresponds to. >> >> Please don't duplicate function and class name in comments. Existing >> code does this, but current style guidelines advise not to. >> >> http://llvm.org/do...