[Consult] tile: How to construct testsuite for tile architecture without hardware.

Mike Stump mikestump@comcast.net
Wed Oct 21 16:40:00 GMT 2015


On Oct 19, 2015, at 3:45 PM, Chen Gang <xili_gchen_5257@hotmail.com> wrote:
> 
> On 10/20/15 02:26, Mike Stump wrote:
>> On Oct 17, 2015, at 10:23 PM, Chen Gang <xili_gchen_5257@hotmail.com> wrote:
>>> After fix one qemu issue about floating point insns, correct the related
>>> environments (make some symbol links), and reconfig building options (so
>>> support g++), the current gcc testsuite result are:
>>> 
>>>                === gcc Summary ===
>>> 
>>> # of expected passes            78156
>>  
>> Nice.
>>  
> 
> Thanks. :-)
> 
>>> # of unexpected failures        98
>>  
>>> Welcome any ideas, suggestions, and completions.
>>  
>> So, if you would like to do more work, and don’t have any other plans, you could investigate the unexpected failures in the above, if you want.  I hesitate to say this, as the funnest work, is work that you want to do.  I would ask, what would you like to do next?  Other work, if you wanted to try your hand at something, would be to read through the PRs on the gcc web site, and find one that you’d like to fix and fix it.
>>  
> 
> At present, for me, I should continue analyzing the unexpected failures,

Sounds good.

> And excuse me, could your provide more details about "PRs", I don't know
> anythings about it.

These are the official bugs reported  against gcc by users of gcc.  They all go into the Problem Report database (PR for short).  The main page it at:

  https://gcc.gnu.org/bugzilla/

and that is a front end for the database.  The database is composed of entries that are numbered, and to get at an entry, in case you want to see one:

  https://gcc.gnu.org/PR17234

will show you entry 17234, which we refer to as PR17234.  This one details a bug with if conversion.  One can search the database for what ever one would like.

> Welcome any ideas, suggestions, and completions.

Your plans sound wonderful, thanks for all the work.  As you find patches to fix things, be sure to send them in.


More information about the Gcc-help mailing list