> From: haochen.jiang
> Sent: Friday, November 1, 2024 4:32 PM
>
> On Linux/x86_64,
>
> e9ab41b79933d42410126f0eb7b29f820745276c is the first bad commit commit
> e9ab41b79933d42410126f0eb7b29f820745276c
> Author: Hu, Lin1
> Date: Fri Nov 1 10:04:40 2024 +0800
>
> Support Intel MOVRS
>
>
; > >
> > > On Tue, Sep 3, 2024 at 9:45 AM Jiang, Haochen via Gcc-regression
> > > wrote:
> > > >
> > > > As each AVX10.2 testcases previously, this is caused by option
> combination
> > > warning,
> > > > which is expe
0_2-bf-vector-
> cmpp-1.c (test for excess errors) on Linux/x86_64
>
> On Tue, Sep 3, 2024 at 9:45 AM Jiang, Haochen via Gcc-regression
> wrote:
> >
> > As each AVX10.2 testcases previously, this is caused by option combination
> warning,
> > which is expected.
&g
As each AVX10.2 testcases previously, this is caused by option combination
warning,
which is expected.
> From: haochen.jiang
> Sent: Monday, September 2, 2024 9:06 PM
>
> On Linux/x86_64,
>
> f77435aa3911c437cba71991509eee57b333b3ce is the first bad commit commit
> f77435aa3911c437cba71991509e
As applied to all AVX10.2 patches, it is caused by vector size warning
mentioned previously.
Thx,
Haochen
> -Original Message-
> From: haochen.jiang
> Sent: Monday, August 26, 2024 11:54 PM
> To: jun.zh...@intel.com; gcc-regression@gcc.gnu.org; gcc-
> patc...@gcc.gnu.org; Jiang, Haochen
The three avx10.2 related test regression are all related to the usage of
-mavx10.2 -march=cascadelake, which is unavoidable warning.
I am considering to change -march=cascadelake to a arch with AVX10 in
the future to avoid these false alarms.
Thx,
Haochen
> -Original Message-
> From: ha
> -Original Message-
> From: Sam James
> Sent: Thursday, August 15, 2024 6:30 AM
> To: Jiang, Haochen
> Cc: gcc-regression@gcc.gnu.org; gcc-testresu...@gcc.gnu.org;
> g...@gcc.gnu.org
> Subject: Re: gcc-regression script build fail info
>
> "Jiang, Haochen" writes:
>
> > Ping for this
Ping for this thread.
Any ideas? If no, I will change the generated info with command following
if we take r15-1643 as example and see if it is clearer:
head -26 makelog.r15-1643.x86_64.native | tail -7 > 1.log;
grep -E "(error:|Error)" makelog.r15-1643.x86_64.native >> 1.log;
echo "=
Ah... When I solved the huge conflict this morning due to AVX10 refactor for
GCC13/12, I forgot that it is in GCC14 AVX10.1 refactor when I added the
_mm_avx512_setzero_ps/pd. Should use _mm_setzero_ps/pd instead.
Never do something tweak quickly on a sleepy Monday morning.
Thx,
Haochen
> -O
> -Original Message-
> From: Jakub Jelinek
> Sent: Wednesday, July 24, 2024 1:09 PM
> To: Jiang, Haochen
> Cc: j...@ventanamicro.com; gcc-regression@gcc.gnu.org; gcc-
> patc...@gcc.gnu.org
> Subject: Re: [r15-2196 Regression] FAIL: c-c++-common/dfp/convert-bfp-6.c
> -std=gnu++98 execut
It might be a false positive timeout alert. Please ignore that first.
Thx,
Haochen
> -Original Message-
> From: haochen.jiang
> Sent: Tuesday, July 23, 2024 7:51 PM
> To: j...@ventanamicro.com; gcc-regression@gcc.gnu.org; gcc-
> patc...@gcc.gnu.org; Jiang, Haochen
> Subject: [r15-2196 R
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
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
> -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
> > 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: Sam James
> Sent: Thursday, July 18, 2024 12:48 PM
> To: haoch...@gnu-skx-1.sc.intel.com
> Cc: gcc-regression@gcc.gnu.org; gcc-testresu...@gcc.gnu.org; Jiang, Haochen
>
> Subject: Re: master branch: commit r15-2116 failed to bootstrap on
> Linux/x86_64 (commit
The fail is expected since -march=cascadelake -mavx10.1-256 will lead to a
warning.
Also, we could not use -mno-avx512f with -mavx10.1-256, which also lead to a
warning.
> -Original Message-
> From: haochen.jiang
> Sent: Monday, June 3, 2024 10:22 PM
> To: Jiang, Haochen ; gcc-regressio
On Linux/x86_64,
a9251ab3c91c8c559d0306838575a666ae62dff4 is the first bad commit
commit a9251ab3c91c8c559d0306838575a666ae62dff4
Author: Richard Biener
Date: Thu May 16 12:35:28 2024 +0200
wrong code with points-to and volatile
caused
with GCC configured with
../../gcc/configure
--pr
Hi Matthias,
From my side, I get several error like this:
/export/users/haochenj/src/gcc-bisect/master/master/r15-429/bld/x86_64-linux/32/libstdc++-v3/include/experimental/bits/simd_builtin.h:131:
error: could not convert
'std::experimental::parallelism_v2::__vec_shuffle<__vector(4) wchar_t,
_
19 matches
Mail list logo
