This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Wrong GCC PR2020 annotated for "[committed, libgomp,amdgcn] Fix plugin-gcn.c bug"
- From: Jakub Jelinek <jakub at redhat dot com>
- To: 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 16:28:43 +0100
- Subject: Re: Wrong GCC PR2020 annotated for "[committed, libgomp,amdgcn] Fix plugin-gcn.c bug"
- References: <b4733c3a-7555-816d-9290-18a8bad1e52b@codesourcery.com> <87blqutcx6.fsf@euler.schwinge.homeip.net>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Thu, Jan 23, 2020 at 04:23:01PM +0100, Thomas Schwinge wrote:
> Hi!
>
> On 2020-01-23T12:46:24+0000, Andrew Stubbs <ams@codesourcery.com> wrote:
> > I've committed this patch to fix a bug in the OpenMP argument parsing.
>
> <https://gcc.gnu.org/g:14e5e74698b98f4cbe398cb989dfa27765cbca6e>.
>
> 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:
.................................................... bug
2020-
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?
Jakub