ge 1? [...]
> >
> > Ok for stage1, thanks.
>
> Thanks. I've now pushed "[OpenMP, gimplifier] 'inform' after 'error'
> diagnostic" to master branch in commit
> 4f2ab6b89e170f1343f935761481c3745fe603b1, see attached.
Forgot about somethi
Geschäftsführer: Thomas Heurung, Alexander
Walter
>From 4f2ab6b89e170f1343f935761481c3745fe603b1 Mon Sep 17 00:00:00 2001
From: Thomas Schwinge
Date: Thu, 30 Apr 2020 09:07:06 +0200
Subject: [PATCH] [OpenMP, gimplifier] 'inform' after 'error' diagnostic
This is not a th
On Thu, Apr 30, 2020 at 12:07:32PM +0200, Thomas Schwinge wrote:
> Hi!
>
> Is the attached OK for master branch, in next stage 1? It may even be
> obvious, per our diagnostic conventions? If approving this patch, please
> respond with "Reviewed-by: NAME " so that your effort will be
> recorded i
Date: Thu, 30 Apr 2020 09:07:06 +0200
Subject: [PATCH] [OpenMP, gimplifier] 'inform' after 'error' diagnostic
This is not a thorough review of the code, just a few cases I noticed while
scanning 'gcc/gimplify.c' for "enclosing".
gcc/
* gimplify
