> > For future reports, would it be possible to change the grep to
> > something
> > like:
> >
> > grep -E "(error:|Error)" or just grep -rsin "error" -w or something.
> >
> > This would allow catching the actual compile error in libbacktrace if
> > it's not going to fit in the last N lines from ma
> -Original Message-
> From: Jiang, Haochen
> Sent: Thursday, July 18, 2024 3:46 PM
> To: 'Sam James'
> Cc: 'gcc-regression@gcc.gnu.org' ; 'gcc-
> testresu...@gcc.gnu.org' ; g...@gcc.gnu.org
> Subject: gcc-regression script build fail info
>
> > > For future reports, would it be possib
Regressions on master at commit r15-2128 vs commit r15-2126 on Linux/x86_64
New failures:
New passes:
FAIL: gcc.dg/torture/convert-dfp-2.c -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects (test for excess errors)
FAIL: gcc.dg/torture/convert-dfp.c -O2 -flto -fuse-linker-plugin
-fno-fat-lt
Regressions on master at commit r15-2137 vs commit r15-2128 on Linux/x86_64
New failures:
FAIL: libgomp.oacc-fortran/privatized-ref-2.f90 -DACC_DEVICE_TYPE_host=1
-DACC_MEM_SHARED=1 -foffload=disable -O0 at line 32 (test for warnings, line
31)
FAIL: libgomp.oacc-fortran/privatized-ref-2.f90 -D
Regressions on master at commit r15-2138 vs commit r15-2132 on Linux/i686
New failures:
FAIL: libgomp.oacc-fortran/privatized-ref-2.f90 -DACC_DEVICE_TYPE_host=1
-DACC_MEM_SHARED=1 -foffload=disable -O0 at line 32 (test for warnings, line
31)
FAIL: libgomp.oacc-fortran/privatized-ref-2.f90 -DAC
Regressions on master at commit r15-2138 vs commit r15-2129 on Linux/x86_64
New failures:
FAIL: libgomp.oacc-fortran/privatized-ref-2.f90 -DACC_DEVICE_TYPE_host=1
-DACC_MEM_SHARED=1 -foffload=disable -O0 at line 32 (test for warnings, line
31)
FAIL: libgomp.oacc-fortran/privatized-ref-2.f90 -D
On Linux/x86_64,
c3aa339ea50f050caf7ed2e497f5499ec2d7b9cc is the first bad commit
commit c3aa339ea50f050caf7ed2e497f5499ec2d7b9cc
Author: Paul Thomas
Date: Thu Jul 18 08:51:35 2024 +0100
Fortran: Suppress bogus used uninitialized warnings [PR108889].
caused
FAIL: libgomp.oacc-fortran/pri
Hi Haochen,
Try removing lines 37-41 since these are precisely the bogus warnings that
the patch is meant to eliminate.
Regards
Paul
On Thu, 18 Jul 2024 at 14:38, haochen.jiang
wrote:
> On Linux/x86_64,
>
> c3aa339ea50f050caf7ed2e497f5499ec2d7b9cc is the first bad commit
> commit c3aa339ea50f
Dear contributor, our automatic CI has detected problems related to your
patch(es). Please find some details below. If you have any questions, please
follow up on linaro-toolch...@lists.linaro.org mailing list, Libera's
#linaro-tcwg channel, or ping your favourite Linaro toolchain developer on
Regressions on releases/gcc-14 at commit r14-10461 vs commit r14-10460 on
Linux/x86_64
New failures:
FAIL: libgomp.c/../libgomp.c-c++-common/for-3.c execution test
FAIL: libgomp.c/../libgomp.c-c++-common/for-5.c execution test
FAIL: libgomp.c/../libgomp.c-c++-common/for-9.c execution test
New pas
Hi Paul,
I suspect it is not the correct way to do that, those lines are ok since they
are XFAIL. The problem is that specific warning test.
Thx,
Haochen
From: Paul Richard Thomas
Sent: Friday, July 19, 2024 12:28 AM
To: haochen.jiang
Cc: pa...@gcc.gnu.org; gcc-regression@gcc.gnu.org; gcc-pat
Just did a quick test. Correct myself previously. Those lines also
needs to be removed since they are XPASS now.
However the real issue is the dg-note at Line 32, that is the warning
disappeared.
diff --git a/libgomp/testsuite/libgomp.oacc-fortran/privatized-ref-2.f90
b/libgomp/testsuite/libgomp
Dear contributor, our automatic CI has detected problems related to your
patch(es). Please find some details below. If you have any questions, please
follow up on linaro-toolch...@lists.linaro.org mailing list, Libera's
#linaro-tcwg channel, or ping your favourite Linaro toolchain developer on
13 matches
Mail list logo