Re: [www/bugzilla] PR 36739 Proposal for clarifications in GCC Bugzilla

[Richard Guenther <richard dot guenther at gmail dot com>]

On Sun, Aug 9, 2009 at 1:14 PM, Manuel
López-Ibáñez<lopezibanez@gmail.com> wrote:
> 2009/8/9 Richard Guenther <richard.guenther@gmail.com>:
>>
>> Well. ?I think the reporting form should have all fields that we require
>> to be given. ?Which IMHO includes the target-triple. ?The triples are
>
> This is news for me. The word "triplet" is never mentioned in
> bugs.html, so it is strange that it is a requirement.
>
>> only meaningless to users because there is not even description available
>
> Where is the description available? How am I to found the target/host triplet?

I said it is not available ;)  It is semi-available by bugs.html talking about
gcc -v output which includes:

$ gcc -v
Using built-in specs.
Target: i486-linux-gnu
...

I suggested to add a description for the *-tripled fields and link to it like
it is done for severity and keywords.  In fact, all fields on the bugreporting
page should have a description linked to.

>> what it is! ?Likewise the known-to-work field is something we require if
>> people report a regression.
>
> I am not going to discuss what could be added. That is orthogonal to
> my patch. Anyone is free to submit patches for adding things.

Heh, but you are touching the page! ;)

>> Most of the time it is guesswork to find out the target and known-to-work
>> fields from the initial description and just thinking people would fill
>> out more required details from the generated bug page is moot - the
>> information there doesn't become more meaningful to them.
>
> No, it doesn't. Most users won't fill that info anyway. But in the
> reporting page it becomes a waste of time and probably a stopping
> energy.

But we need this information.  A way to access it would be to tell them
on the reporting page (yeah ...) to paste the output of running 'gcc -v'
into the description field.

Richard.

> Cheers,
>
> Manuel.
>