On Wed, 30 Aug 2023, Juzhe-Zhong wrote:
> Like ARM SVE, when we enable scalable vectorization for RVV,
> we can't do constant fold for these yet for both ARM SVE and RVV.
>
>
> Ok for trunk ?
OK.
> gcc/testsuite/ChangeLog:
>
> * gcc.dg/vect/pr88598-1.c: Add riscv_vector.
> *
Like ARM SVE, when we enable scalable vectorization for RVV,
we can't do constant fold for these yet for both ARM SVE and RVV.
Ok for trunk ?
gcc/testsuite/ChangeLog:
* gcc.dg/vect/pr88598-1.c: Add riscv_vector.
* gcc.dg/vect/pr88598-2.c: Ditto.
*
On 8/28/23 21:31, Tsukasa OI wrote:
From: Tsukasa OI
arch-24.c and arch-25.c are exactly the same and redundant. The author
suspects that the original author intended to test two base ISAs (RV32I and
RV64I) so this commit changes arch-24.c to test that RV32I+Zcf does not
cause any errors
Committed, thanks Kito.
Pan
-Original Message-
From: Kito Cheng
Sent: Tuesday, August 29, 2023 9:46 PM
To: Li, Pan2
Cc: gcc-patches@gcc.gnu.org; Wang, Yanzhang ;
juzhe.zh...@rivai.ai
Subject: Re: [PATCH v1] RISC-V: Fix one ICE for vect test vect-multitypes-5
LGTM, thanks :)
On Tue
LGTM, thanks :)
On Tue, Aug 29, 2023 at 6:50 PM Pan Li via Gcc-patches
wrote:
>
> From: Pan Li
>
> There will be one ICE when build vect-multitypes-5.c similar as below:
>
> riscv64-unknown-elf-gcc -O3 \
> -march=rv64imafdcv -mabi=lp64d -mcmodel=medlow \
> -fdiagnostics-plain-output -flto
From: Pan Li
There will be one ICE when build vect-multitypes-5.c similar as below:
riscv64-unknown-elf-gcc -O3 \
-march=rv64imafdcv -mabi=lp64d -mcmodel=medlow \
-fdiagnostics-plain-output -flto -ffat-lto-objects \
--param riscv-autovec-preference=scalable -Wno-psabi \
-ftree-vectorize
Committed, thanks Richard.
On 2023/8/29 14:53, Richard Biener via Gcc-patches wrote:
On Tue, 29 Aug 2023, Juzhe-Zhong wrote:
We are planning to enable "vect" testsuite with scalable vector
auto-vectorization.
This case XPASS:
XPASS: gcc.dg/vect/no-scevccp-outer-12.c scan-tree-dump-times
On Tue, 29 Aug 2023, Juzhe-Zhong wrote:
> We are planning to enable "vect" testsuite with scalable vector
> auto-vectorization.
>
> This case XPASS:
> XPASS: gcc.dg/vect/no-scevccp-outer-12.c scan-tree-dump-times vect "OUTER
> LOOP VECTORIZED." 1
>
> like ARM SVE.
OK
> ---
>
We are planning to enable "vect" testsuite with scalable vector
auto-vectorization.
This case XPASS:
XPASS: gcc.dg/vect/no-scevccp-outer-12.c scan-tree-dump-times vect "OUTER LOOP
VECTORIZED." 1
like ARM SVE.
---
gcc/testsuite/gcc.dg/vect/no-scevccp-outer-12.c | 2 +-
1 file changed, 1
From: Tsukasa OI
arch-24.c and arch-25.c are exactly the same and redundant. The author
suspects that the original author intended to test two base ISAs (RV32I and
RV64I) so this commit changes arch-24.c to test that RV32I+Zcf does not
cause any errors.
gcc/testsuite/ChangeLog
as GCC assumed multi-letter
>> 'Z' extensions are three letters or more).
>>
>> After rejecting unrecognized extensions, "dg-error" is added **just to
>> avoid the test failure** and that doesn't look right. Yes, we now don't
>> have an ICE (like in th
extensions, "dg-error" is added **just to
avoid the test failure** and that doesn't look right. Yes, we now don't
have an ICE (like in the original report) but after the PR 102957 fix,
we just accepted it, not rejecting it.
Instead, we have a valid (recognized) two-letter 'Z' extension
ones
(aarch64_operands_adjust_ok_for_ldpstp): Add option-value check and
alignment check and remove superseded ones.
* config/aarch64/aarch64.opt: Add options.
gcc/testsuite/ChangeLog:
* gcc.target/aarch64/ldp_aligned.c: New test.
* gcc.target/aarch64
Committed.
Fix failures:
FAIL: gcc.target/riscv/rvv/vsetvl/vlmax_bb_prop-10.c -O2
scan-assembler-times
add\\ta[0-7],a[0-7],a[0-7]\\s+\\.L[0-9][0-9][0-9]\\:\\s+vle32\\.v\\s+(?:v[0-9]|v[1-2][0-9]|v3[0-1]),0\\s*\\([a-x0-9]+\\)
1
FAIL: gcc.target/riscv/rvv/vsetvl/vlmax_bb_prop-10.c -O2
Jivan's recent work on IRA results in more efficient code for this test.
This adjusts the expected output for the removal of 5 instructions and
conversion of an addi into a simple mv.
Pushed to the trunk,
Jeffcommit 6567837fd823a93f7f7948a73ff9dc1153592e8c
Author: Jeff Law
Date: Sun Aug
Log:
PR preprocessor/90400
* c-c++-common/cpp/pr90400.c: New test.
---
gcc/testsuite/c-c++-common/cpp/pr90400.c | 14 ++
1 file changed, 14 insertions(+)
create mode 100644 gcc/testsuite/c-c++-common/cpp/pr90400.c
diff --git a/gcc/testsuite/c-c++-common/cpp/pr90400.c
On 8/24/23 09:45, Jivan Hakobyan via Gcc-patches wrote:
Subject:
RISC-V: Fix stack_save_restore_1/2 test cases
From:
Jivan Hakobyan via Gcc-patches
Date:
8/24/23, 09:45
To:
GCC Patches , Jeff Law
This patch fixes failing stack_save_restore_1/2 test cases.
After 6619b3d4c15c commit size
wrote:
> Hi Jivan,
>
> On 8/24/23 08:45, Jivan Hakobyan via Gcc-patches wrote:
> > This patch fixes failing stack_save_restore_1/2 test cases.
> > After 6619b3d4c15c commit size of the frame was changed.
> >
> >
> > gcc/testsuite/ChangeLog:
> >
Hi Jivan,
On 8/24/23 08:45, Jivan Hakobyan via Gcc-patches wrote:
This patch fixes failing stack_save_restore_1/2 test cases.
After 6619b3d4c15c commit size of the frame was changed.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/stack_save_restore_1.c: Update frame size
This patch fixes failing stack_save_restore_1/2 test cases.
After 6619b3d4c15c commit size of the frame was changed.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/stack_save_restore_1.c: Update frame size
* gcc.target/riscv/stack_save_restore_2.c: Likewise.
--
With the best
From: Paul Dreik
Tested x86_64-linux. Pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
PR libstdc++/02
* testsuite/std/format/string.cc: Check wide character format
strings with out-of-range widths.
---
libstdc++-v3/testsuite/std/format/string.cc | 15
Tested x86_64-linux. Pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
* testsuite/std/format/functions/format_to.cc: Avoid warning for
unused variables.
---
libstdc++-v3/testsuite/std/format/functions/format_to.cc | 8
1 file changed, 4 insertions(+), 4 deletions(-)
The test is for loop vectorization producing non-canonical
multiplications. We can now BB vectorize the whole function
when the target supports .REDUC_PLUS for V2SImode but we don't
have a dejagnu selector for that. Disable BB vectorization
like we disabled epilogue vectorization.
Tested
FAIL: gcc.target/riscv/rvv/autovec/gather-scatter/gather_load_run-12.c
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/gather-scatter/gather_load_run-12.c: Add
vsetvli asm.
---
.../riscv/rvv/autovec/gather-scatter/gather_load_run-12.c | 6 ++
1 file changed, 6
'. It makes sense to test the standard version
alongside the
deprecated one, especially on systems which don't have the nonstandard
function.
* The testcase unconditionally used an XFAIL version in the tgamma{,f} test, but
the comment indicated that it is only needed for newlib; hence, the XFAIL
h naming in the source itself, so...
>> Would it make sense to skip the first check here
>> (check_effective_target_riscv_v) so we have a proper runtime check?
>
> My starting point was that the changing of global testsuite variables around -
> as the original RISC-V
This is the patch resolving the non-portable test that Iain raised in:
https://gcc.gnu.org/pipermail/libstdc++/2023-August/056534.html
Tested x86_64-linux. Pushed to trunk.
Backports would be OK, but I don't think they are needed.
-- >8 --
This test case calls std::set_terminate wh
On Sun, Aug 20, 2023 at 12:24 PM FX Coudert via Gcc-patches
wrote:
>
> Hi,
>
> On darwin (both x86_64-apple-darwin and aarch64-apple-darwin) we see the
> following test failure:
>
> FAIL: gcc.dg/lto/20091013-1 c_lto_20091013-1_2.o assemble, -fPIC -r -nostdlib
> -O
Hi,
> IMO, changes like this qualify as obvious, so I’d go ahead (thanks for this
> test fail triage)
Makes sense. I’ve committed, as well as another one, attached, slightly
amending the expected pattern of a sarif plugin test.
FX
0001-Testsuite-plugin-make-testcase-patter
Hi FX,
> On 20 Aug 2023, at 13:15, FX Coudert via Gcc-patches
> wrote:
> The fact that this test needs alias support was indicated in
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85656 but never committed.
> Without it, the test fails on darwin.
>
> OK to commi
Hi,
The fact that this test needs alias support was indicated in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85656 but never committed. Without
it, the test fails on darwin.
OK to commit?
FX
0001-Testsuite-mark-IPA-test-as-requiring-alias-support.patch
Description: Binary data
Hi,
On darwin (both x86_64-apple-darwin and aarch64-apple-darwin) we see the
following test failure:
FAIL: gcc.dg/lto/20091013-1 c_lto_20091013-1_2.o assemble, -fPIC -r -nostdlib
-O2 -flto
which is due to this extra warning:
In function 'fontcmp',
inlined from 'find_in_cache' at
/tmp
Bordering on obvious, tested on darwin where the test case fails before (and
now passes).
OK to commit?
FX
0001-Testsuite-fix-contructor-priority-test.patch
Description: Binary data
t; -I/usr/include/python3.10 -I/usr/include/python3.10
>> > Executing on host: /some/sysroot/bin/aarch64-unknown-linux-gnu-gcc --
>> > sysroot=/some/sysroot/libc -Wl,-dynamic-
>> > linker=/some/sysroot/libc/lib/ld-linux-aarch64.so.1 -Wl,-
>> > rpath=/some/sysroot/li
arch64-unknown-linux-gnu-gcc --
> > sysroot=/some/sysroot/libc -Wl,-dynamic-
> > linker=/some/sysroot/libc/lib/ld-linux-aarch64.so.1 -Wl,-
> > rpath=/some/sysroot/libc/lib
> > /some/src/gcc.git/gcc/testsuite/gcc.dg/plugin/cpython-plugin-test-
> > 2.c-fdiagnost
on host: /some/sysroot/bin/aarch64-unknown-linux-gnu-gcc --
> sysroot=/some/sysroot/libc -Wl,-dynamic-
> linker=/some/sysroot/libc/lib/ld-linux-aarch64.so.1 -Wl,-
> rpath=/some/sysroot/libc/lib
> /some/src/gcc.git/gcc/testsuite/gcc.dg/plugin/cpython-plugin-test-
> 2.c -fdia
ones
(aarch64_operands_adjust_ok_for_ldpstp): Add option-value check and
alignment check and remove superseded ones.
* config/aarch64/aarch64.opt: Add options.
gcc/testsuite/ChangeLog:
* gcc.target/aarch64/ldp_aligned.c: New test.
* gcc.target/aarch64
oot/libc/lib/ld-linux-aarch64.so.1
-Wl,-rpath=/some/sysroot/libc/lib
/some/src/gcc.git/gcc/testsuite/gcc.dg/plugin/cpython-plugin-test-2.c
-fdiagnostics-plain-output -fplugin=./analyzer_cpython_plugin.so -fanalyzer
-I/usr/include/python3.10 -I/usr/include/python3.10 -S -o
cpython-plugin-test-
:
* gcc.target/riscv/zbb-rol-ror-08.c: New test.
* gcc.target/riscv/zbb-rol-ror-09.c: New test.
Co-authored-by: Charlie Jenkins
Signed-off-by: Patrick O'Neill
OK
jeff
Committed
IIRC this came up in the context of Linux's TCP checksum code.
Patrick
On 8/16/23 21:36, Jeff Law wrote:
On 8/16/23 19:17, Patrick O'Neill wrote:
This adds new regression tests to ensure half-register rotations are
correctly optimized into rori instructions.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/zbb-rol-ror-08.c: New test.
* gcc.target/riscv/zbb
The following guards the bit test merging code in if-combine against
the appearance of SSA names used in abnormal PHIs.
Bootstrapped and tested on x86_64-unknown-linux-gnu, pushed.
PR tree-optimization/111039
* tree-ssa-ifcombine.cc (ifcombine_ifandif): Check
> I'm not opposed to merging the test change, but I couldn't figure out
> where in C the implicit conversion was coming from: as far as I can
> tell the macros don't introduce any (it's "return _float16 *
> _float16"), I'd had the patch open since last night but couldn't
&g
On 8/16/23 19:17, Patrick O'Neill wrote:
This adds new regression tests to ensure half-register rotations are
correctly optimized into rori instructions.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/zbb-rol-ror-08.c: New test.
* gcc.target/riscv/zbb-rol-ror-09.c: New test
This adds new regression tests to ensure half-register rotations are
correctly optimized into rori instructions.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/zbb-rol-ror-08.c: New test.
* gcc.target/riscv/zbb-rol-ror-09.c: New test.
Co-authored-by: Charlie Jenkins
Signed-off
. The problem is not the
reduction but the additional return-value conversion that is omitted
when calculating the reference value inline.
The attached is simpler and does the trick.
Regards
Robin
Subject: [PATCH v2] RISC-V: Fix reduc_strict_run-1 test case.
This patch fixes
On Wed, Aug 16, 2023 at 4:15 PM Patrick O'Neill wrote:
>
> This adds new regression tests to ensure half-register rotations are
> correctly optimized into rori instructions.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/riscv/zbb-rol-ror-04.c: Add half-register rotation
> cases.
>
This adds new regression tests to ensure half-register rotations are
correctly optimized into rori instructions.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/zbb-rol-ror-04.c: Add half-register rotation
cases.
* gcc.target/riscv/zbb-rol-ror-05.c: Add half-register rotation
conversion that is omitted
when calculating the reference value inline.
The attached is simpler and does the trick.
Regards
Robin
Subject: [PATCH v2] RISC-V: Fix reduc_strict_run-1 test case.
This patch fixes the reduc_strict_run-1 testcase by converting
the reference value to double and back
Pushed to trunk.
-- >8 --
These tests were derived from set.pass.cpp not set.pass.cc, specifically
pstl/test/std/algorithms/alg.sorting/alg.set.operations/set.pass.cpp in
the LLVM repo.
libstdc++-v3/ChangeLog:
* testsuite/25_algorithms/pstl/alg_sorting/set_difference.cc:
tted
when calculating the reference value inline.
The attached is simpler and does the trick.
Regards
Robin
Subject: [PATCH v2] RISC-V: Fix reduc_strict_run-1 test case.
This patch fixes the reduc_strict_run-1 testcase by converting
the reference value to double and back to the tested type.
Without tha
LGTM
juzhe.zh...@rivai.ai
From: Robin Dapp
Date: 2023-08-15 23:49
To: gcc-patches; palmer; Kito Cheng; jeffreyalaw; juzhe.zh...@rivai.ai
CC: rdapp.gcc
Subject: [PATCH] RISC-V: Fix reduc_strict_run-1 test case.
Hi,
this patch changes the equality check for the reduc_strict_run-1
testcase
On 8/15/23 19:21, juzhe.zh...@rivai.ai wrote:
For float/double, the in-order fold-left reduction produced the same
result as scalar codes.
But for _Float16 is not, I think the issue is not the reduction issue,
is float 16 precision issue.
But if it's a float16 precision issue then I would
; palmer; Kito Cheng; juzhe.zh...@rivai.ai
Subject: Re: [PATCH] RISC-V: Fix reduc_strict_run-1 test case.
On 8/15/23 09:49, Robin Dapp wrote:
> Hi,
>
> this patch changes the equality check for the reduc_strict_run-1
> testcase from == to fabs () < EPS. The FAIL only occurs
Log:
* gcc.target/riscv/rvv/autovec/reduc/reduc_strict_run-1.c:
Check float equality with fabs < EPS.
Generally agree with using an EPS test.
The question is shouldn't a fold-left reduction be done in-order and
produce the same result as a scalar equivalent?
Jeff
Hi,
this patch changes the equality check for the reduc_strict_run-1
testcase from == to fabs () < EPS. The FAIL only occurs with
_Float16 but I'd argue approximate equality is preferable for all
float modes.
Regards
Robin
gcc/testsuite/ChangeLog:
*
; > + return 1
> > +}
> > +
> > +# Possible future extensions: If the target is a simulator,
> > dg-add-options
> > +# might change its config to make it allow vector insns, or we might
> > use
> > + # options to set special elf flags
>> commit 6f709f79c915a ("[committed] [RISC-V] Fix expected diagnostic
>> messages
>> in testsuite") "fixed" test failures caused by that change (on
>> pr102957.c,
>> by testing the error message after the first change).
>>
>> However, the
es
in testsuite") "fixed" test failures caused by that change (on pr102957.c,
by testing the error message after the first change).
However, the latter change will break the original intent of PR 102957 test
case because we wanted to make sure that we can parse a valid two-lette
From: Tsukasa OI
Commit c283c4774d1c ("RISC-V: Throw compilation error for unknown
extensions") changed how do we handle unknown extensions and
commit 6f709f79c915a ("[committed] [RISC-V] Fix expected diagnostic messages
in testsuite") "fixed" test failures caused
On Thu, 10 Aug 2023, Jakub Jelinek via Gcc-patches wrote:
> Hi!
>
> The following patch (on top of the stdckdint.h patch and _BitInt patch
> series) adds a test for _BitInt diagnostics of ckd_{add,sub,mul} macros.
I remain unconvinced that diagnosing use with types where it'
Hi!
The following patch (on top of the stdckdint.h patch and _BitInt patch
series) adds a test for _BitInt diagnostics of ckd_{add,sub,mul} macros.
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
2023-08-10 Jakub Jelinek
* gcc.dg/stdckdint-3.c: New test
Committed, thanks Jeff.
Pan
-Original Message-
From: Jeff Law
Sent: Tuesday, August 8, 2023 10:10 PM
To: Li, Pan2 ; gcc-patches@gcc.gnu.org
Cc: juzhe.zh...@rivai.ai; kito.ch...@sifive.com; Wang, Yanzhang
Subject: Re: [PATCH v1] RISC-V: Enhance the test case for RVV vfsub/vfrsub
On 8/2/23 01:59, Pan Li via Gcc-patches wrote:
From: Pan Li
This patch would like to enhance the vfsub/vfrsub rounding API test for
below 2 purposes.
* The non-rm API has no frm related insn generated.
* The rm API has the frm backup/restore/set insn generated.
Signed-off-by: Pan Li
gcc
Kindly ping.
Pan
-Original Message-
From: Li, Pan2
Sent: Wednesday, August 2, 2023 3:59 PM
To: gcc-patches@gcc.gnu.org
Cc: juzhe.zh...@rivai.ai; kito.ch...@sifive.com; Li, Pan2 ;
Wang, Yanzhang
Subject: [PATCH v1] RISC-V: Enhance the test case for RVV vfsub/vfrsub rounding
From: Pan
On Thu, Aug 3, 2023 at 6:27 AM Richard Biener via Gcc-patches
wrote:
>
> zstdtest has some inline data where some testcases lack the
> uncompressed length field. Thus it computes that but still
> ends up allocating memory for the uncompressed buffer based on
> that (zero) length. Oops. Causes
The ICE in PR analyzer/108171 appears to be a dup of the recently fixed
PR analyzer/110882 and is likewise fixed by it; adding this test case.
Successfully regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r14-2957-gf80efa49b7a163.
gcc/testsuite/ChangeLog:
PR analyzer/108171
zstdtest has some inline data where some testcases lack the
uncompressed length field. Thus it computes that but still
ends up allocating memory for the uncompressed buffer based on
that (zero) length. Oops. Causes memory corruption if the
allocator returns non-NULL.
Tested on
On 8/3/23 08:48, Stefan Schulze Frielinghaus wrote:
> This enables the following tests which rely on instruction vperm which
> is available since z13 with the initial vector support.
>
> testsuite/gcc.dg/vect/vect-bswap16.c
> 42:/* { dg-final { scan-tree-dump-times "vectorized 1 loops" 1 "vect" {
This enables the following tests which rely on instruction vperm which
is available since z13 with the initial vector support.
testsuite/gcc.dg/vect/vect-bswap16.c
42:/* { dg-final { scan-tree-dump-times "vectorized 1 loops" 1 "vect" { target
{ vect_bswap || sse4_runtime } } } } */
From: Pan Li
This patch would like to enhance the vfsub/vfrsub rounding API test for
below 2 purposes.
* The non-rm API has no frm related insn generated.
* The rm API has the frm backup/restore/set insn generated.
Signed-off-by: Pan Li
gcc/testsuite/ChangeLog:
* gcc.target/riscv
nge its config to make it allow vector insns, or we might use
> +# options to set special elf flags / sections to effect that.
> +
> +return 0
> +}
So in general we would add {dg-add-options riscv_v} for every
test that requires compile-time vector support?
Fo
/vector/bool/110807.cc (test for excess errors)
with GCC configured with
../../gcc/configure
--prefix=/export/users/haochenj/src/gcc-bisect/master/master/r14-2797/usr
--enable-clocale=gnu --with-system-zlib --with-demangler-in-ld
--with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet
Recent change modified how the loops are created, with the first
iteration being extracted out of the loops in the 2 test cases.
Adjust the text to match from the unroll dump.
gcc/testsuite/ChangeLog:
* gnat.dg/unroll3.adb: Adjust.
---
Tested on x86_64-pc-linux-gnu, committed on master
AIL: gfortran.dg/gomp/pr99226.f90 -O (test for excess errors)
with GCC configured with
../../gcc/configure
--prefix=/export/users/haochenj/src/gcc-bisect/master/master/r14-2754/usr
--enable-clocale=gnu --with-system-zlib --with-demangler-in-ld
--with-fpmath=sse --enable-languages=c,c++,fort
(test for excess errors)
FAIL: g++.dg/gomp/pr58567.C -std=c++17 (test for excess errors)
FAIL: g++.dg/gomp/pr58567.C -std=c++20 (test for excess errors)
FAIL: g++.dg/gomp/pr58567.C -std=c++98 (test for excess errors)
with GCC configured with
../../gcc/configure
--prefix=/export/users/haochenj
On 7/21/23 09:16, Siddhesh Poyarekar wrote:
The test deliberately reads beyond bounds to exersize ubsan and the
return value may be anything, based on previous allocations. The OFF
test caters for it by ANDing the return with 0, do the same for the DYN
test.
gcc/testsuite/ChangeLog
gt; looking at
> and possibly turn it into a testcase?
Yeah, it does! Thanks for the quick fix.
The test was gcc.target/aarch64/sve/live_1.c. Although it wasn't
originally a profile test, I think it should still be a relatively good
way of testing that the latch is treated as more likely than t
Avoid scaling flat loop profiles of vectorized loops
As discussed, when vectorizing loop with static profile, it is not always good
idea
to divide the header frequency by vectorization factor because the profile may
not realistically represent the expected number of iterations. Since in such
The test deliberately reads beyond bounds to exersize ubsan and the
return value may be anything, based on previous allocations. The OFF
test caters for it by ANDing the return with 0, do the same for the DYN
test.
gcc/testsuite/ChangeLog:
PR testsuite/110763
* gcc.dg/ubsan
l for all
>> functions wrongly. The commit r13-4294 for PR99889 has
>> fixed this with the corresponding label LPFE* which sits in
>> the function_section.
>>
>> As Fangrui suggested[1], this patch is to add a bit more test
>> coverage. I didn't find a good way t
4294 for PR99889 has
> fixed this with the corresponding label LPFE* which sits in
> the function_section.
>
> As Fangrui suggested[1], this patch is to add a bit more test
> coverage. I didn't find a good way to check all linked_to
> symbols are different, so I checked for LPFE[012] here.
>
> [1]
/cpp0x/udlit-extended-id-1.C -std=c++14 (test for excess errors)
FAIL: g++.dg/cpp0x/udlit-extended-id-1.C -std=c++17 (test for excess errors)
FAIL: g++.dg/cpp0x/udlit-extended-id-1.C -std=c++20 (test for excess errors)
FAIL: g++.dg/cpp0x/udlit-extended-id-3.C -std=c++14 (test for excess errors)
FAIL
in
the function_section.
As Fangrui suggested[1], this patch is to add a bit more test
coverage. I didn't find a good way to check all linked_to
symbols are different, so I checked for LPFE[012] here.
[1] https://gcc.gnu.org/pipermail/gcc-patches/2023-July/624866.html
Tested well on x86_64-redhat
t;>
>> Honza, Richi, any thoughts? Just wanted to double-check that this
>> was operating as expected before making the tests accept the (arguably)
>> less efficient code. It looks like the commit was more aimed at fixing
>> the profile counts for the epilogues, rath
Richard Biener writes:
> On Thu, 20 Jul 2023, Richard Sandiford wrote:
>
>> Tamar Christina writes:
>> > Hi All,
>> >
>> > The resulting predicate register of a whilelo is not
>> > restricted to the lower half of the predicate register file.
>> >
>> > As such these tests started failing after
fixing
> the profile counts for the epilogues, rather than the main loop.
You are right that we shold not scale down static profiles in case they
are artifically flat. It is nice to have actual testcase.
Old code used to test:
/* Without profile feedback, loops for which we do not k
On Thu, 20 Jul 2023, Richard Sandiford wrote:
> Tamar Christina writes:
> > Hi All,
> >
> > The resulting predicate register of a whilelo is not
> > restricted to the lower half of the predicate register file.
> >
> > As such these tests started failing after recent changes
> > because the
Tamar Christina writes:
> Hi All,
>
> The resulting predicate register of a whilelo is not
> restricted to the lower half of the predicate register file.
>
> As such these tests started failing after recent changes
> because the whilelo outside the loop is getting assigned p15.
It's the whilelo
Hi All,
The resulting predicate register of a whilelo is not
restricted to the lower half of the predicate register file.
As such these tests started failing after recent changes
because the whilelo outside the loop is getting assigned p15.
This widens the regexp.
Tested on
This makes it easier to write tests that safely test features needing
d, v and/or zfh extensions.
check_effective_target_riscv_v checks if the current target allows to
use vector instructions.
add_options_for_riscv_v ask to add an -arch option to change the
target to one like the current one
Committed, thanks Juzhe.
Pan
From: juzhe.zh...@rivai.ai
Sent: Tuesday, July 18, 2023 10:53 AM
To: Li, Pan2 ; gcc-patches
Cc: Li, Pan2 ; Wang, Yanzhang ;
kito.cheng
Subject: Re: [PATCH v2] RISC-V: Fix RVV frm run test failure on RV32
LGTM.
juzhe.zh
LGTM.
juzhe.zh...@rivai.ai
From: pan2.li
Date: 2023-07-18 10:49
To: gcc-patches
CC: juzhe.zhong; pan2.li; yanzhang.wang; kito.cheng
Subject: [PATCH v2] RISC-V: Fix RVV frm run test failure on RV32
From: Pan Li
Refine the run test case to avoid interactive checking in RV32, by
separating
: Re: [PATCH v1] RISC-V: Fix RVV frm run test failure on RV32
LGTM
juzhe.zh...@rivai.ai<mailto:juzhe.zh...@rivai.ai>
From: pan2.li<mailto:pan2...@intel.com>
Date: 2023-07-14 21:20
To: gcc-patches<mailto:gcc-patches@gcc.gnu.org>
CC: juzhe.zho
From: Pan Li
Refine the run test case to avoid interactive checking in RV32, by
separating each checks in different functions.
Signed-off-by: Pan Li
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/base/float-point-frm-run-1.c: Fix run failure.
---
.../riscv/rvv/base/float-point-frm
LGTM
juzhe.zh...@rivai.ai
From: pan2.li
Date: 2023-07-14 21:20
To: gcc-patches
CC: juzhe.zhong; pan2.li; yanzhang.wang; kito.cheng
Subject: [PATCH v1] RISC-V: Fix RVV frm run test failure on RV32
From: Pan Li
Refine the run test case to avoid interactive checking in RV32, by
separating
From: Pan Li
Refine the run test case to avoid interactive checking in RV32, by
separating each checks in different functions.
Signed-off-by: Pan Li
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/base/float-point-frm-run-1.c: Fix failure
on RV32.
---
.../riscv/rvv/base
On Linux/x86_64,
450b05ce54d3f08c583c3b5341233ce0df99725b is the first bad commit commit
450b05ce54d3f08c583c3b5341233ce0df99725b
Author: Tobias Burnus
Date: Wed Jul 12 13:50:21 2023 +0200
libgomp: Use libnuma for OpenMP's partition=nearest allocation trait
caused
with GCC configured
.cc -std=c++14 (test for excess errors)
FAIL: g++.dg/vect/pr110557.cc -std=c++17 (test for excess errors)
FAIL: g++.dg/vect/pr110557.cc -std=c++20 (test for excess errors)
FAIL: g++.dg/vect/pr110557.cc -std=c++98 (test for excess errors)
with GCC configured with
../../gcc/configure
--prefix
>From 5151cf943987347edbc3707f08f0da8cd9f49f88 Mon Sep 17 00:00:00 2001
From: Rishi Raj
Date: Fri, 7 Jul 2023 10:15:57 +0530
Subject: [PATCH] lto: Fixed test(U*) used but never defined error.
This Patch fixes the error during bootstrapped build.
Signed-off-by: Rishi Raj
---
gcc/lto-object
Tested x86_64-linux. Pushed to trunk.
-- >8 --
The header is only supported for the cxx11 ABI. The
declarations of basic_syncbuf, basic_osyncstream, syncbuf and
osyncstream were already correctly guarded by a check for
_GLIBCXX_USE_CXX11_ABI, but the wsyncbuf and wosyncstream declarations
were
901 - 1000 of 6355 matches
Mail list logo
