For a non-multilib build, I see following errors.
| FAIL: gcc.target/riscv/rvv/vtype-call-clobbered.c (test for excess errors)
| Excess errors:
| TC-INSTxyz/sysroot/usr/include/gnu/stubs.h:14:11: fatal error:
gnu/stubs-lp64.h: No such file or directory compilation terminated.
The test selects no
On Wed, Jun 04, 2025 at 03:47:31PM +, Alfie Richards wrote:
> Hi,
>
> This fixes the FMV powerpc tests I recently committed, and hopefully makes
> them
> work on a wider range of target configurations.
>
> I plan to commit this on Monday if no one has any objections.
I, the sole maintainer
OK.
--
Regards
Robin
For a non-multilib build, I see following errors.
| FAIL: gcc.target/riscv/rvv/vtype-call-clobbered.c (test for excess errors)
| Excess errors:
| TC-INSTxyz/sysroot/usr/include/gnu/stubs.h:14:11: fatal error:
gnu/stubs-lp64.h: No such file or directory compilation terminated.
The test selects no
Testcase pr119160.c fails with symbol referencing errors for
`__cyg_profile_func_enter` and `__cyg_profile_func_exit` on non-glibc
systems.
This patch adds empty definitions for `__cyg_profile_func_enter`
and `__cyg_profile_func_exit` in order to prevent those errors.
PR testsuite/119862
Hi,
This fixes the FMV powerpc tests I recently committed, and hopefully makes them
work on a wider range of target configurations.
I plan to commit this on Monday if no one has any objections.
Thanks,
Alfie
--- >8 ---
As discussed on the BZ page, this removes the tests on the symbols in the
r
Todorovic; c...@mips.com
Subject: Re: [PATCH 07/61] Testsuite: Fix tests properly for compact-branches
Hi,
> This likely needs to be updated for the trunk.
> Before:
> === gcc Summary ===
> # of expected passes95
> # of unexpected failures
On May 26, 2025, Xi Ruoyao wrote:
> gcc/testsuite/ChangeLog:
> * lib/target-supports-dg.exp (dg-do-if): Pass the line number
> to
> dg-do.
Thanks! I support that fix, FWIW.
Indeed, an identical fix was included (but remains unreviewed) in
https://gcc.gnu.org/pipermail/gcc-patches/
> > To: Andrew Pinski (QUIC)
> > > Cc: gcc-patches@gcc.gnu.org
> > > Subject: Re: [PATCH] testsuite: Fix pr101145inf*.c testcases
> > > [PR117494]
> > >
> > > Hi Andrew,
> > >
> > > On Sun, 17 Nov 2024 at 22:49, Andrew Pinski
> &g
,,
On Mon, 26 May 2025 at 12:54, Andrew Pinski (QUIC)
wrote:
>
> > -Original Message-
> > From: Christophe Lyon
> > Sent: Monday, May 26, 2025 3:09 AM
> > To: Andrew Pinski (QUIC)
> > Cc: gcc-patches@gcc.gnu.org
> > Subject: Re: [PATCH]
> -Original Message-
> From: Christophe Lyon
> Sent: Monday, May 26, 2025 3:09 AM
> To: Andrew Pinski (QUIC)
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] testsuite: Fix pr101145inf*.c testcases
> [PR117494]
>
> Hi Andrew,
>
> On Sun, 17 Nov 2024
Hi Andrew,
On Sun, 17 Nov 2024 at 22:49, Andrew Pinski wrote:
>
> Instead of doing a dg-run with a specific target check for linux.
> Use signal as the effective-target since this requires the use
> of ALARM signal to do the testing.
> Also use check_vect in the main and renames main to main1 to
I forgot to send this to the list :(.
Forwarded Message
From: Xi Ruoyao
To: Alexandre Oliva
Cc: Xi Ruoyao
Subject: [PATCH] testsuite: Fix up dg-do-if
Date: 05/26/25 17:59:32
The line number needs to be passed to dg-do, instead of being stripped.
Fixes 'compile: syntax
在 2025/5/23 下午7:07, Xi Ruoyao 写道:
On Fri, 2025-03-07 at 14:14 +0800, Lulu Cheng wrote:
By default, vectorization is not enabled on LoongArch,
resulting in the failure of these two test cases.
Hmm, but wouldn't every test in the vect/ directory automatically get -
mlsx (from DEFAULT_VECTCFLAGS
On Wed, May 21, 2025 at 07:34:27PM +0200, Stefan Schulze Frielinghaus wrote:
> libstdc++-v3/ChangeLog:
>
> * testsuite/std/format/parse_ctx.cc: Fix typo for bfloat16 guard.
> ---
> Ok for mainline?
Just realized that I can use my super powers ;-) and pushed as obvious
in commit 08b4f6198de
On Fri, 2025-03-07 at 14:14 +0800, Lulu Cheng wrote:
> By default, vectorization is not enabled on LoongArch,
> resulting in the failure of these two test cases.
Hmm, but wouldn't every test in the vect/ directory automatically get -
mlsx (from DEFAULT_VECTCFLAGS in lib/target-supports.exp)?
>
>
libstdc++-v3/ChangeLog:
* testsuite/std/format/parse_ctx.cc: Fix typo for bfloat16 guard.
---
Ok for mainline?
libstdc++-v3/testsuite/std/format/parse_ctx.cc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libstdc++-v3/testsuite/std/format/parse_ctx.cc
b/libstdc++-v
On PowerPC, there is a psabi warning for argument passing of a DFP vector.
We are not expecting this warning and we get a failure due to it.
Adding -Wno-psabi fixes the testcase.
Committed as obvious after a quick test.
gcc/testsuite/ChangeLog:
PR testsuite/119909
* gcc.dg/tortur
warning, only)
libgomp/testsuite/libgomp.c/interop-hip-nvidia-full.c and (work around
required in addition) testsuite/libgomp.c/interop-hipblas-nvidia-full.c
commit 8ef0518bce489c4c0c252a0e0c44193c5f7cf777
Author: Tobias Burnus
Date: Thu Apr 24 18:26:30 2025 +0200
libgomp/testsuite: Fix
HTEC Public
Hi,
> This likely needs to be updated for the trunk.
> Before:
> === gcc Summary ===
> # of expected passes95
> # of unexpected failures25
> After:
> === gcc Summary ===
> # of expected passes70
> # of unexpected
On 1/31/25 10:13 AM, Aleksandar Rakic wrote:
From: abennett
Cherry-picked 4420f953c31daf1991011d306a56ab74c39b44ee
and 83c13cb19cb1e87a25326024943b95930a17e86b
from https://github.com/MIPS/gcc
Signed-off-by: Andrew Bennett
Signed-off-by: Matthew Fortune
Signed-off-by: Faraz Shahbazker
Si
On Tue, Apr 15, 2025 at 02:38:19PM +, Kyrylo Tkachov wrote:
> Thanks! As discussed on IRC we’ll work on addressing these. I’ve pushed the
> patch with 6d9fdf4bf57 after one more bootstrap on aarch64-none-linux-gnu.
This broke
+FAIL: gcc.dg/completion-2.c (test for excess errors)
+FAIL: gcc.dg
Hi!
dg-additional-options followed by dg-options is ignored. I've added the
-w from there to dg-options and removed dg-additional-options.
Tested on x86_64-linux, committed to trunk as obvious.
2025-04-15 Jakub Jelinek
PR ipa/119318
* gcc.dg/ipa/pr119318.c: Remove dg-additio
Hi!
On Sat, Apr 12, 2025 at 12:19:28AM +0200, Martin Jambor wrote:
> 2025-04-11 Martin Jambor
>
> PR ipa/119318
> * gcc.dg/ipa/pr119318.c: New test.
> * gcc.dg/ipa/pr119530.c: Likwise.
I'm seeing
+FAIL: gcc.dg/ipa/pr119530.c execution test
on i686-linux. The problem is that
The aarch64_sve256_hw line forced the vector length, but didn't force
SVE itself. This meant that the associated:
/* { dg-final { scan-tree-dump "MASK_SCATTER_STORE" "vect" { target
aarch64_sve256_hw } } } */
wouldn't always fire. I imagine this was tested with SVE enabled by
default, which
Jakub Jelinek writes:
> On Thu, Mar 27, 2025 at 12:05:21AM +, Sam James wrote:
>> The test was being ignored because dg.exp looks for .C in g++.dg/.
>>
>> gcc/testsuite/ChangeLog:
>> PR middle-end/112938
>>
>> * g++.dg/strub-internal-pr112938.cc: Move to...
>> * g++.dg/strub-
Jakub Jelinek writes:
> Hi!
>
> r15-8956 changed in the test:
> -/* { dg-final { scan-assembler-times "ldclr\t" 16} */
> +/* { dg-final { scan-assembler-times "ldclr\t" 16 } */
> which made it even worse than before, when the directive has
> been silently ignored because it didn't match the regex
Hi!
r15-8956 changed in the test:
-/* { dg-final { scan-assembler-times "ldclr\t" 16} */
+/* { dg-final { scan-assembler-times "ldclr\t" 16 } */
which made it even worse than before, when the directive has
been silently ignored because it didn't match the regex for
directives. Now it matches it b
Thanks, pushed to trunk :)
On Mon, Mar 31, 2025 at 4:54 PM Liao Shihua wrote:
>
> Fix broken testsuite like
> "ERROR: gcc.target/riscv/cmo-zicbop-2.c -Os : 1: too many arguments for "
> dg-do 1 compile target { { rv32-*-*}} "
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/riscv/cmo-zicb
This is another case of a test that was both an executable test
requiring specific hardware and an assembler scan test. The
requirement for the hardware was masking some useful testing that
could be done (by scanning the assembly output) on almost all test
runs. Fixed in a similar manner to fmaxm
Fix broken testsuite like
"ERROR: gcc.target/riscv/cmo-zicbop-2.c -Os : 1: too many arguments for "
dg-do 1 compile target { { rv32-*-*}} "
gcc/testsuite/ChangeLog:
* gcc.target/riscv/cmo-zicbop-1.c: Fix missing { before target .
* gcc.target/riscv/cmo-zicbop-2.c: Likewise.
Christophe Lyon writes:
> Le dim. 30 mars 2025, 22:10, Sam James a écrit :
>
> Jakub Jelinek writes:
>
> > Hi!
> >
> > r15-8956 changed in the test:
> > -/* { dg-final { scan-assembler-times "ldclr\t" 16} */
> > +/* { dg-final { scan-assembler-times "ldclr\t" 16 } */
> > which made it ev
Le dim. 30 mars 2025, 22:10, Sam James a écrit :
> Jakub Jelinek writes:
>
> > Hi!
> >
> > r15-8956 changed in the test:
> > -/* { dg-final { scan-assembler-times "ldclr\t" 16} */
> > +/* { dg-final { scan-assembler-times "ldclr\t" 16 } */
> > which made it even worse than before, when the direc
On Mar 27, 2025, Jakub Jelinek wrote:
> Here is a fix, tested on x86_64-linux, ok for trunk?
> 2025-03-27 Jakub Jelinek
> * g++.dg/strub-internal-pr112938.C: Add dg-warning for c++20.
LGTM, thanks
--
Alexandre Oliva, happy hackerhttps://blog.lx.oliva.nom.br/
Free Softwar
I believe these don't get detected by DejaGnu's regexp.
Found by dg-lint.
Pushed to trunk as r15-8994-g1ee9caf2f84832.
libstdc++-v3/ChangeLog:
* testsuite/17_intro/shared_with_static_deps.cc: Fix malformed
dg-require-static-libstdcxx directive.
* testsuite/17_intro/static
Pushed to trunk as r15-8993-gc88abca94a6abb.
gcc/testsuite/ChangeLog:
* g++.dg/abi/pure-virtual1.C: Fix dg-require-weak directive.
* g++.target/i386/mangling-alias1.C: Fix dg-require-ifunc
directive.
---
gcc/testsuite/g++.dg/abi/pure-virtual1.C| 2 +-
gcc/testsuite
On Mar 27, 2025, at 12:29 PM, Jakub Jelinek wrote:
>
> On Thu, Mar 27, 2025 at 12:05:21AM +, Sam James wrote:
>> The test was being ignored because dg.exp looks for .C in g++.dg/.
>>
>> gcc/testsuite/ChangeLog:
>> PR middle-end/112938
>>
>> * g++.dg/strub-internal-pr112938.cc: Mov
On Thu, Mar 27, 2025 at 12:05:21AM +, Sam James wrote:
> The test was being ignored because dg.exp looks for .C in g++.dg/.
>
> gcc/testsuite/ChangeLog:
> PR middle-end/112938
>
> * g++.dg/strub-internal-pr112938.cc: Move to...
> * g++.dg/strub-internal-pr112938.C: ...here.
Tested x86_64-pc-linux-gnu, applying to trunk.
-- >8 --
gcc/testsuite/ChangeLog:
* g++.dg/template/explicit-args6.C: Remove an extra set of {} in
a dg-message.
---
gcc/testsuite/g++.dg/template/explicit-args6.C | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/g
Marek Polacek writes:
> On Thu, Mar 27, 2025 at 12:38:55AM +, Sam James wrote:
>> A handful of cosmetic ones in here but most meant the directive wasn't
>> doing anything.
>
> This patch breaks g++.dg/template/explicit-args6.C for me.
See PR119490. I can XFAIL it, but I think it may be a rea
On Thu, Mar 27, 2025 at 12:38:55AM +, Sam James wrote:
> A handful of cosmetic ones in here but most meant the directive wasn't
> doing anything.
This patch breaks g++.dg/template/explicit-args6.C for me.
> gcc/testsuite/ChangeLog:
>
> * g++.dg/cpp0x/udlit-namespace-ambiguous.C: Fix w
When the dg brackets were added, they forgot to add the brackets for the
scan-assembler-times directive.
Committed as obvious.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vls/merge-4.c: Fix typo
Signed-off-by: Edwin Lu
---
gcc/testsuite/gcc.target/riscv/rvv/autovec/vls/mer
I have a handful more of these left but those introduce FAILs, while
these all introduce new PASSes.
libstdc++-v3/ChangeLog:
* testsuite/std/format/string_neg.cc: Add missing brace for dg-error.
gcc/testsuite/ChangeLog:
* gcc.dg/analyzer/fd-datagram-socket.c: Fix 'dg-message' sp
This fixes some 'scan-tree-dump-times' (vs '-time') typos and one or
two others I noticed in passing.
gcc/testsuite/ChangeLog:
* g++.dg/warn/Winvalid-memory-model.C: Fix typo in comment.
* gcc.dg/builtin-dynamic-object-size-19.c: Ditto.
* gcc.dg/builtin-object-size-19.c: D
gcc/testsuite/ChangeLog:
* g++.dg/diagnostic/unclosed-extern-c.C: Fix 'dg-message' typo.
* g++.dg/warn/Wno-attributes-1.C: Ditto.
---
gcc/testsuite/g++.dg/diagnostic/unclosed-extern-c.C | 2 +-
gcc/testsuite/g++.dg/warn/Wno-attributes-1.C| 6 +++---
2 files changed, 4 inse
The dg-bogus directive here is trying to match -Warray-bounds or
-Wstringop-overflow, but it got the casing wrong on the latter.
gcc.dg/pr89350.c gets this right.
gcc/testsuite/ChangeLog:
PR middle-end/93437
* g++.dg/warn/Wstringop-overflow-5.C: Fix -Wstringop-overflow casing.
--
A handful of cosmetic ones in here but most meant the directive wasn't
doing anything.
gcc/testsuite/ChangeLog:
* g++.dg/cpp0x/udlit-namespace-ambiguous.C: Fix whitespace.
* g++.dg/cpp2a/constexpr-init21.C: Ditto.
* g++.dg/diagnostic/wrong-tag-1.C: Ditto.
* g++.dg/
On Wed, Mar 26, 2025 at 02:34:44PM -0400, David Malcolm wrote:
> Found by dg-lint.
>
> gcc/testsuite/ChangeLog:
> * gcc.dg/ipa/pr110377.c: Fix missing trailing " }" in dg-do
> directive.
> * gcc.dg/plugin/infoleak-1.c: Fix dg-bogus directive.
> * gcc.dg/pr101364-1.c: Fix mi
> You're right (although I don't remember which targets are
> non-external_musttail).
Several flavors of ARM and Power at least.
Found by dg-lint.
gcc/testsuite/ChangeLog:
* gcc.dg/ipa/pr110377.c: Fix missing trailing " }" in dg-do
directive.
* gcc.dg/plugin/infoleak-1.c: Fix dg-bogus directive.
* gcc.dg/pr101364-1.c: Fix missing trailing " }" in dg-options
directive.
* gcc.dg
On Tue, Mar 25, 2025 at 10:03:17AM -0600, Sandra Loosemore wrote:
> * gfortran.dg/gomp/append-args-interop.f90: New.
The test fails for me with
UNRESOLVED: gfortran.dg/gomp/append-args-interop.f90 -O scan-tree-dump
gimple "__builtin_GOMP_interop (99, 0, 0B, 0B, 0B, 0, 0B, 3,
intero
On Wed, Mar 26, 2025 at 10:10:07AM -0700, Andi Kleen wrote:
> Jakub Jelinek writes:
>
> > --- gcc/testsuite/g++.dg/opt/musttail2.C.jj 2025-03-24 13:27:44.329204196
> > +0100
> > +++ gcc/testsuite/g++.dg/opt/musttail2.C2025-03-24 13:28:08.975867389
> > +0100
> > @@ -0,0 +1,14 @@
> > +// PR i
On Tue, Mar 25, 2025 at 07:00:34PM -0500, Peter Bergner wrote:
> On 3/25/25 5:17 PM, Segher Boessenkool wrote:
> > On Tue, Mar 25, 2025 at 03:33:59PM -0500, Peter Bergner wrote:
> >> Segher, any reason you can give on why we shouldn't go the easy route to
> >> "fix" (yes, these are air-quotes) this
On 3/25/25 1:42 AM, jeevitha wrote:
> gcc/testsuite/
> PR testsuite/119382
> * gcc.target/powerpc/vsx-builtin-7.c: Add '-fno-ipa-icf' to dg-options.
>
> diff --git a/gcc/testsuite/gcc.target/powerpc/vsx-builtin-7.c
> b/gcc/testsuite/gcc.target/powerpc/vsx-builtin-7.c
> index 5095d5030
On 3/25/25 5:17 PM, Segher Boessenkool wrote:
> On Tue, Mar 25, 2025 at 03:33:59PM -0500, Peter Bergner wrote:
>> Segher, any reason you can give on why we shouldn't go the easy route to
>> "fix" (yes, these are air-quotes) this by using -fno-ipa-icf?
>
> One reason is that that option should not
On Tue, Mar 25, 2025 at 03:33:59PM -0500, Peter Bergner wrote:
> On 3/25/25 1:42 AM, jeevitha wrote:
> > gcc/testsuite/
> > PR testsuite/119382
> > * gcc.target/powerpc/vsx-builtin-7.c: Add '-fno-ipa-icf' to dg-options.
> >
> > diff --git a/gcc/testsuite/gcc.target/powerpc/vsx-builtin-7.c
Hi All,
The following patch has been tested on powerpc64le-linux and verified it's
fixed.
The test vsx-builtin-7.c was failing on powerpc64le-linux due to identical
function detection by ICF. This behavior was introduced by commit
r15-7961-gdc47161c1f32c3, which improved alias analysis in
ao_comp
From: Arthur Cohen
Some failures occur in the testsuite because we
did not account for the little-endian case.
gcc/testsuite/ChangeLog:
* rust/compile/issue-1446.rs: Add swap_bytes function.
* rust/compile/iterators1.rs: Remove unused {to, from}_le functions.
---
gcc/testsuite/
Since r15-3992-g698e0ec89bc096 we optimize x<=y && x>=y to x==y.
Honour signaling NaNs by using option -fsignaling-nans in order to
prevent this.
gcc/testsuite/ChangeLog:
* gcc.target/s390/zvector/autovec-double-signaling-eq-z13.c:
Honour sNaNs.
---
.../gcc.target/s390/zvector/au
Previously we optimized expressions of the form a < 0 ? -1 : 0 to
(signed)a >> 31 during vcond expanding. Since r15-1638-gaac00d09859cc5
this is done in match.pd. The implementation in the back end as well as
in match.pd are basically the same but still distinct. For the tests in
vcond-shift.c t
From: Matthew Fortune
Ensure micromips test does not get confused about library support.
Ensure insn-casesi.c and insn-tablejump.c can be executed.
Move the micromips/mips16 selection into the file as per function
attributes so that there is no requirement on having a full
micromips or mips16 ru
From: Andrew Bennett
gcc/
* testsuite/gcc.target/mips/near-far-1.c: Fix tests properly for
compact-branches (jals and balc).
* testsuite/gcc.target/mips/near-far-2.c: Likewise.
* testsuite/gcc.target/mips/near-far-3.c: Likewise.
* testsuite/gcc.target/mips/
Among other things, this testcase tests an addition of the four
values (n*4+[0:3])*9//2 for each n in [0:99]. The addition is
done in multiple integer and floating-point types and the test
is compiled with -ffast-math.
One of the floating-point types is _Float16, and as Andrew says
in the PR, _Fl
On 2025-03-11 16:13, Richard Earnshaw wrote:
On 11/03/2025 13:46, Torbjorn SVENSSON wrote:
Is it okay to backport below patch and r15-7890-gb7f5d911480 to
releases/gcc-14?
Yes, sure.
Pushed as r14.2.0-877-gf1dd3a17cf3 and r14.2.0-878-gde08b13018a.
Kind regards,
Torbjörn
R.
Kind reg
Is it okay to backport below patch and r15-7890-gb7f5d911480 to releases/gcc-14?
Kind regards,
Torbjörn
On 2025-03-11 12:06, Richard Earnshaw wrote:
GCC will complain if the -mcpu flag specifies a different architecture
to that specified in -march, but if the floating-point ABI is "soft",
then
On 11/03/2025 13:46, Torbjorn SVENSSON wrote:
Is it okay to backport below patch and r15-7890-gb7f5d911480 to
releases/gcc-14?
Yes, sure.
R.
Kind regards,
Torbjörn
On 2025-03-11 12:06, Richard Earnshaw wrote:
GCC will complain if the -mcpu flag specifies a different architecture
to that s
GCC will complain if the -mcpu flag specifies a different architecture
to that specified in -march, but if the floating-point ABI is "soft",
then differences in the floating-point architecture features are
ignored.
However, the arm_libc_fp_abi checks whether we change the FP ABI by
adding -mfloat-
After d34cda720988674bcf8a24267c9e1ec61335d6de, what was originally
not vectorizable can now be vectorized. So adjust
gcc.dg/vect/slp-26.c.
gcc/testsuite/ChangeLog:
* gcc.dg/vect/slp-26.c: Adjust.
---
gcc/testsuite/gcc.dg/vect/slp-26.c | 4 ++--
1 file changed, 2 insertions(+), 2 delet
By default, vectorization is not enabled on LoongArch,
resulting in the failure of these two test cases.
gcc/testsuite/ChangeLog:
* gcc.dg/vect/pr112325.c: Add the vector compilation
option '-mlsx' for LoongArch.
* gcc.dg/vect/pr117888-1.c: Likewise.
---
gcc/testsuite/gc
The issue is the same as 12383255fe4e82c31f5e42c72a8fbcb1b5dea35d.
Neither is .REDUC_PLUS set for V2SImode on LoongArch, so add it
to the list of targets not expecting BB vectorization.
gcc/testsuite/ChangeLog:
* gcc.dg/vect/bb-slp-77.c: Add loongarch*-*-* to the list
of expected
On Fri, Feb 28, 2025 at 9:40 AM Jakub Jelinek wrote:
>
> Hi!
>
> The testcase uses -m32 in dg-options, something we try hard not to do,
> if something should be tested only for -m32, it is { target ia32 } test,
> if it can be tested for -m64/-mx32 too, just some extra options are
> needed for ia32
On Fri, 28 Feb 2025, Jakub Jelinek wrote:
> Hi!
>
> The testcase uses -m32 in dg-options, something we try hard not to do,
> if something should be tested only for -m32, it is { target ia32 } test,
> if it can be tested for -m64/-mx32 too, just some extra options are
> needed for ia32, it should
Hi!
The testcase uses -m32 in dg-options, something we try hard not to do,
if something should be tested only for -m32, it is { target ia32 } test,
if it can be tested for -m64/-mx32 too, just some extra options are
needed for ia32, it should have dg-additional-options with ia32 target.
Furthermo
This test has been failing since r15-1619-g3b9b8d6cfdf593, which made
IRA prefer a call-clobbered register over a call-preserved register
for mem1 (the second load). In this particular case, that just
forces the variable p3 to be allocated to a call-preserved register
instead, leading to an extra
gcc.target/aarch64/sve/var_stride_2.c started failing after
r15-268-g9dbff9c05520, but the change was an improvement:
@@ -36,13 +36,11 @@
b.any .L9
ret
.L17:
- ubfiz x5, x3, 10, 16
- ubfiz x4, x2, 10, 16
- add x5, x1, x5
- add x4, x0, x4
-
在 2025/2/19 下午3:27, Xi Ruoyao 写道:
On Wed, 2025-02-05 at 08:57 +0800, Xi Ruoyao wrote:
Like RISC-V, on LoongArch we don't really support %cN for SYMBOL_REFs
even with -fno-pic.
gcc/testsuite/ChangeLog:
* c-c++-common/toplevel-asm-1.c: Use %cc3 %cc4 instead of %c3
%c4 on LoongA
On Wed, 2025-02-05 at 08:57 +0800, Xi Ruoyao wrote:
> Like RISC-V, on LoongArch we don't really support %cN for SYMBOL_REFs
> even with -fno-pic.
>
> gcc/testsuite/ChangeLog:
>
> * c-c++-common/toplevel-asm-1.c: Use %cc3 %cc4 instead of %c3
> %c4 on LoongArch.
> ---
>
> Ok for trunk?
On 2/14/25 4:21 AM, Robin Dapp wrote:
Hi,
my last fix wasn't sufficient. This patch just scans for the scalar
insns now.
Going to commit as obvious if the CI is happy.
Regards
Robin
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/reduc/reduc-8.c: Scan for add.
On 2/14/25 11:48 AM, Matthew Malcomson wrote:
On 2/14/25 07:56, Jason Merrill wrote:
External email: Use caution opening links or attachments
On 2/13/25 11:38 AM, Matthew Malcomson wrote:
On 2/12/25 23:30, Jason Merrill wrote:
Shall I make that change?
Please.
Jason
Much simpler pa
Hi,
my last fix wasn't sufficient. This patch just scans for the scalar
insns now.
Going to commit as obvious if the CI is happy.
Regards
Robin
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/reduc/reduc-8.c: Scan for add.
* gcc.target/riscv/rvv/autovec/reduc/reduc-9
34bc44d3e491b5db998e4288cba5ae9006a44879 Mon Sep 17 00:00:00 2001
From: Matthew Malcomson
Date: Mon, 10 Feb 2025 16:24:20 +
Subject: [PATCH] gcc: testsuite: Fix builtin-speculation-overloads[14].C
testism
When making warnings trigger a failure in template substitution I
could not find any way to
On 2/13/25 11:38 AM, Matthew Malcomson wrote:
On 2/12/25 23:30, Jason Merrill wrote:
In the new `check_known_compiler_messages_nocache` procedure I use some
Why is it not enough to look for the message with "[regexp" like
check_alias_available does?
The goal was that I wanted to be able to
On 2/12/25 23:30, Jason Merrill wrote:
External email: Use caution opening links or attachments
In the new `check_known_compiler_messages_nocache` procedure I use some
Why is it not enough to look for the message with "[regexp" like
check_alias_available does?
Jason
The goal was that I
The existing usage comment for check-function-bodies is presumably a
typo, as it doesn't match existing uses. Fix it.
Tested on x86_64-linux-gnu. I'm going to install it as obvious if there
are no objections in the next 24 hours.
for gcc/testsuite/ChangeLog
* lib/scanasm.exp (check
On 2/12/25 5:23 PM, mmalcom...@nvidia.com wrote:
From: Matthew Malcomson
I've posted the patch on the relevant Bugzilla, but also sending to
mailing list. If should have only done one please do mention.
Having it in both places is fine, or send to the mailing list and put a
link to the list
From: Matthew Malcomson
I've posted the patch on the relevant Bugzilla, but also sending to
mailing list. If should have only done one please do mention.
- 8< --- >8
When making warnings trigger a failure in template substitution I
could not find any way
On 2/7/25 6:15 AM, Nathaniel Shead wrote:
Tested on x86_64-pc-linux-gnu, OK for trunk?
OK.
-- >8 --
This testcase wasn't running, because adl-5_a had the wrong extension.
adl-5_d should have been reporting an error because 'frob' is only
visible from within the 'hidden' module but this was m
Tested on x86_64-pc-linux-gnu, OK for trunk?
-- >8 --
This testcase wasn't running, because adl-5_a had the wrong extension.
adl-5_d should have been reporting an error because 'frob' is only
visible from within the 'hidden' module but this was missed.
gcc/testsuite/ChangeLog:
* g++.dg/
Like RISC-V, on LoongArch we don't really support %cN for SYMBOL_REFs
even with -fno-pic.
gcc/testsuite/ChangeLog:
* c-c++-common/toplevel-asm-1.c: Use %cc3 %cc4 instead of %c3
%c4 on LoongArch.
---
Ok for trunk?
gcc/testsuite/c-c++-common/toplevel-asm-1.c | 2 +-
1 file change
From: Matthew Fortune
Ensure micromips test does not get confused about library support.
Ensure insn-casesi.c and insn-tablejump.c can be executed.
Move the micromips/mips16 selection into the file as per function
attributes so that there is no requirement on having a full
micromips or mips16 ru
From: abennett
Cherry-picked 4420f953c31daf1991011d306a56ab74c39b44ee
and 83c13cb19cb1e87a25326024943b95930a17e86b
from https://github.com/MIPS/gcc
Signed-off-by: Andrew Bennett
Signed-off-by: Matthew Fortune
Signed-off-by: Faraz Shahbazker
Signed-off-by: Aleksandar Rakic
---
gcc/testsuite/
Hi,
in both tests we expect a VEC_SHL_INSERT expression but we now add the
initial value at the end. Just remove that scan check.
Will commit as obvious after the CI run.
Regards
Robin
---
gcc/testsuite/gcc.target/riscv/rvv/autovec/reduc/reduc-8.c | 1 -
gcc/testsuite/gcc.target/riscv/rvv/a
Hi,
the test fails with _zvfh because we vectorize more. Just adjust the
test expectations. I regtested this a while ago on rv64gcv_zvl512b.
Will commit as obvious if the CI is happy.
Regards
Robin
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/gather-scatter/gather_load_64-
On Mon, Jan 20, 2025 at 08:10:31PM +, Simon Martin wrote:
> Successfully tested on x86_64-pc-linux-gnu with "make check-c++-all".
> gcc/testsuite/ChangeLog:
>
> * g++.dg/cpp1z/constexpr-asm-5.C: Pass -fno-implicit-constexpr.
LGTM.
Jakub
that and I can merge it later today if that works
> for
> you.
Here’s the updated patch, successfully tested on x86_64-pc-linux-gnu
with “make check-c++-all”. OK?
Thanks, Simon
From eccf73af1b3555be3e02ea2f3b1ca0be32c81cc1 Mon Sep 17 00:00:00 2001
From: Simon Martin
Date: Mon, 20 Jan 2025 20
Hi Jakub,
On 20 Jan 2025, at 10:15, Jakub Jelinek wrote:
> On Mon, Jan 20, 2025 at 08:52:17AM +, Simon Martin wrote:
>> On 12 Jan 2025, at 12:10, Simon Martin wrote:
>>
>>> While testing an unrelated C++ patch with "make check-c++-all", I
>>> noticed that r15-6760-g38a13ea4117b96 added a test
On Mon, Jan 20, 2025 at 08:52:17AM +, Simon Martin wrote:
> On 12 Jan 2025, at 12:10, Simon Martin wrote:
>
> > While testing an unrelated C++ patch with "make check-c++-all", I
> > noticed that r15-6760-g38a13ea4117b96 added a test case that fails
> > with
> > -fimplicit-constexpr.
> >
> > T
Hi,
On 12 Jan 2025, at 12:10, Simon Martin wrote:
> While testing an unrelated C++ patch with "make check-c++-all", I
> noticed that r15-6760-g38a13ea4117b96 added a test case that fails
> with
> -fimplicit-constexpr.
>
> The problem is that this test unconditionally expects an error stating
> t
While testing an unrelated C++ patch with "make check-c++-all", I
noticed that r15-6760-g38a13ea4117b96 added a test case that fails with
-fimplicit-constexpr.
The problem is that this test unconditionally expects an error stating
that a non-constexpr function is called, but that function is
auto-
Tested on x86_64-pc-linux-gnu, committing as obvious.
-- >8 --
GCC14 doesn't have the new spelling '-fmodules' for enabling modules;
use the old '-fmodules-ts' spelling instead.
gcc/testsuite/ChangeLog:
* g++.dg/modules/pr114630_a.C: Use -fmodules-ts instead of
-fmodules in test
1 - 100 of 1190 matches
Mail list logo
