On Fri, Nov 15, 2024 at 04:04:55PM +0800, Hongyu Wang wrote:
> Following the discussion in pr116738, the insn for UNSPEC_IEEE_MAXMIN
> actually matches the behavior of if_then_else, so remove the UNSPEC and
> rewrite related pattern with if_then_else.
I'm not sure if it is necessarily always a win
> On 7 Nov 2024, at 13:47, Richard Biener wrote:
>
> External email: Use caution opening links or attachments
>
>
> On Tue, 5 Nov 2024, Jennifer Schmitz wrote:
>
>> We are working on a patch to improve the codegen for the following test case:
>> uint64x2_t foo (uint64x2_t r) {
>>uint32x4
On Fri, Nov 15, 2024 at 07:45:32AM +, Paul Richard Thomas wrote:
> Hi Jakub,
Honza's catch.
> Good catch! Does it fix any specific PR?
Dunno. I think even without a PR it can be backported after a while.
Jakub
Hi,
Following the discussion in pr116738, the insn for UNSPEC_IEEE_MAXMIN
actually matches the behavior of if_then_else, so remove the UNSPEC and
rewrite related pattern with if_then_else.
Bootstrapped & regtested on x86-64-pc-linux-gnu.
Ok for trunk?
gcc/ChangeLog:
* config/i386/i386-
On Fri, Nov 15, 2024 at 12:04:11AM -0500, Marek Polacek wrote:
> This test FAILs due to the second dg-do compile:
> FAIL: g++.dg/tree-ssa/pr58483.C -std=gnu++98 (test for excess errors)
> and it passes in C++11 as well.
The other tests are valid C++11, so we can run them in C++11 as well
(just th
> So this is really the biggest question in my mind. When we kicked this
> around in the patchwork meeting several weeks ago I got the impression
> Robin had a correctness concern with this code. Robin, do you remember
> what had you worried?
Unfortunately I haven't managed to get back to this
Richard Biener writes:
> The following ensures that peeling a single iteration for gaps is
> sufficient by enforcing niter masking (partial vector use) given
> we cannot (always) statically decide when the vector size isn't known.
> The condition guarding this and thus statically giving a pass in
On 14/11/24 23:09 -0500, Jason Merrill wrote:
On 10/18/24 9:38 AM, Jason Merrill wrote:
This patch is not ready for integration, but I'd like to get feedback on the
approach (and various specific questions below).
An updated version:
From 533c496ae39ba2cf1783136e1da5ae9f0f61d4f7 Mon Sep 17
> On 14 Nov 2024, at 18:40, Wilco Dijkstra wrote:
>
>
> Cleanup the extra tune defines by introducing AARCH64_EXTRA_TUNE_BASE as a
> common base supported by all modern cores. Initially set it to
> AARCH64_EXTRA_TUNE_CHEAP_SHIFT_EXTEND. No change in generated code.
>
> Passes regress & boo
Hi,
This is a v2 which hopefully addresses the feedback for v1 of the 1/5
patch, originally posted here:
https://gcc.gnu.org/pipermail/gcc-patches/2024-October/48.html
As mentioned on IRC, it will need follow-up work to fix up latent
profile issues, but that can be done during stage 3. We wi
On 11/15/24 9:20 AM, Jonathan Wakely wrote:
On 15/11/24 08:53 -0500, Jason Merrill wrote:
On 11/15/24 6:04 AM, Jonathan Wakely wrote:
On 14/11/24 23:09 -0500, Jason Merrill wrote:
Since bits/stdc++.h also intends to include the whole standard
library, I
include it rather than duplicate it.
Hi,
On Tue, Nov 05 2024, Jan Hubicka wrote:
>> Hi,
>>
>> when inlining (during the analysis phase) a call graph edge, we update
>> all pass-through jump functions corresponding to edges going out of
>> the newly inlined function to be relative to the function into which
>> we are inlining or to e
On Fri, Nov 15, 2024 at 10:41 PM Andrew Pinski wrote:
>
> On Fri, Nov 15, 2024 at 1:30 PM Christoph Müllner
> wrote:
> >
> > This extends forwprop by yet another VEC_PERM optimization:
> > It attempts to blend two isomorphic vector sequences by using the
> > redundancy in the lane utilization in
Hi,
On Thu, Nov 07 2024, Aldy Hernandez wrote:
> Jan Hubicka writes:
>
>>> > 2024-11-01 Martin Jambor
>>> >
>>> > * ipa-prop.cc (ipa_compute_jump_functions_for_edge): When creating
>>> > value-range jump functions from pointer type constant zero, do so
>>> > as if it wa
On Sat, 16 Nov 2024, Florian Weimer wrote:
> +@opindex Wdeprecated-non-prototype
> +@opindex Wno-deprecated-non-prototype
> +@item -Wdeprecated-non-prototype @r{(C and Objective-C only)}
> +Warn if a function declarated with an empty parameter list @samp{()} is
> +called with one or more arguments
On Thu, Nov 14, 2024 at 3:55 PM Christoph Müllner
wrote:
>
> On Thu, Nov 14, 2024 at 3:07 PM Richard Biener wrote:
> >
> > On Thu, 14 Nov 2024, Christoph Müllner wrote:
> >
> > > This extends forwprop by yet another VEC_PERM optimization:
> > > It attempts to merge two isomorphic vector sequences
v1-0003-Rename-SEH-functions-for-reuse-in-AArch64.patch
Description: v1-0003-Rename-SEH-functions-for-reuse-in-AArch64.patch
This patch adds stdcall and cdecl attributes, which might be used for
DLL export/import in MinGW.
gcc/ChangeLog:
* config/aarch64/aarch64.cc: Update.
---
gcc/config/aarch64/aarch64.cc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/gcc/config/aarch64/aarch64.cc b/gcc/config/aarch64
This is another recent GCC extension whose use is apparently
difficult to spot in code reviews.
The name of the option is due to Jonathan Wakely. Part of it
could apply to C++ as well (for labels at the end of a compound
statement).
gcc/c-family/
* c-opts.cc (c_common_post_options): Ini
On Fri, Nov 15, 2024 at 9:13 AM Florian Weimer wrote:
>
> This is another recent GCC extension whose use is apparently
> difficult to spot in code reviews.
>
> The name of the option is due to Jonathan Wakely. Part of it
> could apply to C++ as well (for labels at the end of a compound
> statemen
From 4274d1126a1aa60d16dca1cbf7dde1c5ee344bf7 Mon Sep 17 00:00:00 2001
From: Evgeny Karpov
Date: Fri, 15 Nov 2024 13:36:41 +0100
Subject: [PATCH v1 3/4] Rename SEH functions for reuse in AArch64
This patch renames functions related to SEH functionality. These
functions will be reused in the aarch
From 69ce2026b10711b32595d58e23f92f54e6c718c2 Mon Sep 17 00:00:00 2001
From: Evgeny Karpov
Date: Fri, 15 Nov 2024 13:14:18 +0100
Subject: [PATCH v1 4/4] aarch64: Add SEH, stack unwinding and C++ exceptions
This patch reuses the existing SEH, stack unwinding and C++ exceptions
from ix86 and implem
On Tue, Nov 12, 2024 at 10:42:50PM +, Richard Sandiford wrote:
> Sorry for the slow review. I think Jeff's much better placed to comment
> on this than I am, but here's a stab. Mostly it looks really good to me
> FWIW.
>
> Andrew Carlotti writes:
> > This pass is used to optimise assignment
This extends forwprop by yet another VEC_PERM optimization:
It attempts to blend two isomorphic vector sequences by using the
redundancy in the lane utilization in these sequences.
This redundancy in lane utilization comes from the way how specific
scalar statements end up vectorized: two VEC_PERMs
On Fri, Nov 15, 2024 at 1:30 PM Christoph Müllner
wrote:
>
> This extends forwprop by yet another VEC_PERM optimization:
> It attempts to blend two isomorphic vector sequences by using the
> redundancy in the lane utilization in these sequences.
> This redundancy in lane utilization comes from the
On Sat, 16 Nov 2024 at 01:12, Jason Merrill wrote:
>
> Does this seem like an interesting direction?
>
> -- 8< --
>
> A problem with coexistence of module std and the library headers is that
> import and then #include tends to break (PR99000). But even with that
> fixed, it might be useful to be
Change the default language version for C compilation from -std=gnu17
to -std=gnu23. A few tests are updated to remove local definitions of
bool, true and false (where making such an unconditional test change
seemed to make more sense than changing the test conditionally earlier
or building it wit
This patch is a followup to:
"c++: use diagnostic nesting [PR116253]"
Following Sy Brand's UX suggestions in P2429R0 for example 1, this patch
tweaks print_z_candidates to add a note about the number of candidates,
and adds a candidate number to each one.
Various examples of output can be seen
While working on fancy pointer support for the linked lists I noticed
they didn't have any debug assertions. This adds the obvious non-empty
assertions to front(), back(), pop_front() and pop_back().
For the pop members, adding an assertion to the underlying function that
erases a member means it
On 11/13/24 3:02 PM, Richard Sandiford wrote:
Indu Bhagat writes:
Store Allocation Tags (st2g) is an Armv8.5-A memory tagging (MTE)
instruction. It stores an allocation tag to two tag granules of memory.
TBD:
- Not too sure what is the best way to generate the st2g yet; A
subsequent pa
libstdc++-v3/ChangeLog:
* Makefile.am: Use $(MAKE) -C dir instead of cd dir && $(MAKE).
* Makefile.in: Regenerate.
---
We require GNU Make, so this is always supported.
Tested x86_64-linux. Pushed to trunk.
libstdc++-v3/Makefile.am | 4 ++--
libstdc++-v3/Makefile.in | 4 ++--
2
On Sat, 16 Nov 2024, 01:21 Jonathan Wakely, wrote:
> On Sat, 16 Nov 2024 at 01:09, Jonathan Wakely wrote:
> >
> > While working on fancy pointer support for the linked lists I noticed
> > they didn't have any debug assertions. This adds the obvious non-empty
> > assertions to front(), back(), po
On 11/15/24 10:19, Jan Hubicka wrote:
I have seen this happen when the result of the intersection is an empty
set (one of the few comments in value-range.h actually describes an
undefined range as an "empty range"). I have only seen this happen when
the edge has been redirected to builtin_unre
Hi!
The following patch adds a new tristate option for optimizations related to
replaceable global operators new/delete.
The option isn't called -fassume-sane-operator-new (which clang++
implements), because
1) clang++ option means something different; initially it was an
option to add malloc a
On 11/15/24 04:36, Jakub Jelinek wrote:
On Thu, Nov 14, 2024 at 06:25:49PM +0100, Jakub Jelinek wrote:
On Thu, Nov 14, 2024 at 10:05:05AM -0500, Andrew MacLeod wrote:
The inferred range mechanism is also initialized using cfun, so again
introducing a use of cfun shouldnt be an issue.
Somethi
Hi PA,
* I believe that all prep + middle end patches are approved and ready to go
* Pending for C and C++ are the three patches, attached to the email
I am hereby replying to - for the C and the C++ front end and the
common C/C++ testcases.
→ Those 3 patches LGTM - thanks!
Related but not
Hi all,
This is a patch submission following-up from the RFC at:
https://gcc.gnu.org/pipermail/gcc/2024-November/245076.html
The patch is rebased and retested against current trunk, some debugging code
removed, comments improved and some fixes added as I've we've done more
testing.
--
> On 15 Nov 2024, at 12:05, Richard Biener wrote:
>
> External email: Use caution opening links or attachments
>
>
> On Fri, 15 Nov 2024, Jennifer Schmitz wrote:
>
>>
>>
>>> On 7 Nov 2024, at 13:47, Richard Biener wrote:
>>>
>>> External email: Use caution opening links or attachments
>>
* Jakub Jelinek:
> On Fri, Nov 15, 2024 at 08:13:28PM +0100, Florian Weimer wrote:
>> * Andrew Pinski:
>>
>> > On Fri, Nov 15, 2024 at 9:13 AM Florian Weimer wrote:
>> >>
>> >> This is another recent GCC extension whose use is apparently
>> >> difficult to spot in code reviews.
>> >>
>> >> The n
This patch is a followup to:
"c++: use diagnostic nesting [PR116253]"
This patch tweaks how text output with experimental-nesting=yes
prints nested diagnostics, by omitting the leading "note: " from
nested notes.
This reduces the amount of visual cruft the user has to ignore when
reading C++ te
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
gcc/cp/ChangeLog:
* call.cc (print_conversion_rejection): When we're using
the location of the param in the decl, match the color
in the quoted source to that of %qI in the message.
Signed-off-by: David Malcolm
Introduce a helper function for complaining about "signed unsigned"
and "short long". Add colorization there so that e.g. the 'signed'
and 'unsigned' are given consisten contrasting colors in both the
message and the quoted source.
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
g
This warning covers the C23 incompibilities resulting from using
() as parameter lists in function declarations.
The warning name comes from Clang. The implementation is not
perfect because GCC treats these two declarations as equivalent:
void f ();
void f (not_a_type);
This is a bit confus
Does this seem like an interesting direction?
-- 8< --
A problem with coexistence of module std and the library headers is that
import and then #include tends to break (PR99000). But even with that
fixed, it might be useful to be able to test whether a module has been
imported. So, this patch i
This extends forwprop by yet another VEC_PERM optimization:
It attempts to blend two isomorphic vector sequences by using the
redundancy in the lane utilization in these sequences.
This redundancy in lane utilization comes from the way how specific
scalar statements end up vectorized: two VEC_PERMs
On Linux/x86_64,
c83e2d47574fd9a21f257e0f0d7e350c3f1b0618 is the first bad commit
commit c83e2d47574fd9a21f257e0f0d7e350c3f1b0618
Author: Jennifer Schmitz
Date: Mon Nov 4 07:56:09 2024 -0800
match.pd: Fold vec_perm with view_convert
caused
FAIL: gcc.dg/tree-ssa/pr117093.c (test for exces
r15-5327-g55e3bd376b2214 changes the default to -std=gnu23 but this
test now triggers -Wold-style-function-definition. Follow Joseph's advice
in that commit and tweak the test accordingly.
gcc/testsuite/ChangeLog:
* gcc.target/i386/pr66891.c: Pass -Wold-style-function-definition.
---
OK i
... with s/-function// and the commit message and ChangeLogs fixed, of course.
RISC-V N32 ABI means using 32-bit ABI on 64-bit ISA, the discussion in
https://github.com/riscv-non-isa/riscv-elf-psabi-doc/pull/381 .
At this moment, N32 is supported batemental toolchain.
Three OpenSource RTOS using this feature and have been merged in upstream.
You can see them in
EasyXem (A
On 11/15/24 8:16 PM, Sam James wrote:
r15-5327-g55e3bd376b2214 changes the default to -std=gnu23 but these
tests now trigger -Wold-style-function-definition. Follow Joseph's advice
in that commit and tweak the tests accordingly.
gcc/testsuite/ChangeLog:
* gcc.dg/graphite/id-15.c: Pas
> On 16 Nov 2024, at 03:28, Jeff Law wrote:
>
>
>
>> On 11/15/24 8:16 PM, Sam James wrote:
>> r15-5327-g55e3bd376b2214 changes the default to -std=gnu23 but these
>> tests now trigger -Wold-style-function-definition. Follow Joseph's advice
>> in that commit and tweak the tests accordingly.
r15-5327-g55e3bd376b2214 changes the default to -std=gnu23 but these
tests now trigger -Wold-style-definition. Follow Joseph's advice
in that commit and tweak the tests accordingly.
gcc/testsuite/ChangeLog:
* gcc.dg/graphite/id-15.c: Pass -Wno-old-style-definition.
* gcc.dg/graphi
Hi,
The attached patch attempts to enable automatic linking of libatomic, and makes
the following changes:
(1) Introduces a new driver option -f[no]-link-libatomic, which is enabled by
default.
(2) Adds new dependencies in toplevel Makefile.def so libatomic is built before
other target libraries
r15-5327-g55e3bd376b2214 changes the default to -std=gnu23 but these
tests now trigger -Wold-style-function-definition. Follow Joseph's advice
in that commit and tweak the tests accordingly.
gcc/testsuite/ChangeLog:
* gcc.dg/graphite/id-15.c: Pass -Wold-style-function-definition.
Hi,
When making a patch to adjust VECTOR_P8_VECTOR rs6000_vector
enum, I noticed that V1TImode's mode attribute in VI_unit
VECTOR_UNIT_ALTIVEC_P (V1TImode) is never true, since
VECTOR_UNIT_ALTIVEC_P checks if vector_unit[V1TImode] is
equal to VECTOR_ALTIVEC, but vector_unit[V1TImode] can only
be V
Hi,
As the associated test case shows, signbit generated assembly
is sub-optimal for _Float128 argument from memory on P8 LE.
On P8 LE, p8swap pass puts an explicit AND -16 on the memory,
which causes mode_dependent_address_p considers it's invalid
to change its mode and combine fails to make use
Hi,
Andi's greedy bit test finding algorithm was reverted. I found a fix for the
problem that caused the revert. I made this patch to reintroduce the greedy
alg into GCC. However I think we should keep the old slow but more powerful
algorithm so I added a limit on the number of cases of the swi
This patch only support landing pad value is 1.
The next version will implement function signature based labeling
scheme.
RISC-V CFI SPEC: https://github.com/riscv/riscv-cfi
gcc/ChangeLog:
* gcc/common/config/riscv/riscv-common.cc: Add ZICFILP ISA
string.
* gcc/config.gc
This patch is implemented according to the RISC-V CFI specification.
It supports the generation of shadow stack instructions in the prologue,
epilogue, non-local gotos, and unwinding.
RISC-V CFI SPEC: https://github.com/riscv/riscv-cfi
gcc/ChangeLog:
* common/config/riscv/riscv-common.cc:
gcc/ChangeLog:
* gcc/config/riscv/riscv.cc
(is_zicfilp_p): New function.
(is_zicfiss_p): New function.
* gcc/config/riscv/riscv-zicfilp.cc: Update.
* gcc/config/riscv/riscv.h: Update.
* gcc/config/riscv/riscv.md: Update.
---
gcc/config/riscv/risc
gcc/ChangeLog:
* gcc/config/riscv/riscv.cc
(riscv_file_end_indicate_exec_stack): Add .note.gnu.property.
* gcc/config/riscv/linux.h (TARGET_ASM_FILE_END): Define.
libgcc/ChangeLog:
* libgcc/config/riscv/crti.S: Add lpad instructions.
* libgcc/config/riscv/cr
On Thu, 14 Nov 2024 at 18:33, Torbjorn SVENSSON
wrote:
>
>
>
> On 2024-11-14 16:53, Christophe Lyon wrote:
> > On Sun, 10 Nov 2024 at 17:44, Torbjörn SVENSSON
> > wrote:
> >>
> >> Ok for trunk and releases/gcc-14?
> >>
> >> --
> >>
> >> When the feature "needs_status_wrapper" in dejagnu is used,
On Thu, 14 Nov 2024 at 18:16, Jan Hubicka wrote:
>
> > Hi!
> >
> > The inlining heuristics uses DECL_DECLARED_INLINE_P (whether a function
> > has been explicitly marked inline; that can be inline keyword, or for C++
> > also constexpr keyword or defining a function inside of a class definition)
>
This patch adds support for the SME_F16F16 extension. The extension
adds two new instructions to convert from a single vector of f16s
to two vectors of f32s. It also adds f16 variants of existing SME
ZA instructions.
gcc/
* config/aarch64/aarch64-option-extensions.def
(sme-f16f16
This patch adds support for the SVE_B16B16 extension, which provides
non-widening BF16 versions of existing instructions.
Mostly it's just a simple extension of iterators. The main
complications are:
(1) The new instructions have no immediate forms. This is easy to
handle for the cond_* pat
@aarch64_sme_write and *aarch64_sme_write_plus
were using UNSPEC_SME_READ instead of UNSPEC_SME_WRITE.
gcc/
* config/aarch64/aarch64-sme.md (@aarch64_sme_write)
(*aarch64_sme_write_plus): Use UNSPEC_SME_WRITE instead
of UNSPEC_SME_READ.
---
gcc/config/aarch64/aarch64-sme.m
> Hi Jakub,
>
> Good catch! Does it fix any specific PR?
>
> If you don't have the time, I would be happy to apply the correction to
> 13-branch through to mainline.
I caught it with my WIP patch to improve tree-ssa-dce. I am not aware
it can produce wrong code. It will likely lead to missed o
This patch adds support for FEAT_SME2p1. There are two sets of
new instructions: MOVAZ to read from ZA and zero the source data,
and new forms of ZERO. All of them require streaming mode.
MOVAZ can't reuse the existing UNSPEC_SME_READ* patterns because
of the write to ZA. I did wonder about try
This patch adds support for the SME_B16B16 extension. It follows
similar lines to the SME_F16F16 extension added earlier.
gcc/
* config/aarch64/aarch64-option-extensions.def
(sme-b16b16): New extension.
* doc/invoke.texi: Document it.
* config/aarch64/aarch64.h (TA
Hi,
Paul-Antoine Arras wrote:
This patch adds support for the `dispatch` construct and the
`adjust_args` clause to the Fortran front-end.
Handling of `adjust_args` across translation units is missing due
to PR115271.
First, can you add a run-time test?
[I think it helps to have at least one
On Fri, 15 Nov 2024, Jan Hubicka wrote:
> Hi,
> To implement pointer parameters reproducible and unsequenced I would like to
> use fnspec built at callgraph construction time. Pointer parameters are
> either
> const or non-const. After discussion with Jens, I now understand that memory
> pointe
On 11/15/24 12:17 AM, Richard Biener wrote:
On Thu, Nov 14, 2024 at 10:41 PM Jeff Law wrote:
Several weeks ago I was looking at SATD and realized that we had loads
of permutation constants that could be implemented as a trivial
adjustment to a prior loaded permutation constant.
For exampl
Hi Jeff,
The patch has support for both. In the test cases, approx half the test cases
have min(a, b) op max(a, b) and the other half have max(a, b) op min(a, b).
Regards,
Eikansh
From: Andrew Pinski
Sent: Friday, November 15, 2024 7:03 AM
To: Jeff Law
Cc: Eika
On Fri, 15 Nov 2024 at 12:02, Jakub Jelinek wrote:
>
> On Fri, Nov 15, 2024 at 11:25:00AM +, Jonathan Wakely wrote:
> > On Thu, 14 Nov 2024 at 18:16, Jan Hubicka wrote:
> > >
> > > > Hi!
> > > >
> > > > The inlining heuristics uses DECL_DECLARED_INLINE_P (whether a function
> > > > has been e
There are separate patterns for predicated FADD, FSUB, and FMUL.
Previously they each had their own in-built split to convert the
instruction to unpredicated form where appropriate. However, it's
more convenient for later patches if we use a single separate split
instead.
gcc/
* config/aa
This patch just renames the iterators SME_READ and SME_WRITE to
SME_READ_HV and SME_WRITE_HV, to distinguish them from other forms
of ZA read and write.
gcc/
* config/aarch64/iterators.md (SME_READ): Rename to...
(SME_READ_HV): ...this.
(SME_WRITE): Rename to...
(SM
On Fri, 15 Nov 2024 at 15:12, Jason Merrill wrote:
>
> On 11/15/24 9:20 AM, Jonathan Wakely wrote:
> > On 15/11/24 08:53 -0500, Jason Merrill wrote:
> >> On 11/15/24 6:04 AM, Jonathan Wakely wrote:
> >>> On 14/11/24 23:09 -0500, Jason Merrill wrote:
>
> Since bits/stdc++.h also intends to inc
>
> I have seen this happen when the result of the intersection is an empty
> set (one of the few comments in value-range.h actually describes an
> undefined range as an "empty range"). I have only seen this happen when
> the edge has been redirected to builtin_unreachable because, the has
> been
On Fri, 15 Nov 2024 at 15:20, Jonathan Wakely wrote:
>
> On Fri, 15 Nov 2024 at 15:12, Jason Merrill wrote:
> >
> > On 11/15/24 9:20 AM, Jonathan Wakely wrote:
> > > On 15/11/24 08:53 -0500, Jason Merrill wrote:
> > >> On 11/15/24 6:04 AM, Jonathan Wakely wrote:
> > >>> On 14/11/24 23:09 -0500, J
Remove some preprocessor conditionals by moving the _M_size member for
the cxx11 ABI into a new base class, which is empty for the gcc4-compat
ABI.
Move some unused members that are only retained for ABI compatibility to
the end of _List_base and add an explanatory comment. Stop using
list::_M_nod
Currently std::list uses raw pointers to connect its nodes, which is
non-conforming. We should use the allocator's pointer type everywhere
that a "pointer" is needed.
Because the existing types like _List_node are part of the ABI now,
we can't change them. To support nodes that are connected by fa
We can just use the injected-class-name instead of defining a new name.
That seems simpler.
libstdc++-v3/ChangeLog:
* include/bits/stl_list.h (_List_iterator): Remove _Self typedef
and just use injected-class-name instead.
(_List_const_iterator): Likewise.
---
Tested x86_
When configuring GCC for RV32EC with:
./configure \
--target=riscv32-none-elf \
--with-multilib-generator="rv32ec-ilp32e--" \
--with-abi=ilp32e \
--with-arch=rv32ec
Then the build fails becaus
On Thu, Nov 14, 2024 at 7:50 PM Soumya AR wrote:
>
> The SVE SUBR instruction performs a reversed subtract from an immediate.
>
> This patches enables the emission of SUBR for Neon modes and avoids the need
> to
> materialise an explicit constant.
>
> For example, the below test case:
>
> typedef
Paul-Antoine Arras wrote:
OpenMP: common C/C++ testcases for dispatch + adjust_args
gcc/testsuite/ChangeLog:
...
libgomp/ChangeLog:
* testsuite/libgomp.c-c++-common/dispatch-1.c: New test.
* testsuite/libgomp.c-c++-common/dispatch-2.c: New test.
LGTM
On Thu, Nov 14, 2024 at 08:53:48PM +, Sam James wrote:
> r15-5257-g56ded80b96b0f6 didn't regenerate configure correctly.
>
> See https://inbox.sourceware.org/gcc-patches/zzzf69gorvpro...@zen.kayari.org/.
>
> gcc/ChangeLog:
>
> * configure: Regenerate.
> ---
> Pushed as obvious.
Thank
From: Pan Li
The test files of scalar SAT_SUB only has numbers as the suffix.
Rearrange the file name to -{form number}-{target-type}. For example,
test form 3 for uint32_t SAT_SUB will have -3-u32.c for asm check and
-run-3-u32.c for the run test.
Meanwhile, all related test files moved to ris
On Fri, Nov 15, 2024 at 11:25:00AM +, Jonathan Wakely wrote:
> On Thu, 14 Nov 2024 at 18:16, Jan Hubicka wrote:
> >
> > > Hi!
> > >
> > > The inlining heuristics uses DECL_DECLARED_INLINE_P (whether a function
> > > has been explicitly marked inline; that can be inline keyword, or for C++
> >
> On 15 Nov 2024, at 12:33, Wilco Dijkstra wrote:
>
> Hi Kyrill,
>
>> This would make USE_NEW_VECTOR_COSTS effectively the default.
>> Jennifer has been trying to do that as well and then to remove it (as it
>> would be always true) but there are some codegen regressions that still >
>> need
On Fri, 15 Nov 2024, Richard Biener wrote:
> On Fri, 15 Nov 2024, Richard Sandiford wrote:
>
> > Richard Biener writes:
> > > The following ensures that peeling a single iteration for gaps is
> > > sufficient by enforcing niter masking (partial vector use) given
> > > we cannot (always) statical
Hi,
To implement pointer parameters reproducible and unsequenced I would like to
use fnspec built at callgraph construction time. Pointer parameters are either
const or non-const. After discussion with Jens, I now understand that memory
pointed to by const pointers can only be read directly and n
We fail to demote this to VMAT_ELEMENTWISE and thus run into the three
vector permutation limit (and would not consider to use strided loads
or gathers).
This resolves another bunch of SVE regressions with --param
vect-force-slp=1
PR tree-optimization/117605
* tree-vect-stmts.cc (
The following ensures that peeling a single iteration for gaps is
sufficient by enforcing niter masking (partial vector use) given
we cannot (always) statically decide when the vector size isn't known.
The condition guarding this and thus statically giving a pass in
some cases for VL vectors is que
The following flips the vectorizer to forced SLP, there is almost
no expected fallout at this point, the remains should be target
specific cost modeling issues.
* params.opt (vect-force-slp): Default to 1.
---
gcc/params.opt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --gi
The following tries to reduce the amount of difference between
SLP and non-SLP for single-element interleaving load classification.
This fixes another fallout of --param vect-force-slp=1
PR tree-optimization/117606
* tree-vect-stmts.cc (get_group_load_store_type): For single
On 11/15/24 6:04 AM, Jonathan Wakely wrote:
On 14/11/24 23:09 -0500, Jason Merrill wrote:
On 10/18/24 9:38 AM, Jason Merrill wrote:
Currently this installs the sources under $(gxx_include_dir)/bits/,
i.e. /usr/include/c++/15/bits. So with my -fsearch-include-path change,
std.cc can be compil
Hi All,
This patch makes it so that when you use any of the Cortex-A53 errata
workarounds but have specified an -march or -mcpu we know is not affected by it
that we suppress the errata workaround.
This is a driver only patch as the linker invocation needs to be changed as
well. The linker and c
Hi,
When making patch to replace TARGET_P8_VECTOR, I noticed
for *eqv3_internal1 unlike the other logical
operations, we only exploited the vsx version. I think it
is an oversight, this patch is to consider veqv as well.
Bootstrapped and regtested on ppc64-linux P8/P9 and
ppc64le-linux P9/P10 tw
Hi,
This patch is to adjust define_insn altivec_v{add,sub}uqm
with standard names, as the associated test case shows, w/o
this patch, it ends up with scalar {add,subf}c/{add,subf}e,
the standard names help to exploit v{add,sub}uqm.
Bootstrapped and regtested on ppc64-linux P8/P9 and
ppc64le-linux
The following tries to reduce the amount of difference between
SLP and non-SLP for single-element interleaving load classification.
This fixes another fallout of --param vect-force-slp=1
Bootstraped on x86_64-unknown-linux-gnu, testing in progress.
PR tree-optimization/117606
* t
1 - 100 of 171 matches
Mail list logo
