On Thu, Jun 5, 2025 at 5:19 PM Tomasz Kamiński wrote:
> We do not test with wchar_t currently, as operator<< (and format) are
> ill-formed in such case, because we do not widen abbrev member of
> local_info.
>
> Adding a tests for behavior of the ostream operator and the fo
t also reworks a bit
class_mandate_neg.cc test, as previously one error was not generated
when debug was enabled.
libstdc++-v3/include/std/mdspan| 18 +-
.../mdspan/layouts/class_mandate_neg.cc| 18 ++
2 files changed, 19 insertions(+), 17 del
We do not test with wchar_t currently, as operator<< (and format) are
ill-formed in such case, because we do not widen abbrev member of local_info.
Adding a tests for behavior of the ostream operator and the formatting
with empty chrono-spec for the chrono types. The coverage is now
co
On Thu, Jun 5, 2025 at 4:46 PM Tomasz Kamiński wrote:
> We do not test with wchar_t currently, as operator<< (and format) are
> ill-formed in such case, because we do not widen abbrev member of
> local_info.
>
> Adding a tests for behavior of the ostream operator and the fo
We do not test with wchar_t currently, as operator<< (and format) are
ill-formed in such case, because we do not widen abbrev member of local_info.
Adding a tests for behavior of the ostream operator and the formatting
with empty chrono-spec for the chrono types. The coverage is now
co
while merging profile.
>>* pass_manager.h (get_pass_auto_profile): New.
>>
>> gcc/testsuite/ChangeLog:
>>
>> * gcc.dg/tree-prof/clone-merge-1.c: New test.
>>
>> Is this OK?
> OK, thanks!
> It would be nice to also test that
dc++-v3/ChangeLog:
>> >
>> > * testsuite/std/time/format/empty_spec.cc: New tests.
>> >---
>> >The only change is mention of the duration test in commit message,
>> >after the rebase. OK for trunk?
>>
>> OK with one comment added, as sugge
point, zoned_time and local_time_format in this commit,
> > * duration and hh_mm_ss in r16-1099-gac0a04b7a254fb,
> > * calendar types in r16-1016-g28a17985dd34b7.
> >
> >libstdc++-v3/ChangeLog:
> >
> > * testsuite/std/time/format/empty_spec.cc: New tests.
> >---
>
-gac0a04b7a254fb,
* calendar types in r16-1016-g28a17985dd34b7.
libstdc++-v3/ChangeLog:
* testsuite/std/time/format/empty_spec.cc: New tests.
---
The only change is mention of the duration test in commit message,
after the rebase. OK for trunk?
OK with one comment added, as suggested below. Thanks
n_passes.
>
> gcc/ChangeLog:
>
> * auto-profile.cc (autofdo_source_profile::read): Dump message
> while merging profile.
> * pass_manager.h (get_pass_auto_profile): New.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.dg/tree-prof/clone-merge-1.c: Ne
point, zoned_time and local_time_format in this commit,
> * duration and hh_mm_ss in r16-1099-gac0a04b7a254fb,
> * calendar types in r16-1016-g28a17985dd34b7.
>
> libstdc++-v3/ChangeLog:
>
> * testsuite/std/time/format/empty_spec.cc: New tests.
> ---
> The only ch
On Wed, 4 Jun 2025, 12:05 Daniel Krügler, wrote:
> Am Mi., 4. Juni 2025 um 12:57 Uhr schrieb Tomasz Kaminski <
> tkami...@redhat.com>:
>
>>
>>
>> On Wed, Jun 4, 2025 at 12:43 PM Daniel Krügler
>> wrote:
>>
>>> Am Mi., 4. Juni 2025 um 11:27 Uhr schrieb Tomasz Kamiński <
>>> tkami...@redhat.com>:
e also need to specialize the other:
>> > Moreover, common_type_t shall denote the same type, if any, as
>> does common_type_t.
>> <https://eel.is/c++draft/meta.trans.other#5.sentence-4>
>> > No diagnostic is required for a violation of this Note's rules.
>> <https://eel.is/c++draft/meta.trans.other#5.sentence-5>
>> "shall" are requirements on the users.
>>
>
> Yes you are right, sorry for the noise.
>
FWIW, I initially wrote the test with only one of these specializations, as
you suggested.
Adding the second one was driven by compiler errors.
>
> - Daniel
>
>
>
-g28a17985dd34b7.
libstdc++-v3/ChangeLog:
* testsuite/std/time/format/empty_spec.cc: New tests.
---
The only change is mention of the duration test in commit message,
after the rebase. OK for trunk?
.../testsuite/std/time/format/empty_spec.cc | 208 --
1 file changed, 194 insertions
Am Mi., 4. Juni 2025 um 12:57 Uhr schrieb Tomasz Kaminski <
tkami...@redhat.com>:
>
>
> On Wed, Jun 4, 2025 at 12:43 PM Daniel Krügler
> wrote:
>
>> Am Mi., 4. Juni 2025 um 11:27 Uhr schrieb Tomasz Kamiński <
>> tkami...@redhat.com>:
>>
>>> [...]
>>> +
>>> +template
>>> + requires std::is_integr
mat_to, when duration with custom representation
>> types
>> are used.
>>
>> It's also adding the test for behavior of ostream operator and the
>> formatting
>> with empty chron-spec for the chrono types. Current coverage is:
>> * duration and hh_mm_ss in t
Am Mi., 4. Juni 2025 um 11:27 Uhr schrieb Tomasz Kamiński <
tkami...@redhat.com>:
> This patches fixes an obvious error, where the output iterator argument was
> missing for call to format_to, when duration with custom representation
> types
> are used.
>
> It's also
On Wed, 4 Jun 2025, 10:27 Tomasz Kamiński, wrote:
> This patches fixes an obvious error, where the output iterator argument was
> missing for call to format_to, when duration with custom representation
> types
> are used.
>
> It's also adding the test for behavior of o
This patches fixes an obvious error, where the output iterator argument was
missing for call to format_to, when duration with custom representation types
are used.
It's also adding the test for behavior of ostream operator and the formatting
with empty chron-spec for the chrono types. Cu
:
* auto-profile.cc (autofdo_source_profile::read): Dump message
while merging profile.
* pass_manager.h (get_pass_auto_profile): New.
gcc/testsuite/ChangeLog:
* gcc.dg/tree-prof/clone-merge-1.c: New test.
Is this OK?
Thanks,
Kugan
0001-AutoFDO_v2-Profile-merging-for-clone
/time/format/empty_spec.cc: New tests.
---
Tested on x86_64-linux. OK for trunk.
The test coverage reflects my current progress in decopling format("{}",
t) for os << t. The compilation time for the file is already noticeable,
so this file will be good one for quick testing o
Check the appropriate feature test macro instead of checking that
__cplusplus >= 201703L.
libstdc++-v3/ChangeLog:
* include/std/stop_token: Check __glibcxx_jthread instead of
__cplusplus.
---
Tested x86_64-linux. Pushed to trunk.
libstdc++-v3/include/std/stop_token
Hi!
The test PASSes for C, but FAILs for C++:
.../libgomp.c-c++-common/omp_target_memset-3.c: In function 'void
test_it(void*, int, size_t)':
.../libgomp.c-c++-common/omp_target_memset-3.c:31:7: warning: pointer of type
'void *' used in arithmetic [-Wpointer-arith]
.../
From: Pan Li
Add asm dump check test for vec_duplicate + vdiv.vv combine to vdiv.vx,
with the GR2VR cost is 0, 2 and 15.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-1-i16.c: Add
From: Pan Li
Add asm dump check test for vec_duplicate + vdiv.vv combine to vdiv.vx,
with the GR2VR cost is 0, 1 and 2.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-4-i16.c: Add
From: Pan Li
Some existing vdiv related test need some adjust for the
asm check.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/binop/vdiv-rv32gcv-nofm.c: Adjust
the asm check for vdiv.
* gcc.target/riscv/rvv/autovec/binop/vdiv-rv32gcv.c: Ditto
the return value) to r3 the incoming memory address. Both of
> > are valid.
> >
> > Adjust the test to match what GCC is producing now.
> >
> > gcc/testsuite/ChangeLog:
> >
> > * gcc.target/or1k/return-2.c: Fix test.
> Given you're the mai
On 5/31/25 12:03 AM, Stafford Horne wrote:
In or1k structs are returned from functions using the memory address
passed in r3. In the current version of GCC the struct stores changed
from r11 (the return value) to r3 the incoming memory address. Both of
are valid.
Adjust the test to match
In or1k structs are returned from functions using the memory address
passed in r3. In the current version of GCC the struct stores changed
from r11 (the return value) to r3 the incoming memory address. Both of
are valid.
Adjust the test to match what GCC is producing now.
gcc/testsuite
On Fri, 30 May 2025 at 15:26, Tomasz Kaminski wrote:
>
>
>
> On Fri, May 30, 2025 at 1:55 PM Jonathan Wakely wrote:
>>
>> On Fri, 30 May 2025 at 10:38, Tomasz Kamiński wrote:
>> >
>> > Adding a test for behavior of the ostream operator and the for
On Fri, May 30, 2025 at 1:55 PM Jonathan Wakely wrote:
> On Fri, 30 May 2025 at 10:38, Tomasz Kamiński wrote:
> >
> > Adding a test for behavior of the ostream operator and the formatting
> > with empty chron-spec for the chrono types. This commit covers calendar
> >
From: Waffl3x
libgomp/ChangeLog:
* testsuite/libgomp.c++/target-flex-10.C: New test.
* testsuite/libgomp.c++/target-flex-100.C: New test.
* testsuite/libgomp.c++/target-flex-101.C: New test.
* testsuite/libgomp.c++/target-flex-11.C: New test.
* testsuite
On Fri, 30 May 2025 at 10:38, Tomasz Kamiński wrote:
>
> Adding a test for behavior of the ostream operator and the formatting
> with empty chron-spec for the chrono types. This commit covers calendar
> types.
>
> libstdc++-v3/ChangeLog:
>
> * testsuite/std/time/f
Adding a test for behavior of the ostream operator and the formatting
with empty chron-spec for the chrono types. This commit covers calendar
types.
libstdc++-v3/ChangeLog:
* testsuite/std/time/format/empty_spec.cc: New test.
---
Tested on x86_64-linux. OK for trunk?
.../testsuite/std
there might be a disconnect
> > between those predicates and the presence of a vuse (I hope not, but ...)
> >
> > The patch looks OK to me, the comments above apply to the copy propagation
> > case.
>
> The copy prop case should be ok too since the vuse/vdef on the
>
From: Pan Li
Add asm and run testcase for avg_ceil vaadd implementation.
The below test suites are passed for this patch series.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/avg.h: Add test helper macros.
* gcc.target/riscv/rvv
From: Pan Li
Some existing avg_floor test need updated due to change to
leverage vaadd.vv directly.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vls/avg-4.c: Update asm check
to vaadd.
* gcc.target/riscv/rvv/autovec/vls/avg-5.c: Ditto.
* gcc.target
nt does not change when doing the prop; only the rhs of the
statement. There is no inserting of a statement. This is unless we
remove the statement and then unlink_stmt_vdef will prop the vuse into
the vdef of the statement which we are removing.
I did test the copy prop using just SSA_NAME_IS_D
On AIX printf formats a quiet NaN as "NaNQ" and it doesn't matter
whether %f or %F is used. Similarly, it always prints "INF" for
infinity, even when %f is used. Adjust a test that currently fails due
to this AIX-specific (and non-conforming) behaviour
Commit the test file `cmpbr.c` before rules for generating the new
instructions are added, so that the changes in codegen are more obvious
in the next commit.
gcc/testsuite/ChangeLog:
* lib/target-supports.exp: Add `cmpbr` to the list of extensions.
* gcc.target/aarch64/cmpbr.c
From: Pan Li
Add asm dump check test for vec_duplicate + vmul.vv combine to vmul.vx,
with the GR2VR cost is 0, 1 and 2.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-4-i16.c: Add
From: Pan Li
Add asm dump check test for vec_duplicate + vmul.vv combine to vmul.vx,
with the GR2VR cost is 0, 2 and 15.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-1-i16.c: Add
From: Pan Li
Add asm and run testcase for avg_floor vaadd implementation.
The below test suites are passed for this patch series.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/avg.h: New test.
* gcc.target/riscv/rvv/autovec
From: Pan Li
Some existing avg_floor test need updated due to change to
leverage vaadd.vv directly.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vls/avg-1.c: Update asm check
to vaadd.
* gcc.target/riscv/rvv/autovec/vls/avg-2.c: Ditto.
* gcc.target
On the 13 branch and older, C++ >= 20 tests need an explicit dg-options
directive specifying the -std flag, otherwise they won't run by default.
PR libstdc++/112490
libstdc++-v3/ChangeLog:
* testsuite/24_iterators/const_iterator/112490.cc: Add
dg-options directive.
---
l
On 5/27/25 2:19 PM, Harald Anlauf wrote:
Jerry, all,
that was entirely my fault - attempting a last-minute cleanup
that reordered code, trying to use a refactoring. I've put
on my brown bag and pushed a corrections as obvious as:
r16-921-g74a2281ae18c6d.
See attached.
Caveat: this was tested
No failures after reverting this:
commit r16-914-g787a8dec1acedf5561c8ee43bed0b3653fca150d
Author: Harald Anlauf
As my daughter would say. It happens to the best of us.
Jerry
--- snip ---
FAIL: gfortran.dg/associate_68.f90 -O0 (test for excess errors)
FAIL: gfortran.dg/associate_68.f90
Anlauf
As my daughter would say. It happens to the best of us.
Jerry
--- snip ---
FAIL: gfortran.dg/associate_68.f90 -O0 (test for excess errors)
FAIL: gfortran.dg/associate_68.f90 -O1 (test for excess errors)
FAIL: gfortran.dg/associate_68.f90 -O2 (test for excess errors)
FAIL
libstdc++-v3/ChangeLog:
* testsuite/17_intro/names.cc [_AIX] (n): Undefine.
* testsuite/experimental/names.cc [_AIX] (ptr): Undefine.
---
Tested x86_64-linux and powerpc-aix.
Pushed to trunk.
libstdc++-v3/testsuite/17_intro/names.cc | 2 ++
libstdc++-v3/testsuite/experimenta
On Tue, 27 May 2025 at 13:46, Tomasz Kaminski wrote:
>
>
>
> On Tue, May 27, 2025 at 2:38 PM Jonathan Wakely wrote:
>>
>> With -maix32 (the default) we only have 16-bit wchar_t so these tests
>> fail. The debug.cc one is because we use -fwide-exec-charset=UTF-32BE
>> which tries to encode each wi
On Tue, May 27, 2025 at 2:38 PM Jonathan Wakely wrote:
> With -maix32 (the default) we only have 16-bit wchar_t so these tests
> fail. The debug.cc one is because we use -fwide-exec-charset=UTF-32BE
> which tries to encode each wide character as four bytes in a 2-byte
> wchar_t. The format.cc one
With -maix32 (the default) we only have 16-bit wchar_t so these tests
fail. The debug.cc one is because we use -fwide-exec-charset=UTF-32BE
which tries to encode each wide character as four bytes in a 2-byte
wchar_t. The format.cc one is because the clown face character can't be
encoded in a single
On Tue, May 27, 2025 at 5:02 AM Andrew Pinski wrote:
>
> This was noticed in the review of copy propagation for aggregates
> patch, instead of checking for a NULL or a non-ssa name of vuse,
> we should instead check if it the vuse is a default name and stop
> then.
>
> Bootstrapped and tested on x
This was noticed in the review of copy propagation for aggregates
patch, instead of checking for a NULL or a non-ssa name of vuse,
we should instead check if it the vuse is a default name and stop
then.
Bootstrapped and tested on x86_64-linux-gnu.
gcc/ChangeLog:
* tree-ssa-forwprop.cc (o
From: Pan Li
Add asm and run testcase for avg_floor vaadd implementation.
The below test suites are passed for this patch series.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/avg.h: New test.
* gcc.target/riscv/rvv/autovec
From: Pan Li
Some existing avg_floor test need updated due to change to
leverage vaadd.vv directly.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vls/avg-1.c: Update asm check
to vaadd.
* gcc.target/riscv/rvv/autovec/vls/avg-2.c: Ditto.
* gcc.target
In indirect/ctor.cc test_inplace_ctor function was defined, but never
called.
PR libstdc++/119152
libstdc++-v3/ChangeLog:
* testsuite/std/memory/indirect/ctor.cc: Run test_inplace_ctor.
---
Tested on x86_64-linux. Pushed to trunk.
libstdc++-v3/testsuite/std/memory/indirect/ctor
From: Pan Li
Add asm dump check test for vec_duplicate + vxor.vv combine to vxor.vx,
with the GR2VR cost is 0, 2 and 15.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-1-i16.c: Add
From: Pan Li
Add asm dump check test for vec_duplicate + vxor.vv combine to vxor.vx,
with the GR2VR cost is 0, 1 and 2.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-4-i16.c: Add
From: Pan Li
Add asm dump check test for vec_duplicate + vor.vv combine to vor.vx,
with the GR2VR cost is 0, 1 and 2.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-4-i16.c: Add asm
From: Pan Li
Add asm dump check test for vec_duplicate + vor.vv combine to vor.vx,
with the GR2VR cost is 0, 2 and 15.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-1-i16.c: Add
These were fixed upstream by:
https://github.com/uxlfoundation/oneDPL/pull/534
https://github.com/uxlfoundation/oneDPL/pull/546
libstdc++-v3/ChangeLog:
* testsuite/util/pstl/test_utils.h (ForwardIterator::operator++):
Fix return type.
(BidirectionalIterator::operator++): L
Thanks. I will pay attention to this.
Dongyan Chen
在 2025/5/22 11:49, Jeff Law 写道:
On 5/21/25 9:16 PM, Dongyan Chen wrote:
Failed testcases occurred in the regression test of gcc:
cset-sext-sfb.c failed
the -Oz test, and zba-slliuw.c failed the -Og test.
This patch solves the problem by
On 5/21/25 9:16 PM, Dongyan Chen wrote:
Failed testcases occurred in the regression test of gcc: cset-sext-sfb.c failed
the -Oz test, and zba-slliuw.c failed the -Og test.
This patch solves the problem by skipping the optimization.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/cset
Failed testcases occurred in the regression test of gcc: cset-sext-sfb.c failed
the -Oz test, and zba-slliuw.c failed the -Og test.
This patch solves the problem by skipping the optimization.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/cset-sext-sfb.c: Skip for -Oz.
* gcc.target
From: Pan Li
Add asm dump check test for vec_duplicate + vand.vv combine to vand.vx,
with the GR2VR cost is 0, 2 and 15.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-1-i16.c: Add
From: Pan Li
Add asm dump check test for vec_duplicate + vand.vv combine to vand.vx,
with the GR2VR cost is 0, 1 and 2.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-4-i16.c: Add
/callind.c -O0 (internal compiler error:
Segmentation fault)
FAIL: gcc.c-torture/compile/callind.c -O0 (test for excess errors)
FAIL: gcc.c-torture/compile/callind.c -O1 (internal compiler error:
Segmentation fault)
FAIL: gcc.c-torture/compile/callind.c -O1 (test for excess errors)
FAIL
1
> FAIL: gcc.dg/tree-ssa/pr81627.c scan-tree-dump-times pcom "Store-stores
> chain" 1
This is just an extra inlining which causes pcom to happen twice now.
Will look into fix that this coming week.
> FAIL: gcc.target/i386/avx512vl-vpmovuswb-2.c (test for excess errors)
> FAI
-dump-times vect "Alignment of
access forced using peeling" 1
FAIL: gcc.dg/tree-ssa/gen-vect-28.c scan-tree-dump-times vect "vectorized 1
loops" 1
FAIL: gcc.dg/tree-ssa/pr81627.c scan-tree-dump-times pcom "Store-stores chain" 1
FAIL: gcc.target/i386/avx512vl-vpmovus
From: Pan Li
Add asm dump check test for vec_duplicate + vrsub.vv combine to vrsub.vx
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-2-i16.c: Add vrsub asm
dump check
From: Pan Li
Add asm dump check test for vec_duplicate + vrsub.vv combine to vrsub.vx.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-5-i16.c: Add asm check
for vrsub with
From: Pan Li
Add asm dump check test for vec_duplicate + vrsub.vv combine to vrsub.vx.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-6-i16.c: Add asm check
for vrsub with
From: Pan Li
Tweak the asm check with define T uint8_t for adding more
vx test easily, as well as less possibility to make mistake.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-1
From: Pan Li
Add asm dump check test for vec_duplicate + vrsub.vv combine to vrsub.vx.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-4-i16.c: Add asm check
for vrsub case 1
From: Pan Li
Add asm dump check and run test for vec_duplicate + vrsub.vv combine to
vrsub.vx.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-1-i16.c: Add vrsub asm check
From: Pan Li
Add asm dump check test for vec_duplicate + vrsub.vv combine to vrsub.vx.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-3-i16.c: Add asm check
for vrsub with
On 5/16/25 2:38 AM, pan2...@intel.com wrote:
From: Pan Li
Some of the previous scalar unsigned SAT_ADD test data are
duplicated in different test files. This patch would like to
move them into a shared header file, to avoid the test data
duplication.
The below test suites are passed for
1,3 @@
-// { dg-do compile { target c++17 } }
-
#include "coro.h"
// Test that we get matching types to traits and promise param
base-commit: de3cbcf9730b60db76c31c5b628f4bf2ebd6b284
--
2.49.0
Commit the test file `cmpbr.c` before rules for generating the new
instructions are added, so that the changes in codegen are more obvious
in the next commit.
gcc/testsuite/ChangeLog:
* lib/target-supports.exp: Add `cmpbr` to the list of extensions.
* gcc.target/aarch64/cmpbr.c
From: Pan Li
Some of the previous scalar unsigned SAT_ADD test data are
duplicated in different test files. This patch would like to
move them into a shared header file, to avoid the test data
duplication.
The below test suites are passed for this patch series.
* The rv64gcv fully regression
Commit the test file `cmpbr.c` before rules for generating the new
instructions are added, so that the changes in codegen are more obvious
in the next commit.
gcc/testsuite/ChangeLog:
* lib/target-supports.exp: Add `cmpbr` to the list of extensions.
* gcc.target/aarch64/cmpbr.c
From: Pan Li
Add asm dump check test for vec_duplicate + vsub.vv combine to vsub.vx.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-4-i16.c: Add test cases
for vsub vx
From: Pan Li
For run test, we have a name like add/sub to indicate
the testcase. So we can reuse this to identify the
test data instead of a new one.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv
From: Pan Li
Add asm dump check test for vec_duplicate + vsub.vv combine to vsub.vx.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-3-i16.c: Add test cases
for vsub vx
From: Pan Li
Add asm dump check test for vec_duplicate + vsub.vv combine to vsub.vx.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-6-i16.c: Add test cases
for vsub vx
From: Pan Li
Given we will put all vx combine for int8 in a single file,
we need to make sure the generate function for different
types and ops has different function name. Thus, refactor
the test helper macros for avoiding possible function name
conflict.
The below test suites are passed for
From: Pan Li
Add asm dump check and run test for vec_duplicate + vsub.vv
combine to vsub.vx.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-1-i16.c: Add vector sub
vx
From: Pan Li
Add asm dump check test for vec_duplicate + vsub.vv combine to vsub.vx.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-5-i16.c: Add test cases
for vsub vx
From: Pan Li
Add asm dump check test for vec_duplicate + vsub.vv combine to vsub.vx
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-2-i16.c: Add test cases
for vsub vx
Thomas Schwinge wrote:
On 2025-05-12T17:03:29+0200, I wrote:
"Add effective-target 'offload_device_usm',
'libgomp.c-c++-common/target-usm-1.c'"
On top, we could then add the attached
"libgomp: Add a few more OpenMP/USM test cases"? These all PASS for
Hi!
On 2025-05-12T17:03:29+0200, I wrote:
> "Add effective-target 'offload_device_usm',
> 'libgomp.c-c++-common/target-usm-1.c'"
On top, we could then add the attached
"libgomp: Add a few more OpenMP/USM test cases"? These all PASS for GCN
gfx9
From: Pan Li
Add asm dump check test for vec_duplicate + vsub.vv combine to vsub.vx.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx_vsub-4-i16.c: New test.
* gcc.target
From: Pan Li
Add asm dump check test for vec_duplicate + vsub.vv combine to vsub.vx.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx_vsub-6-i16.c: New test.
* gcc.target
From: Pan Li
Add asm dump check and run test for vec_duplicate + vsub.vv
combine to vsub.vx.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx_binary_data.h: Add test
data for
From: Pan Li
Add asm dump check test for vec_duplicate + vsub.vv combine to vsub.vx.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx_vsub-3-i16.c: New test.
* gcc.target
From: Pan Li
Add asm dump check test for vec_duplicate + vsub.vv combine to vsub.vx.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx_vsub-5-i16.c: New test.
* gcc.target
From: Pan Li
Add asm dump check test for vec_duplicate + vsub.vv combine to vsub.vx
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx_vsub-2-i16.c: New test.
* gcc.target/riscv
On Apr 16, 2025, Alexandre Oliva wrote:
> On Apr 14, 2025, Peter Bergner wrote:
>> On 4/11/25 1:03 PM, Alexandre Oliva wrote:
>>> gcc.dg/pr87600.h and gcc.dg/pr89313.c test for __powerpc__ and
>>> __POWERPC__ to choose ppc register names, but ppc-elf defines neither;
In r15-3752-g48261bd26df624 I added a test plugin that overrode the
regular output, instead emitting diagnostics in crude HTML form.
In r15-4760-g0b73e9382ab51c I added support for multiple kinds of
diagnostic output simultaneously, adding
-fdiagnostics-add-output=DIAGNOSTICS-OUTPUT-SPEC
1 - 100 of 2083 matches
Mail list logo
