[RFC] (Better) Tagging of Fortran PRs in Bugzilla

[Tobias Burnus]

Hi Thomas, hi Harald,

On 12/10/19 10:41 PM, Thomas Koenig wrote:
>> Maybe others feel the same way.  Couldn't we do more towards 
>> appropriate tagging
>> of PR's for features like the following:
>>
>> - [OpenMP]
>> - [OpenACC]
>> - [OOP]
>> - [Coarray]/[CAF]
>> - [F0x]/[F18]
>> - [...]
> I think this is a good suggestion.

I think that's already mostly the case today.

For OpenMP and OpenACC, please also use the same-named keywords (in the 
key-world field), not only the the bug title. — Also other key words 
like wrong-code, ice-on-(in)valid, diagnostic, rejects-valid can help.

> When looking at bug lists, a subject like ICE in gfc_some_function
> does not tell a lot about what area of the compiler this is

Actually, such titles usually tell a lot – as the function name tells 
where it fails. (The bug may be way earlier.) I think in many cases, 
that's the best one has, unless one studies the bug more closely. Having 
additionally a hint in the bug title still helps (like: it has to do 
with common blocks) but I still regard the function name as valuable.

Recently, many issues were about C binding (which used the C array 
descriptor); I am not sure how to put this into brackets.

Cheers,

Tobias