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
On Thu, 6 Mar 2025 at 16:09, Patrick Palka wrote:
>
> On Thu, Mar 6, 2025 at 6:28 AM Jonathan Wakely wrote:
> >
> > We need to include in C++23 and later, so that
> > __pair_like_convertible_from can use __pair_like.
> >
> > libstdc++-v3/ChangeLog:
> >
> > * include/bits/ranges_util.h: I
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the French team of translators. The file is available at:
https://translationproject.org/latest/gcc/fr.po
(This file, 'gcc-15-b20250216.fr.po', h
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the Swedish team of translators. The file is available at:
https://translationproject.org/latest/gcc/sv.po
(This file, 'gcc-15-b20250216.sv.po',
Hi Mikael,
_symbol *asym = a->expr->symtree->n.sym;
You may consider calling gfc_commit_symbol(s) instead at the end of the
function body. It might avoid leaking the old_symbol field in case the
function is called more than once or the symbol is already existing (not
completely clear wheth
Le 09/03/2025 à 17:40, Thomas Koenig a écrit :
Hi Mikael,
_symbol *asym = a->expr->symtree->n.sym;
You may consider calling gfc_commit_symbol(s) instead at the end of
the function body. It might avoid leaking the old_symbol field in
case the function is called more than once or the symbol
After r12-5300-gf98f373dd822b3, value_replacement would be able to look at the
following cfg structure:
```
[local count: 1014686024]:
if (h_6 != 0)
goto ; [94.50%]
else
goto ; [5.50%]
[local count: 114863530]:
# h_6 = PHI <0(4), 1(5)>
[local count: 1073741824]:
# f_8 = P
The test spuriously failed on pru-unknown-elf due to missing support for
_Float16 type.
Pushed to trunk as obvious.
PR target/119133
gcc/testsuite/ChangeLog:
* gcc.dg/torture/pr119133.c: Require effective target float16.
Signed-off-by: Dimitar Dimitrov
---
gcc/testsuite/gcc.d
RDI, RSI, RDX and RCX registers are used to pass arguments in 64-bit
mode. EAX, EDX and ECX registers are used to pass arguments in 32-bit
mode. Add tests to verify that argument registers are spilled properly.
PR target/119171
* gcc.target/i386/pr119171-1.c: New test.
*
> Am 09.03.2025 um 18:11 schrieb Andrew Pinski :
>
> After r12-5300-gf98f373dd822b3, value_replacement would be able to look at
> the
> following cfg structure:
> ```
> [local count: 1014686024]:
> if (h_6 != 0)
>goto ; [94.50%]
> else
>goto ; [5.50%]
>
> [local count: 11486353
On 3/6/25 11:23 AM, Jakub Jelinek wrote:
Hi!
My r15-7822 PR118787 change unfortunately broke build on x86_64-w64-mingw32.
The reduced testcase below shows what is going on.
va_list on this target is char * with extra (non-dependent) attributes
on it.
Before my r15-7822 change, instantiation of s
This is the first of what I expect to be a few patches to improve memory
consumption and performance of ext-dce.
While I haven't been able to reproduce the insane memory usage that
Richi saw, I can certainly see how we might get there. I instrumented
ext-dce to dump the size of liveness sets,
The next step in improving ext-dce is to clean up a minor wart in the
set/clobber handling code.
In that code the safe thing to do is to not process a destination at
all. That will leave bits set in the live bitmaps for objects that may
no longer be live. Of course with extraneous bits set
This patch introduces inline definitions for the __fma and __fmaf
functions in arm_acle.h for AArch64 targets. These definitions rely on
__builtin_fma and __builtin_fmaf to ensure proper inlining and to meet
the ACLE requirements [1].
The patch has been tested locally using a crosstool-NG sysroot
HTML 5 again uses over or .
(I pushed this some 10 days ago.)
Gerald
---
htdocs/gcc-5/changes.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/gcc-5/changes.html b/htdocs/gcc-5/changes.html
index 5035ed3c..6c04a70b 100644
--- a/htdocs/gcc-5/changes.html
+++ b/htd
LLVM folks noticed that GCC was shrink wrapping the call to
vector::push_back.
So I thought it was a good idea to commit a testcase to make sure GCC does not
regress
in this area unknowning.
Note the shrink wrapping started with r15-1619-g3b9b8d6cfdf593.
Note this enables the testcase for x86_64
On Sun, Mar 9, 2025 at 2:54 PM Sam James wrote:
>
> Uros Bizjak writes:
>
> > On Sun, Mar 9, 2025 at 3:05 PM H.J. Lu wrote:
> >>
> >> RDI, RSI, RDX and RCX registers are used to pass arguments in 64-bit
> >> mode. EAX, EDX and ECX registers are used to pass arguments in 32-bit
> >> mode. Add t
On Sun, Mar 9, 2025 at 3:05 PM H.J. Lu wrote:
>
> RDI, RSI, RDX and RCX registers are used to pass arguments in 64-bit
> mode. EAX, EDX and ECX registers are used to pass arguments in 32-bit
> mode. Add tests to verify that argument registers are spilled properly.
>
> PR target/119171
>
Uros Bizjak writes:
> On Sun, Mar 9, 2025 at 3:05 PM H.J. Lu wrote:
>>
>> RDI, RSI, RDX and RCX registers are used to pass arguments in 64-bit
>> mode. EAX, EDX and ECX registers are used to pass arguments in 32-bit
>> mode. Add tests to verify that argument registers are spilled properly.
>>
This patch introduces inline definitions for the __fma and __fmaf
functions in arm_acle.h for arm targets. These definitions rely on
__builtin_fma and __builtin_fmaf to ensure proper inlining and to meet
the ACLE requirements [1].
The patch has been tested locally using a crosstool-NG sysroot for
While working on a local x86 patch, which passed the GCC testsuite, I got
a compiler error:
In function ‘paravirt_read_msr’,
inlined from ‘perf_ibs_handle_irq’ at arch/x86/events/amd/ibs.c:1055:2:
./arch/x86/include/asm/paravirt_types.h:397:17: error: ‘asm’ operand has
impossible constraints
21 matches
Mail list logo