On Wed, Jan 8, 2025 at 7:51 AM Haochen Jiang wrote:
>
> Hi all,
>
> In ISE, The model number for Diamond Rapids is 13_01H.
> Remove 0x00 since it is unused.
>
> Ref: https://cdrdv2.intel.com/v1/dl/getContent/671368
>
> Ok for trunk?
OK as a trivial patch.
Thanks,
Uros.
>
> Thx,
> Haochen
>
> gc
On Tue, 7 Jan 2025, Jakub Jelinek wrote:
> Hi!
>
> DWARF has voted in yesterday https://dwarfstd.org/issues/241209.1.html ,
> which is basically just a guarantee that the DWARF 6 draft
> DW_AT_language_{name,version} attribute codes and content of
> https://dwarfstd.org/languages-v6.html can be u
On Mon, Dec 2, 2024 at 9:05 PM Richard Biener wrote:
>
> The PR uncovers unchecked constraints on the ability to code-generate
> with SLP but also latent issues with regard to stmt order checking
> since loop (early-break) and BB (for quite some time) vectorization
> are no longer constraint to si
Hi all,
In ISE, The model number for Diamond Rapids is 13_01H.
Remove 0x00 since it is unused.
Ref: https://cdrdv2.intel.com/v1/dl/getContent/671368
Ok for trunk?
Thx,
Haochen
gcc/ChangeLog:
* common/config/i386/cpuinfo.h (get_intel_cpu): Remove 0x00.
---
gcc/common/config/i386/cpuin
> From: Liu, Hongtao
> Sent: Friday, January 3, 2025 6:33 PM
>
> > From: Jiang, Haochen
> > Sent: Friday, January 3, 2025 4:55 PM
> >
> > Hi all,
> >
> > The mnemonics for TCVTROWPS2PBF16[H,L] has been changed to
> > TCVTROWPS2BF16[H,L] in ISE056. There will be also some more BF16
> > mnemonics
Jeff Law 于2025年1月8日周三 07:06写道：
>
>
>
> On 1/1/25 6:42 PM, YunQiang Su wrote:
> > Matthias Klose 于2025年1月1日周三 22:37写道：
> >>
> >> in https://gcc.gnu.org/pipermail/gcc-patches/2024-January/641619.html
> >>
> >> there are two typos in the patch, compared to the local Debian patch,
> >>
> >
> > Oh, so
> LGTM, but please note there are a whole lot of CMOVE issues on x86,
> collected in [1] meta-bug, especially [2].
>
> [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85559
> [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56309
Thanks for noting this, I've verified my patch have no impact for t
On Tue, 7 Jan 2025, Eric Botcazou wrote:
> > The fix feels hackish and I wonder how other frontends handle this, but
> > overall thank you for taking care of this peculiarity.
>
> You're welcome. The main Makefile does the same for xgcc -> gcc-cross and,
> as this example shows, every change is
On 1/7/25 10:58 AM, Marek Polacek wrote:
Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
OK.
-- >8 --
Here, cxx_eval_outermost_expression gets a sequence of initialization
statements:
D.2912.t = TARGET_EXPR <...>;
TARGET_EXPR ;
D.2922 = 0;
the last of which wasn't conv
On Tue, 2025-01-07 at 15:08 -0500, Marek Polacek wrote:
> On Thu, Dec 19, 2024 at 06:40:19PM -0500, David Malcolm wrote:
> > Consider this case of a bad call to a callback function (perhaps
> > due to C23 changing the meaning of () in function decls):
> >
> > struct p {
> > int (*bar)();
>
> OK for the trunk. Sorry for the delay.
Never mind, thanks Jeff and Happ New Year, 😉!
Pan
-Original Message-
From: Jeff Law
Sent: Tuesday, January 7, 2025 9:32 PM
To: Li, Pan2 ; gcc-patches@gcc.gnu.org
Cc: richard.guent...@gmail.com; tamar.christ...@arm.com; juzhe.zh...@rivai.ai;
ki
On Tue, Jan 07, 2025 at 08:36:29PM +0100, Jakub Jelinek wrote:
> Hi!
>
> The following patch fixes ICEs when the new inline asm syntax
> to use C++26 static_assert-like constant expressions in place
> of string literals is used in templates.
> As finish_asm_stmt doesn't do any checking for
> proce
On 1/1/25 6:42 PM, YunQiang Su wrote:
Matthias Klose 于2025年1月1日周三 22:37写道：
in https://gcc.gnu.org/pipermail/gcc-patches/2024-January/641619.html
there are two typos in the patch, compared to the local Debian patch,
Oh, sorry it is not duplicated.
- the subst macro has an additional
This improves codegen for x264 sum of absolute difference routines.
The insn count is same, but we avoid double widening ops and ensuing
whole register moves.
Also for more general applicability, we chose to implement abs diff
vs. the sum of abs diff variant.
Suggested-by: Robin Dapp
Co-authored
On 1/1/25 2:16 PM, Keith Packard wrote:
I thought I had sent all of my m68k soft float fixes along last year,
but it looks like I managed to leave some out. I had been building
my toolchain from a private repo (oops), which masked my mistake. We're
fixing that by automatically building toolcha
On 1/2/25 12:13 AM, Tsung Chun Lin wrote:
Don't use the QI vector if its size is equal to UNITS_PER_WORD for
better code generation.
Before patch:
vsetivlizero,4,e8,mf4,ta,ma
vmv.v.i v1,0
addia4,sp,12
vse8.v v1,0(a4)
After patch:
sw zero,12(sp)
I've pushed this patch to
On 1/7/25 11:18 AM, Richard Sandiford wrote:
Jeff Law writes:
On 1/7/25 2:09 AM, Tsung Chun Lin wrote:
Hi,
Could someone help merge this patch if there are no further concerns?
It'll get addressed. Many contributors have been on holiday and are
still catching up.
FWIW, I'm happy to pus
Tamar's recent improvement to improve affine unsigned folding for
exchange2 twiddle code generation for a couple tests in the RVV
testsuite just enough to cause testsuite failures.
I've looked at both tests before/after Tamar's change and the code is
clearly better -- essentially tighter vecto
On 1/7/25 10:25, Patrick O'Neill wrote:
On 1/7/25 10:18, Richard Sandiford wrote:
Jeff Law writes:
On 1/7/25 2:09 AM, Tsung Chun Lin wrote:
Hi,
Could someone help merge this patch if there are no further concerns?
It'll get addressed. Many contributors have been on holiday and are
still
Ok for trunk and releases/gcc-14?
--
Since armv8-m.base uses thumb1 that does not suport sigcall/tailcall,
a pattern is needed that uses PUSH/BL/POP sequence instead of a single
B instruction to reuse an already existing function in the compile unit.
gcc/testsuite/ChangeLog:
* gcc.targe
On Thu, Dec 19, 2024 at 06:40:19PM -0500, David Malcolm wrote:
> Consider this case of a bad call to a callback function (perhaps
> due to C23 changing the meaning of () in function decls):
>
> struct p {
> int (*bar)();
> };
>
> void baz() {
> struct p q;
> q.bar(1);
> }
>
> Bef
On Tue, Jan 07, 2025 at 07:55:45AM -0800, Palmer Dabbelt wrote:
> On Mon, 09 Dec 2024 08:13:22 PST (-0800), dimi...@dinux.eu wrote:
> > Many test cases implicitly require some form of I ABI variant for
> > RISC-V to be the default. Hence they fail when ILP32E is configured as
> > the default ABI f
Hi!
With the following patch I actually get a simple namespace scope structured
binding working with modules.
The core_vals change ensure we actually save/restore DECL_VALUE_EXPR even
for namespace scope vars, the get_merge_kind is based on the assumption
that structured bindings are always uniqu
Hi!
The following patch fixes ICEs when the new inline asm syntax
to use C++26 static_assert-like constant expressions in place
of string literals is used in templates.
As finish_asm_stmt doesn't do any checking for
processing_template_decl, this patch also just defers handling
those strings in te
On 1/7/25 8:35 AM, Andreas Schwab wrote:
* lib/target-supports.exp
(check_effective_target_sync_char_short): Enable for riscv*-*-*.
I went ahead and pushed this as well.
Thanks again,
jeff
On Mon, Jan 06, 2025 at 07:52:23AM -0700, Jeff Law wrote:
>
>
> On 1/4/25 11:01 AM, Dimitar Dimitrov wrote:
> > Add new effective target check for either ILP32E or ILP64E ABI variants.
> >
> > Initial implementation only checks for RV32E or RV64E ISA, which in turn
> > implies that ILP32E/ILP64E
On 1/7/25 8:37 AM, Andreas Schwab wrote:
gcc:
PR target/118137
* config/riscv/sync.md ("lrsc_atomic_exchange"): Apply mask
to shifted value.
gcc/testsuite:
PR target/118137
* gcc.dg/atomic/pr118137.c: New.
Thanks. I went ahead and pushed this to the t
Hi!
DWARF has voted in yesterday https://dwarfstd.org/issues/241209.1.html ,
which is basically just a guarantee that the DWARF 6 draft
DW_AT_language_{name,version} attribute codes and content of
https://dwarfstd.org/languages-v6.html can be used as an extension
in DWARF 5 and won't be changed.
This is a trivial bug that showed up after Mark W's recent patch to not
apply the size limit on jump tables.
The ft32 port has limited immediate ranges on comparisons and the casesi
expander didn't honor those. It'd blindly pass along an out of range
constant.
This patch adds the trivial ad
On 1/7/25 8:35 AM, Andreas Schwab wrote:
* lib/target-supports.exp
(check_effective_target_sync_char_short): Enable for riscv*-*-*.
OK
jeff
On 1/7/25 11:17 AM, Richard Sandiford wrote:
Andrew Carlotti writes:
I forgot to include this in the earlier patch; is this ok for master (once the
pass is merged, of course)?
gcc/ChangeLog:
* doc/passes.texi: Document hardreg PRE pass.
diff --git a/gcc/doc/passes.texi b/gcc/doc/
From: Jim Tsung-Chun Lin
Re-sending this via git send-email to avoid the application/octet-stream
attachement type that prevents Patchworks/CI from finding the patch.
---
Don't use the QI vector if its size is equal to UNITS_PER_WORD for
better code generation.
Before patch:
vsetivliz
On 1/7/25 10:18, Richard Sandiford wrote:
Jeff Law writes:
On 1/7/25 2:09 AM, Tsung Chun Lin wrote:
Hi,
Could someone help merge this patch if there are no further concerns?
It'll get addressed. Many contributors have been on holiday and are
still catching up.
FWIW, I'm happy to push the
Jeff Law writes:
> On 1/7/25 2:09 AM, Tsung Chun Lin wrote:
>> Hi,
>>
>> Could someone help merge this patch if there are no further concerns?
> It'll get addressed. Many contributors have been on holiday and are
> still catching up.
FWIW, I'm happy to push the patch, but wasn't sure how to ch
Andrew Carlotti writes:
> I forgot to include this in the earlier patch; is this ok for master (once the
> pass is merged, of course)?
>
> gcc/ChangeLog:
>
> * doc/passes.texi: Document hardreg PRE pass.
>
>
> diff --git a/gcc/doc/passes.texi b/gcc/doc/passes.texi
> index
> 639f6b325c8be47b
> >> i.e. we use separate address arithmetic and avoid UMOVs. Counting
> >> two loads and one store for each element of the scatter store seems
> >> like overkill for that.
> >
> > Hmm agreed..
> >
> > How about for stores we increase the load counts by count / 2?
> >
> > This would account for th
Andrew Carlotti writes:
> On Mon, Nov 25, 2024 at 11:26:39PM +, Richard Sandiford wrote:
>> Sorry for the slow review.
>>
>> Andrew Carlotti writes:
>> > These new flags (+fcma, +jscvt, +rcpc2, +jscvt, +frintts, +wfxt and +xs)
>> > were only recently added to the assembler. To improve compa
aarch64_function_ok_for_sibcall required the caller and callee
to use the same PCS variant. However, it should be enough for the
callee to preserve at least as much register state as the caller;
preserving more state is fine.
ARM_PCS_AAPCS64, ARM_PCS_SIMD, and ARM_PCS_SVE agree on what
GPRs shoul
On Tue, Jan 07, 2025 at 03:28:31PM +0100, Thomas Koenig wrote:
> Hello world,
>
> the attached patch does what it says in the ChangeLog entry.
>
> Tested with "make dvi" and "make pdf".
>
> OK for trunk?
>
OK.
--
Steve
> The fix feels hackish and I wonder how other frontends handle this, but
> overall thank you for taking care of this peculiarity.
You're welcome. The main Makefile does the same for xgcc -> gcc-cross and,
as this example shows, every change is this area is almost guaranteed to break
something,
I forgot to include this in the earlier patch; is this ok for master (once the
pass is merged, of course)?
gcc/ChangeLog:
* doc/passes.texi: Document hardreg PRE pass.
diff --git a/gcc/doc/passes.texi b/gcc/doc/passes.texi
index
639f6b325c8be47bffd64269340c4dd8ea0f321c..5c2a174a7495404
On Thu, 2024-12-19 at 18:40 -0500, David Malcolm wrote:
Jason: are the C++ changes OK? Patch can also be seen at:
https://gcc.gnu.org/pipermail/gcc-patches/2024-December/672076.html
Joseph approved the C part of this in
https://gcc.gnu.org/pipermail/gcc-patches/2025-January/672473.html
Thanks
D
Christophe Lyon writes:
> A recent commit mistakenly changed the field name for tuples from
> 'val' to '__val', but unlike SVE this name is mandated by ACLE.
>
> The patch simply switches back the name to 'val'.
>
> PR target/118332
>
> gcc/ChangeLog:
>
> * config/arm/arm-mve-builtins.
A recent commit mistakenly changed the field name for tuples from
'val' to '__val', but unlike SVE this name is mandated by ACLE.
The patch simply switches back the name to 'val'.
PR target/118332
gcc/ChangeLog:
* config/arm/arm-mve-builtins.cc (wrap_type_in_struct): Use 'val'
LGTM
Patrick O'Neill 於 2025年1月8日 週三 00:12 寫道：
>
> On 1/7/25 07:37, Andreas Schwab wrote:
> > gcc:
> > PR target/118137
> > * config/riscv/sync.md ("lrsc_atomic_exchange"): Apply mask
> > to shifted value.
> >
> > gcc/testsuite:
> > PR target/118137
> > * gcc.dg/atom
On 1/7/25 07:37, Andreas Schwab wrote:
gcc:
PR target/118137
* config/riscv/sync.md ("lrsc_atomic_exchange"): Apply mask
to shifted value.
gcc/testsuite:
PR target/118137
* gcc.dg/atomic/pr118137.c: New.
---
Thanks for fixing this - I can't give approva
On Mon, 6 Jan 2025, Eric Botcazou wrote:
> This is a regression introduced by
> https://gcc.gnu.org/pipermail/gcc-cvs/2024-July/405522.html
> in the form of a spurious relinking of the gnatbind executable for the
> install
> target of cross Ada compilers.
The fix feels hackish and I wonder h
Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
-- >8 --
Here, cxx_eval_outermost_expression gets a sequence of initialization
statements:
D.2912.t = TARGET_EXPR <...>;
TARGET_EXPR ;
D.2922 = 0;
the last of which wasn't converted to void and so we, since r15-6369,
do not take
On Mon, 09 Dec 2024 08:13:22 PST (-0800), dimi...@dinux.eu wrote:
Many test cases implicitly require some form of I ABI variant for
RISC-V to be the default. Hence they fail when ILP32E is configured as
the default ABI for the toolchain. Example error:
spawn ... -march=rv32gc_zbb ...
Now committed as r15-6659-gd3ccd89fa0d34d – with an additional typo fix:
stipe → stripe (OpenMP 6.0 loop transformation directive).
Tobias
commit d3ccd89fa0d34d44226af47fe82c27ba7833fe65
Author: Tobias Burnus
Date: Tue Jan 7 16:43:30 2025 +0100
libgomp.texi: Minor update to omp_get_num_d
gcc:
PR target/118137
* config/riscv/sync.md ("lrsc_atomic_exchange"): Apply mask
to shifted value.
gcc/testsuite:
PR target/118137
* gcc.dg/atomic/pr118137.c: New.
---
gcc/config/riscv/sync.md | 1 +
gcc/testsuite/gcc.dg/atomic/pr118137.c |
* lib/target-supports.exp
(check_effective_target_sync_char_short): Enable for riscv*-*-*.
---
gcc/testsuite/lib/target-supports.exp | 1 +
1 file changed, 1 insertion(+)
diff --git a/gcc/testsuite/lib/target-supports.exp
b/gcc/testsuite/lib/target-supports.exp
index 5ce7b7976f9.
On Sat, 4 Jan 2025 at 20:06, Nicolas Werner wrote:
>
> std::to_underlying was missing from the std module introduced in
> 7db55c0ba1baaf0e323ef7f9ef8c9cda077d40e9. This patch adds the missing
> export for this utility.
>
> There might be more exports missing, but this is the one I found when
> try
On Tue, Jan 07, 2025 at 11:20:11PM +0800, Gerald Pfeifer wrote:
> On Tue, 7 Jan 2025, Simon Martin wrote:
> > Noticed while trying to understand when I can expect the GCC 15 branch
> > to be created: the GCC 15 release criteria page still mentions GCC 14.
> >
> > I'll push this as obvious.
>
> Th
On Tue, 7 Jan 2025, Gerald Pfeifer wrote:
>> Are such pages created via a script? If so I am happy to fix it as well.
> Unless our release managers (Jakub on this case) have been taken over by
> ChatGPT/Gemini/you-name-it I believe this is manual work following
> https://gcc.gnu.org/releasing.h
On Tue, 7 Jan 2025, Simon Martin wrote:
> Noticed while trying to understand when I can expect the GCC 15 branch
> to be created: the GCC 15 release criteria page still mentions GCC 14.
>
> I'll push this as obvious.
Thank you, Simon!
> Are such pages created via a script? If so I am happy to fi
Hi,
On 11 Dec 2024, at 22:27, Simon Martin wrote:
> Hi,
>
> On 29 Nov 2024, at 15:33, Simon Martin wrote:
>
>> We currently ICE upon the following code, that is valid under
>> -Wno-pointer-arith:
>>
>> === cut here ===
>> int main() {
>> decltype( [](auto) { return sizeof(void); } ) x;
>> ret
Hi,
On 13 Dec 2024, at 13:50, Simon Martin wrote:
> Hi Marek,
>
> On 13 Dec 2024, at 0:44, Marek Polacek wrote:
>
>> On Thu, Dec 12, 2024 at 07:07:38PM +, Simon Martin wrote:
>>> We currently ICE upon the following valid (under -Wno-vla) code
>>>
>>> === cut here ===
>>> void f(int c) {
>>>
Hi,
On 11 Nov 2024, at 20:36, Simon Martin wrote:
> Hi,
>
> On 30 Oct 2024, at 11:44, Simon Martin wrote:
>
>> Friendly ping.
> Friendly ping.
Ping. Thanks!
Simon
>>
>> On 16 Oct 2024, at 17:43, Simon Martin wrote:
>>
>>> Hi Jason,
>>>
>>> On 12 Oct 2024, at 4:51, Jason Merrill wrote:
>>>
O
Hi,
On 11 Nov 2024, at 20:35, Simon Martin wrote:
> Hi,
>
> On 30 Oct 2024, at 11:46, Simon Martin wrote:
>
>> On 19 Oct 2024, at 11:09, Simon Martin wrote:
>>
>>> We currently ICE in checking mode with cxx_dialect < 17 on the
>>> following
>>> valid code
>>>
>>> === cut here ===
>>> struct X {
>
On Tue, Jan 07, 2025 at 03:49:26PM +0100, Richard Biener wrote:
> When nonlocal goto lowering creates an artificial label it fails
> to adjust its context.
>
> Bootstrapped on x86_64-unknown-linux-gnu, testing in progress
> (I doubt good test coverage is present for non-local gotos)
>
> OK when t
When nonlocal goto lowering creates an artificial label it fails
to adjust its context.
Bootstrapped on x86_64-unknown-linux-gnu, testing in progress
(I doubt good test coverage is present for non-local gotos)
OK when testing succeeds?
Thanks,
Richard.
PR middle-end/118325
* tre
On Tue, 10 Dec 2024, Jan Hubicka wrote:
> Hi,
> int:
> struct foo
> {
> int a;
> void bar() const;
> ~foo()
> {
> if (a != 42)
> __builtin_abort ();
> }
> };
> __attribute__ ((noinline))
> void test(const struct foo a)
> {
> int b = a.a;
> a.bar();
> if
After a bit of a prod from Hans...
Make the obvious change to these tests to get them passing again on m68k.
Jeff
commit a856b4d97b8d328fdcb169b792ac5456e40f8c00
Author: Jeff Law
Date: Tue Jan 7 07:43:19 2025 -0700
[PR testsuite/118055] Trivial testsuite adjustment for m68k target
On Thu, 2 Jan 2025, 赵洲 wrote:
> Add Reviewer Richard Biener.
>
>
> > -原始邮件-
> > 发件人: "Zhou Zhao"
> > 发送时间:2025-01-02 19:37:07 (星期四)
> > 收件人: gcc-patches@gcc.gnu.org
> > 抄送: xry...@xry111.site, i...@xen0n.name, chengl...@loongson.cn,
> > xucheng...@loongson.cn, zhaoz...@loongson.cn
> >
OpenMP 6 changed that omp_get_initial_device may not only return the
dynamic value of omp_get_num_devices() but also the constant value
omp_get_num_devices (== -1).
For now, GCC returns omp_get_num_devices() but we may want to change
this in the future as '-1' can be solved at compile time; in pa
Hello world,
the attached patch does what it says in the ChangeLog entry.
Tested with "make dvi" and "make pdf".
OK for trunk?
Best regards
Thomas
Document unsigned constants in intrinsic modules.
gcc/fortran/ChangeLog:
* intrinsic.texi (ISO_FORTRAN_ENV): Also
On 1/2/25 1:34 AM, Li Xu wrote:
From: xuli
This patch would like to support .SAT_ADD when IMM=-1.
Form1:
T __attribute__((noinline)) \
sat_s_add_imm_##T##_fmt_1##_##INDEX (T x) \
{\
T sum = (UT)x + (UT)IMM;
On 1/2/25 1:03 AM, Li Xu wrote:
From: xuli
This patch would like to support vector SAT_ADD when one of the op
is singed IMM.
void __attribute__((noinline)) \
vec_sat_s_add_imm_##T##_fmt_1##_##INDEX (T *out, T *op_1, unsigned limit) \
{
When the RTL unroller handles constant iteration loops it bails out
prematurely when heuristics wouldn't apply any unrolling before
checking #pragma unroll.
Bootstrapped and tested on x86_64-unknown-linux-gnu, pushed.
PR rtl-optimization/118298
* loop-unroll.cc (decide_unroll_cons
> Or maybe write a blog post about how to do a new
> GCC frontend (there are multiple such for backends). But I know time
> is scarce.
I made a set of slides a few decades ago on doing that. It's somewhat,
but not fully, out of date and I don't know how to find them, but it
does exist somewhere.
The testcases use -save-temps which doesn't play nice with -flto
and multilib testing resulting in spurious UNRESOLVED like
/usr/lib64/gcc/x86_64-suse-linux/14/../../../../x86_64-suse-linux/bin/ld:
i386:x86-64 architecture of input file `./convert-dfp-2.ltrans0.ltrans.o' is
incompatible with i38
On 1/2/25 10:46 PM, Tsung Chun Lin wrote:
From c05d80e696b226444af26a981d78875a5767bf82 Mon Sep 17 00:00:00 2001
From: Jim Tsung-Chun Lin
Date: Fri, 3 Jan 2025 13:27:40 +0800
Subject: [PATCH] RISC-V: Add missing dg-runtest to run the testcase under
gcc.target/riscv/rvv/
gcc/testsuite/Chang
On 1/6/25 7:47 PM, Li, Pan2 wrote:
Kindly ping for the series>
Pan
-Original Message-
From: Li, Pan2
Sent: Monday, December 23, 2024 3:09 PM
To: gcc-patches@gcc.gnu.org
Cc: richard.guent...@gmail.com; tamar.christ...@arm.com; juzhe.zh...@rivai.ai;
kito.ch...@gmail.com; jeffreya...@gm
On Mon, 23 Dec 2024, Robert Dubner wrote:
> Richard, a bunch of things you address are in my bailwick.
>
> When Jim and I set out to create a COBOL front end, I knew *NOTHING*
> about, well, anything vis-à-vis GCC. I barely knew how it worked. Some
> things I had to figure out even before I kne
When analyzing 525 on LoongArch architecture, it was found that the
for loop of hotspot function x264_pixel_satd_8x4 could not be quantized
256-bit due to the cost of vec_construct setting. After re-adjusting
vec_construct, the performance of 525 program was improved by 16.57%.
It was found that
Do not mention an explicit version.
gcc/ada/ChangeLog:
* libgnat/a-calcon.ads: Adjust.
* libgnat/a-calend.ads: Adjust.
Tested on x86_64-pc-linux-gnu, committed on master.
---
gcc/ada/libgnat/a-calcon.ads | 16
gcc/ada/libgnat/a-calend.ads | 14 ++
2
From: Javier Miranda
According to RM 13.14(8/4), a static expression in an aspect specification
does not cause freezing; however, the frontend performs many calls to
Preanalyze_Spec_Expression made during the analysis of aspects. This
patch, suggested by Eric Botcazou, takes care of this addition
From: Piotr Trojanek
A code cleanup in routine intended to be used from DGB, suggested by running
GNATcheck rule Boolean_Negations. However, this code can be tuned to protect
against more illegal uses.
gcc/ada/ChangeLog:
* exp_disp.adb (Write_DT): Add guards that prevent crashes on ille
From: Piotr Trojanek
Code cleanup suggested by GNATcheck rule Constant_Overlays.
gcc/ada/ChangeLog:
* repinfo-input.adb (Decode_Name, Read_Name_With_Prefix): Use constant
overlay with pragma Import.
Tested on x86_64-pc-linux-gnu, committed on master.
---
gcc/ada/repinfo-input
From: Eric Botcazou
Assignment statements marked with the No_Ctrl_Actions or No_Finalize_Actions
flag are initialization statements and, therefore, no temporaries are needed
to hold the value of the right-hand side for them.
gcc/ada/ChangeLog:
* gcc-interface/trans.cc (Call_to_gnu): Alw
On Tue, Jan 07, 2025 at 02:07:58PM +0100, Jakub Jelinek wrote:
> Stage1:
>
> https://gcc.gnu.org/pipermail/gcc-patches/2024-September/662379.html
> https://gcc.gnu.org/pipermail/gcc-patches/2024-September/662380.html
> https://gcc.gnu.org/pipermail/gcc-patches/2024-September/662381.html
> https://
From: Piotr Trojanek
Code cleanup; semantics is unaffected.
gcc/ada/ChangeLog:
* diagnostics-pretty_emitter.adb (Get_Last_Line_Char): Fix whitespace.
* sem_aggr.adb (Resolve_Array_Aggregate): Fix style.
Tested on x86_64-pc-linux-gnu, committed on master.
---
gcc/ada/diagnosti
On 1/7/25 2:09 AM, Tsung Chun Lin wrote:
Hi,
Could someone help merge this patch if there are no further concerns?
It'll get addressed. Many contributors have been on holiday and are
still catching up.
jeff
From: Piotr Trojanek
Flag Address_Warning_Posted was only read and never written, so it can be
safely removed.
gcc/ada/ChangeLog:
* gen_il-fields.ads (Opt_Field_Enum): Remove flag.
* gen_il-gen-gen_nodes.adb (N_Attribute_Definition_Clause): Remove
field.
* sem_ch
From: Ronan Desplanques
This patch fixes two problems with how abort was deferred in finally
parts. First, calls to runtime subprograms are now omitted when
aborting is disallowed by active restrictions. Second, Abort_Undefer is
now correctly called when the finally part propagates an exception.
From: Piotr Trojanek
Code cleanup related to work on expression functions for GNATprove
(which require accessibility checks even when they are not expanded
and thus have no explicit return statements).
gcc/ada/ChangeLog:
* accessibility.adb (First_Selector): Remove redundant and locally
Hi!
I'd like to ping 10 C++ patches:
https://gcc.gnu.org/pipermail/gcc-patches/2024-December/672040.html
P1 - Fix ICEs with large initializer lists or ones including #embed [PR118124]
https://gcc.gnu.org/pipermail/gcc-patches/2024-December/672041.html
P1 - Fix up maybe_init_list_as_array for
From: Ronan Desplanques
This patch adds a new reserved word, "finally", and accompanying new
syntax that's similar to the Java equivalent.
gcc/ada/ChangeLog:
* atree.adb (Parent_Or_List_Containing): New function.
* atree.ads (Parent_Or_List_Containing): Likewise.
* gen_i
From: Alexandre Oliva
Having moved __gnat_convert_caught_object to g-cstyin.o, we can drop
other g-cpp* units that are now needed by programs that actually use
their APIs to get more information about C++ exceptions and type_info
objects.
gcc/ada/ChangeLog:
* gcc-interface/Make-lang.in
From: Piotr Trojanek
Functions with aspect Side_Effects should not reference attribute Result in
consequences of their aspect Exceptional_Cases.
gcc/ada/ChangeLog:
* sem_prag.adb (Analyze_Exceptional_Cases_In_Decl_Part): Reject
references to attribute Result.
Tested on x86_64-p
From: Piotr Trojanek
Code cleanup; behavior is unaffected. Flag Is_Inherited_Pragma is only set in
GNAT, but is not actually used, neither by the compiler nor by any backend.
gcc/ada/ChangeLog:
* contracts.adb (Inherit_Pragma): Don't set flag Is_Inherited_Pragma.
* gen_il-fields
From: Eric Botcazou
An exception is now raised during bootstrap and this causes compatibility
issues with older compilers.
gcc/ada/ChangeLog:
* exp_aggr.adb (Packed_Array_Aggregate_Handled): Remove declaration
and handler for Not_Handled local exception. Check the return value
From: Alexandre Oliva
Adding -msmp to linker options in system-vxworks-ppc-rtp-smp.ads
obviated vxworks-smp-ppc-link.spec. Drop it.
gcc/ada/ChangeLog:
* libgnat/system-vxworks-ppc-rtp-smp.ads: Drop
--specs=vxworks-ppc-link.spec from Linker_Options.
* vxworks-smp-ppc-lin
From: Piotr Trojanek
Previously checks for consequence expressions of Exceptional_Cases aspects were
done in GNATprove backend. However, we can do them in the frontend, where they
will apply to all subprograms, regardless of the SPARK_Mode aspect.
gcc/ada/ChangeLog:
* sem_prag.adb (Anal
From: Piotr Trojanek
Code cleanup.
gcc/ada/ChangeLog:
* sem_prag.adb (Analyze_Attribute): Replace runtime conversion
with existing constant.
Tested on x86_64-pc-linux-gnu, committed on master.
---
gcc/ada/sem_prag.adb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
dif
From: Eric Botcazou
The problem is that we analyze references to an object before the actual
subtype of the object is established, thus creating a type mismatch that
is flagged by the code generator.
gcc/ada/ChangeLog:
* exp_ch7.ads (Store_After_Actions_In_Scope_Without_Analysis): New
From: Eric Botcazou
There is no need to keep multiplying the result once it saturates to +Inf.
gcc/ada/ChangeLog:
* libgnat/s-powflt.ads (Maxpow_Exact): Minor comment fix.
* libgnat/s-powlfl.ads (Maxpow_Exact): Likewise.
* libgnat/s-powllf.ads (Maxpow_Exact): Likewise.
From: Piotr Trojanek
Use existing machinery for internal attributes to handle attributes
related to Ada 2012 iterators. All these attributes exist exclusively
as a mean to delay processing.
Code cleanup. The only change in behavior is the wording of error
emitted when one of the internal attribu
On Wed, Dec 18, 2024 at 12:15:15PM +0100, Jakub Jelinek wrote:
> On Fri, Dec 06, 2024 at 05:07:40PM +0100, Jakub Jelinek wrote:
> > I'd like to ping the
> > https://gcc.gnu.org/pipermail/gcc-patches/2024-November/668699.html
> > patch.
> >
> > The patches it depended on are already committed and t
1 - 100 of 132 matches
Mail list logo
