This is the mail archive of the
mailing list for the GCC project.
Re: Wrong GCC PR2020 annotated for "[committed, libgomp,amdgcn] Fix plugin-gcn.c bug"
- From: "Richard Earnshaw (lists)" <Richard dot Earnshaw at arm dot com>
- To: Jakub Jelinek <jakub at redhat dot com>, Thomas Schwinge <thomas at codesourcery dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: gcc at gcc dot gnu dot org, Andrew Stubbs <ams at codesourcery dot com>
- Date: Thu, 23 Jan 2020 15:33:32 +0000
- Subject: Re: Wrong GCC PR2020 annotated for "[committed, libgomp,amdgcn] Fix plugin-gcn.c bug"
- References: <firstname.lastname@example.org> <email@example.com> <20200123152843.GA10088@tucnak>
On 23/01/2020 15:28, Jakub Jelinek wrote:
On Thu, Jan 23, 2020 at 04:23:01PM +0100, Thomas Schwinge wrote:
On 2020-01-23T12:46:24+0000, Andrew Stubbs <firstname.lastname@example.org> wrote:
I've committed this patch to fix a bug in the OpenMP argument parsing.
Why did "the system" decided to annotate <https://gcc.gnu.org/PR2020>?
For obvious reasons, there are "2020" references in this commit, but
nothing with a "PR" or "PR [...]/" prefix.
Thus, some problem in GCC's Git/Bugzilla hooks?
I think it also recognizes bug NNNN and matches any whitespace in between
the bug and word and number. The commit message has:
Perhaps we should match only at most one newline (but that is non-fun with
the various Unix/MSDOS/MacOS line endings), or not match if the number is
followed by - without whitespace?
Perhaps we should restrict that to a single line, ie only horizontal
white space. Our commit style isn't really that free-form when citing
bugs. Or perhaps require [:.]?\w after the number (ie an optional
period or colon and then some white space).