On Tue, 2 May 2023, Christophe Lyon wrote:
> Hi Richard,
>
> On Fri, 28 Apr 2023 at 14:41, Richard Biener via Gcc-patches <
> gcc-patches@gcc.gnu.org> wrote:
>
> > This adds a scatter vectorization capability to the vectorizer
> > without target support by decomposing the offset and data vectors
On Tue, May 2, 2023 at 11:36 PM Jeff Law wrote:
>
>
>
> On 5/3/23 00:27, Andrew Pinski via Gcc-patches wrote:
> > On Tue, May 2, 2023 at 11:14 PM Richard Biener
> > wrote:
> >>
> >> On Wed, May 3, 2023 at 12:04 AM Andrew Pinski wrote:
> >>>
> >>> On Tue, May 2, 2023 at 5:26 AM Richard Biener via
On 5/3/23 00:27, Andrew Pinski via Gcc-patches wrote:
On Tue, May 2, 2023 at 11:14 PM Richard Biener
wrote:
On Wed, May 3, 2023 at 12:04 AM Andrew Pinski wrote:
On Tue, May 2, 2023 at 5:26 AM Richard Biener via Gcc-patches
wrote:
On Sun, Apr 30, 2023 at 11:14 PM Andrew Pinski via Gcc-
On 5/2/23 14:34, Patrick O'Neill wrote:
Is this OK for a backport to GCC-13 as well?
Let me sync with Richi & Jakub. They're the release managers and this
doesn't fall under the usual rules for things that can be backported.
jeff
On Tue, May 2, 2023 at 11:14 PM Richard Biener
wrote:
>
> On Wed, May 3, 2023 at 12:04 AM Andrew Pinski wrote:
> >
> > On Tue, May 2, 2023 at 5:26 AM Richard Biener via Gcc-patches
> > wrote:
> > >
> > > On Sun, Apr 30, 2023 at 11:14 PM Andrew Pinski via Gcc-patches
> > > wrote:
> > > >
> > > >
On Wed, May 3, 2023 at 1:15 AM Andrew Pinski via Gcc-patches
wrote:
>
> While looking to move substitute_and_fold_engine
> over to use simple_dce_from_worklist, I noticed
> that we don't record the stats of the removed stmts/phis.
> So this does that.
>
> OK? Bootstrapped and tested on x86_64-linu
On Wed, May 3, 2023 at 12:04 AM Andrew Pinski wrote:
>
> On Tue, May 2, 2023 at 5:26 AM Richard Biener via Gcc-patches
> wrote:
> >
> > On Sun, Apr 30, 2023 at 11:14 PM Andrew Pinski via Gcc-patches
> > wrote:
> > >
> > > While looking at differences between what minmax_replacement
> > > and mat
On Tue, May 2, 2023 at 4:45 PM Alexander Monakov via Gcc-patches
wrote:
>
> When instrumentation is requested via -fsanitize-coverage=trace-pc, GCC
> emits calls to __sanitizer_cov_trace_pc callback into each basic block.
> This callback is supposed to be implemented by the user, and should be
> a
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
We try to cache the result of reduce_template_parm_level so that when we
reduce the same parm multiple times we get the same result, but this wasn't
working for template template parms because in that case TYPE is a
TEMPLATE_TEMPLATE_PARM, a
While improving replace_phi_edge_with_variable for the diamond formed bb
case, I needed a new function, copy_phi_args and then I went to search for
similar code and noticed both gimple_duplicate_sese_tail and
remove_forwarder_block have the same code I need. So I decided it would
be best if I facto
While looking at differences between what minmax_replacement
and match_simplify_replacement does. I noticed that they sometimes
chose different edges to remove. I decided we should be able to do
better and be able to remove both empty basic blocks in the
case of match_simplify_replacement as that m
This patch always sets _M_string_length in the constructor specialized
for range of input_iterator, for the cases like istringstream.
We copy from source range to the local buffer, and then reallocate to
a larger one if necessary. When disposing the old buffer, the old buffer
could be provisioned
Hi Jonathan,
Thank you for your review and suggestion. The change looks great!
Assigning a value with an immediate zero is indeed much faster.
in v2:
* revised the commit message a little bit, I found it a little bit
difficult to parse when re-reading it.
* associated the commit with PR/libstd
On Tue, May 2, 2023 at 5:38 PM Kito Cheng via Gcc-patches
wrote:
>
> > >>> Pushed to trunk, thanks for catching that, that's definitely should
> > >>> use log2 no matter C++03 or C++11,
> > >>> but I think GCC allows the usage of C++11 according to
> > >>> https://gcc.gnu.org/install/prerequisites
> >>> Pushed to trunk, thanks for catching that, that's definitely should
> >>> use log2 no matter C++03 or C++11,
> >>> but I think GCC allows the usage of C++11 according to
> >>> https://gcc.gnu.org/install/prerequisites.html :P
> >> Yes, we should be able to use C++11. I'd like to get that to
While looking to move substitute_and_fold_engine
over to use simple_dce_from_worklist, I noticed
that we don't record the stats of the removed stmts/phis.
So this does that.
OK? Bootstrapped and tested on x86_64-linux-gnu.
gcc/ChangeLog:
* tree-ssa-dce.cc (simple_dce_from_worklist): Reco
This PR points out that std::is_convertible has given the wrong answer
in
static_assert (!std::is_convertible_v , "");
since r13-2822 implemented __is_{,nothrow_}convertible.
std::is_convertible uses the imaginary
To test() { return std::declval(); }
to do its job. Here, From is 'int () c
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
I noticed that for member class templates of a class template we were
unnecessarily substituting both the template and its type. Avoiding that
duplication speeds compilation of this silly testcase from ~12s to ~9s on my
laptop. It's unlike
On Wed, Apr 26, 2023 at 12:18:36PM -0400, Michael Meissner wrote:
> * gcc/config/rs6000/genfusion.pl (gen_ld_cmpi_p10): Improve generation
> of the ld and lwa instructions which use the DS encoding instead of D.
> Use the YZ constraint for these loads. Handle prefixed loads bette
On Tue, May 2, 2023 at 5:26 AM Richard Biener via Gcc-patches
wrote:
>
> On Sun, Apr 30, 2023 at 11:14 PM Andrew Pinski via Gcc-patches
> wrote:
> >
> > While looking at differences between what minmax_replacement
> > and match_simplify_replacement does. I noticed that they sometimes
> > chose di
On 4/28/23 6:49 PM, Hans-Peter Nilsson wrote:
> On Fri, 28 Apr 2023, Jeff Law wrote:
>> So while what Ajit has done is a step forward, at some point the actual
>> details of the ABI need to be described in a way that can be checked and
>> consumed by REE.
>
> IIRC I also commented and suggested a
Hi!
On Tue, May 02, 2023 at 05:20:49PM +0100, Roger Sayle wrote:
> On 02 May 2023 14:49, Segher Boessenkool wrote:
> Then combine inserts an additional copy:
Combine makes sure a pseudo-to-pseudo move remains. Without that,
combine will seize part of RA's job, and butcher it. It has always done
On Tue, May 2, 2023 at 5:24 AM Richard Biener via Gcc-patches
wrote:
>
> On Sun, Apr 30, 2023 at 11:13 PM Andrew Pinski via Gcc-patches
> wrote:
> >
> > This ports the clrsb builtin part of builtin_zero_pattern
> > to match.pd. A simple pattern to port.
> >
> > OK? Bootstrapped and tested on x86_
I accidently messed up these patterns so the comparison
against 0 and the arguments was not matching up when they
need to be.
I committed this as obvious after a bootstrap/test on x86_64-linux-gnu
PR tree-optimization/109702
gcc/ChangeLog:
* match.pd: Fix "a != 0 ? FUNC(a) : CST
constraints_satisfied_p already carefully checks dependence of template
arguments before proceeding with satisfaction, so the dependence check
in instantiate_alias_template is unnecessary and overly conservative.
Getting rid of it allows us to check satisfaction ahead of time in more
cases as in th
On Tue, May 2, 2023 at 5:23 AM Richard Sandiford via Gcc-patches
wrote:
>
> Andrew Pinski via Gcc-patches writes:
> > There is no canonical form for this case defined. So the aarch64 backend
> > needs
> > a pattern to match both of these forms.
> >
> > The forms are:
> > (set (reg/i:SI 0 x0)
> >
Hi Kito,
Le 02/05/2023 à 17:51, Kito Cheng a écrit :
>>> Pushed to trunk, thanks for catching that, that's definitely should
>>> use log2 no matter C++03 or C++11,
>>> but I think GCC allows the usage of C++11 according to
>>> https://gcc.gnu.org/install/prerequisites.html :P
>> Yes, we should be
On Thu, 27 Apr 2023 at 16:58, Marek Polacek wrote:
> On Thu, Apr 27, 2023 at 12:16:34PM +0100, Jonathan Wakely via Gcc-patches
> wrote:
> > C2x adds the ability to give an enumeration type a fixed underlying
> > type, as C++ already has. The -fshort-enums option alters the compiler's
> > choice of
Is this OK for a backport to GCC-13 as well?
(with the whitespace fixes/changelog revision squashed into it)
Patrick
On 4/26/23 10:01, Patrick O'Neill wrote:
Committed - I had to reformat the changelog so it would push and resolve a
trivial merge conflict in riscv.opt.
---
RISC-V has no supp
Updated the amo/load/store/fence tests to use check-function-bodies to
ensure ordering. This is especially important for Load/Store where
we want to ensure the correct fence is emitted in the correct spot.
Compare exchange & subword amo ops still use scan-assembler-times.
The change to check-func
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
In the testcase below, we push_to_top_level to instantiate f and g, and they
can both use the previous_class_level cache from instantiating A.
Wiping the cache in pop_from_top_level is not helpful; we'll do that in
pushclass if needed.
te
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
While looking at the empty base handling for 109678, it occurred to me that
we ought to be able to look for an empty base at a specific offset, not just
in general.
PR c++/109678
gcc/cp/ChangeLog:
* cp-tree.h (lookup_base)
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
Here, when dealing with a class with a complex subobject structure, we would
try and fail to find the relevant FIELD_DECL for an empty base before giving
up. And we would do this at each level, in a combinatorially problematic
way. Instead
On 4/28/23 11:04, Jeff Law wrote:
On 4/27/23 10:23, Patrick O'Neill wrote:
This change brings atomic loads in line with table A.6 of the ISA
manual.
2023-04-27 Patrick O'Neill
gcc/ChangeLog:
* config/riscv/sync.md (atomic_load): Implement atomic
load mapping.
OK.
jeff
Committe
On 4/28/23 10:40, Jeff Law wrote:
On 4/27/23 10:22, Patrick O'Neill wrote:
This change makes atomic stores strictly stronger than table A.6 of the
ISA manual. This mapping makes the overall patchset compatible with
table A.7 as well.
2023-04-27 Patrick O'Neill
PR 89835
Should be "PR
On 4/28/23 11:00, Jeff Law wrote:
On 4/27/23 10:22, Patrick O'Neill wrote:
This change brings atomic fences in line with table A.6 of the ISA
manual.
Relax mem_thread_fence according to the memmodel given.
2023-04-27 Patrick O'Neill
gcc/ChangeLog:
* config/riscv/sync.md (mem_thread_
On 4/28/23 10:56, Jeff Law wrote:
On 4/27/23 10:22, Patrick O'Neill wrote:
Introduce the %I and %J flags for setting the .aqrl bits on LR/SC pairs
as needed.
Atomic compare and exchange ops provide success and failure memory
models. C++17 and later place no restrictions on the relative stre
On 4/28/23 10:34, Jeff Law wrote:
On 4/27/23 10:22, Patrick O'Neill wrote:
This patch sets the relevant .rl bits on amo operations.
2023-04-27 Patrick O'Neill
gcc/ChangeLog:
* config/riscv/riscv.cc (riscv_print_operand): change behavior
of %A to include release bits.
Capitalize
On 4/28/23 10:43, Jeff Law wrote:
On 4/27/23 10:22, Patrick O'Neill wrote:
Atomic operations with the appropriate bits set already enfore release
semantics. Remove unnecessary release fences from atomic ops.
This change brings AMO ops in line with table A.6 of the ISA manual.
2023-04-27 Pa
On 4/28/23 10:23, Jeff Law wrote:
On 4/27/23 10:22, Patrick O'Neill wrote:
This patch enforces SEQ_CST for atomic compare_exchange ops.
Replace Fence/LR.aq/SC.aq pairs with SEQ_CST LR.aqrl/SC.rl pairs
recommended by table A.6 of the ISA manual.
2023-04-27 Patrick O'Neill
gcc/ChangeLog:
On 4/27/23 09:22, Patrick O'Neill wrote:
Replace LR.aq/SC.rl pairs with the SEQ_CST LR.aqrl/SC.rl pairs
recommended by table A.6 of the ISA manual.
2023-04-27 Patrick O'Neill
gcc/ChangeLog:
* config/riscv/sync.md: Change LR.aq/SC.rl pairs into
sequentially consistent LR.aqrl
On 4/28/23 09:50, Jeff Law wrote:
On 4/27/23 10:22, Patrick O'Neill wrote:
Replace LR.aq/SC.rl pairs with the SEQ_CST LR.aqrl/SC.rl pairs
recommended by table A.6 of the ISA manual.
2023-04-27 Patrick O'Neill
libgcc/ChangeLog:
* config/riscv/atomic.c: Change LR.aq/SC.rl pairs into
On 4/28/23 09:23, Jeff Law wrote:
On 4/27/23 10:22, Patrick O'Neill wrote:
Remove references to MEMMODEL_SYNC_* models by converting via
memmodel_base().
2023-04-27 Patrick O'Neill
gcc/ChangeLog:
* config/riscv/riscv.cc: Remove MEMMODEL_SYNC_* cases and
sanitize memmodel input with m
on Tue, 2 May 2023, Patrick Palka wrote:
> On Tue, 2 May 2023, Jason Merrill wrote:
>
> > On 5/1/23 15:59, Patrick Palka wrote:
> > > Here we're incorrectly deeming the templated call a.g() inside b's
> > > initializer as potentially constant, despite g being non-constexpr,
> > > which leads to u
On Tue, 2 May 2023, Jason Merrill wrote:
> On 5/1/23 15:59, Patrick Palka wrote:
> > Here we're incorrectly deeming the templated call a.g() inside b's
> > initializer as potentially constant, despite g being non-constexpr,
> > which leads to us wastefully instantiating the initializer ahead of ti
On 5/2/23 11:19, Jakub Jelinek wrote:
Hi!
During patch backporting, I've noticed that while most cp_walk_tree calls
with cp_fold_r callback callers were changed from &pset to cp_fold_data
&data, the VEC_INIT_EXPR gimplifications has not, so it still passes just
address of a hash_set and so if du
On 5/1/23 15:59, Patrick Palka wrote:
enforce_access currently inspects processing_template_decl to determine
whether to defer the given access check until instantiation time. But
using this flag is unreliable because it gets cleared during e.g.
non-dependent initializer folding, and can lead to
On 5/1/23 15:59, Patrick Palka wrote:
Here we're incorrectly deeming the templated call a.g() inside b's
initializer as potentially constant, despite g being non-constexpr,
which leads to us wastefully instantiating the initializer ahead of time
and triggering a bug in access checking deferral (w
On 5/1/23 19:54, Marek Polacek wrote:
Sadly, -Wdangling-reference generates false positives for std::span-like
user classes, and it seems imprudent to attempt to improve the heuristic
in GCC 13. Let's move the warning to -Wextra, that will hopefully
reduce the number of false positives the users
On Tue, May 02, 2023 at 05:50:17PM +0200, Jakub Jelinek via Gcc-patches wrote:
> On Tue, May 02, 2023 at 04:42:52PM +0100, Jonathan Wakely wrote:
> > On Tue, 2 May 2023 at 09:45, Jakub Jelinek wrote:
> >
> > > Hi!
> > >
> > > The following patch regenerates the ABI files (I've only changed the
>
See also https://gcc.gnu.org/PR109128 (+ description in the patch log)
The linker plugin API was designed to handle LTO - such that the compiler (i.e.
GCC's lto-plugin)
can claim an input file if it finds LTO code. In that case, the symbols inside
that file are ignored
by 'ld'.
However, GCC al
> -Original Message-
> From: Christophe Lyon
> Sent: Tuesday, April 18, 2023 2:46 PM
> To: gcc-patches@gcc.gnu.org; Kyrylo Tkachov ;
> Richard Earnshaw ; Richard Sandiford
>
> Cc: Christophe Lyon
> Subject: [PATCH 13/22] arm: [MVE intrinsics] rework vorrq
>
> Implement vorrq using th
On 5/1/23 21:24, Hans-Peter Nilsson via Gcc-patches wrote:
There may be
minor code quality regressions or there may be minor code quality
improvements -- I'm leaving that for the port maintainers to own going
forward.
Right; I noticed performance regressions, and didn't want to
commit
> -Original Message-
> From: Christophe Lyon
> Sent: Tuesday, April 18, 2023 2:46 PM
> To: gcc-patches@gcc.gnu.org; Kyrylo Tkachov ;
> Richard Earnshaw ; Richard Sandiford
>
> Cc: Christophe Lyon
> Subject: [PATCH 12/22] arm: [MVE intrinsics] add binary_orrq shape
>
> patch adds the
> -Original Message-
> From: Christophe Lyon
> Sent: Tuesday, April 18, 2023 2:46 PM
> To: gcc-patches@gcc.gnu.org; Kyrylo Tkachov ;
> Richard Earnshaw ; Richard Sandiford
>
> Cc: Christophe Lyon
> Subject: [PATCH 11/22] arm: [MVE intrinsics] rework vandq veorq
>
> Implement vamdq, v
> -Original Message-
> From: Christophe Lyon
> Sent: Tuesday, April 18, 2023 2:46 PM
> To: gcc-patches@gcc.gnu.org; Kyrylo Tkachov ;
> Richard Earnshaw ; Richard Sandiford
>
> Cc: Christophe Lyon
> Subject: [PATCH 10/22] arm: [MVE intrinsics] factorize vandq veorq vorrq
> vbicq
>
> F
> -Original Message-
> From: Christophe Lyon
> Sent: Tuesday, April 18, 2023 2:46 PM
> To: gcc-patches@gcc.gnu.org; Kyrylo Tkachov ;
> Richard Earnshaw ; Richard Sandiford
>
> Cc: Christophe Lyon
> Subject: [PATCH 09/22] arm: [MVE intrinsics] add binary shape
>
> This patch adds the
> -Original Message-
> From: Christophe Lyon
> Sent: Tuesday, April 18, 2023 2:46 PM
> To: gcc-patches@gcc.gnu.org; Kyrylo Tkachov ;
> Richard Earnshaw ; Richard Sandiford
>
> Cc: Christophe Lyon
> Subject: [PATCH 08/22] arm: [MVE intrinsics] rework vaddq vmulq vsubq
>
> Implement va
On 4/29/23 19:40, Kito Cheng wrote:
Hi Jeff:
The RTL pattern already models tail element and vector length well,
so I don't feel the first version of Pan's patch has any problem?
Input RTL pattern:
#(insn 10 7 12 2 (set (reg:VNx2BI 134 [ _1 ])
#(if_then_else:VNx2BI (unspec:VNx2BI [
On 5/2/23 08:50, Jeff Law wrote:
On 5/1/23 10:10, Patrick O'Neill wrote:
This patch fixes the changelog to explicitly name the added command line
flags introduced in this patch:
https://gcc.gnu.org/pipermail/gcc-patches/2023-April/616807.html
2023-05-01 Patrick O'Neill
gcc/ChangeLog:
* C
On 5/2/23 18:19, Kyrylo Tkachov wrote:
-Original Message-
From: Christophe Lyon
Sent: Tuesday, April 18, 2023 2:46 PM
To: gcc-patches@gcc.gnu.org; Kyrylo Tkachov ;
Richard Earnshaw ; Richard Sandiford
Cc: Christophe Lyon
Subject: [PATCH 07/22] arm: [MVE intrinsics] factorize vadd
On 02 May 2023 14:49, Segher Boessenkool wrote:
> On Tue, May 02, 2023 at 02:18:43PM +0100, Roger Sayle wrote:
> > On 02 May 2023 13:40, Paul Koning wrote:
> > > > On May 1, 2023, at 7:37 PM, Roger Sayle
> > > >
> > > wrote:
> > > > The shiftsi.cc regression on xstormy16 is fixed by adding
> > >
> -Original Message-
> From: Christophe Lyon
> Sent: Tuesday, April 18, 2023 2:46 PM
> To: gcc-patches@gcc.gnu.org; Kyrylo Tkachov ;
> Richard Earnshaw ; Richard Sandiford
>
> Cc: Christophe Lyon
> Subject: [PATCH 07/22] arm: [MVE intrinsics] factorize vadd vsubq vmulq
>
> In order t
> -Original Message-
> From: Christophe Lyon
> Sent: Tuesday, April 18, 2023 2:46 PM
> To: gcc-patches@gcc.gnu.org; Kyrylo Tkachov ;
> Richard Earnshaw ; Richard Sandiford
>
> Cc: Christophe Lyon
> Subject: [PATCH 06/22] arm: [MVE intrinsics] add
> unspec_based_mve_function_exact_insn
> -Original Message-
> From: Christophe Lyon
> Sent: Tuesday, April 18, 2023 2:46 PM
> To: gcc-patches@gcc.gnu.org; Kyrylo Tkachov ;
> Richard Earnshaw ; Richard Sandiford
>
> Cc: Christophe Lyon
> Subject: [PATCH 05/22] arm: [MVE intrinsics] add binary_opt_n shape
>
> This patch add
> -Original Message-
> From: Christophe Lyon
> Sent: Tuesday, April 18, 2023 2:46 PM
> To: gcc-patches@gcc.gnu.org; Kyrylo Tkachov ;
> Richard Earnshaw ; Richard Sandiford
>
> Cc: Christophe Lyon
> Subject: [PATCH 04/22] arm: [MVE intrinsics] Rework vuninitialized
>
> Implement vunin
Discussed in the patchworks meeting with Jeff Law and decided to move
forward with the trailing fence compatibility approach. If the trailing
fence becomes a performance issue and people want to generate A.6 code,
we'll need a PSABI change to identify which mapping a binary uses. We'll
cross that
On 5/1/23 17:37, Roger Sayle wrote:
Jeff Law wrote:
This patch converts the xstormy16 patch to LRA. It introduces a code
quality regression in the shiftsi testcase, but it also fixes numerous
aborts/errors. IMHO it's a good tradeoff.
I've investigated the shiftsi regression on xstormy16
GCC maintainers:
The following patch adds three buitins for inserting and extracting the
exponent and significand for an IEEE 128-bit floating point values.
The builtins are valid for Power 9 and Power 10.
The patch has been tested on both Power 9 and Power 10.
Please let me know if this patc
> > Pushed to trunk, thanks for catching that, that's definitely should
> > use log2 no matter C++03 or C++11,
> > but I think GCC allows the usage of C++11 according to
> > https://gcc.gnu.org/install/prerequisites.html :P
> Yes, we should be able to use C++11. I'd like to get that to C++17 at
>
On Tue, May 02, 2023 at 04:42:52PM +0100, Jonathan Wakely wrote:
> On Tue, 2 May 2023 at 09:45, Jakub Jelinek wrote:
>
> > Hi!
> >
> > The following patch regenerates the ABI files (I've only changed the
> > Linux files which were updated recently (last month)).
> >
> > Tested on x86_64-linux, ok
On 5/1/23 10:10, Patrick O'Neill wrote:
This patch fixes the changelog to explicitly name the added command line
flags introduced in this patch:
https://gcc.gnu.org/pipermail/gcc-patches/2023-April/616807.html
2023-05-01 Patrick O'Neill
gcc/ChangeLog:
* ChangeLog: Name the flags ad
On Tue, May 02, 2023 at 10:11:27AM -0400, Paul Koning wrote:
> > On May 2, 2023, at 9:18 AM, Roger Sayle wrote:
> > Yes, see the section -fsplit-wide-types in
> > https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html
>
> Thanks. So I'm wondering why that would be a problem.
>
> The obvious q
On 5/2/23 17:28, Kyrylo Tkachov wrote:
-Original Message-
From: Christophe Lyon
Sent: Tuesday, May 2, 2023 3:05 PM
To: Kyrylo Tkachov ; gcc-patches@gcc.gnu.org;
Richard Earnshaw ; Richard Sandiford
Subject: Re: [PATCH 03/22] arm: [MVE intrinsics] Rework vreinterpretq
On 5/2/23
On 5/2/23 08:31, Kito Cheng via Gcc-patches wrote:
Hi Romain:
Pushed to trunk, thanks for catching that, that's definitely should
use log2 no matter C++03 or C++11,
but I think GCC allows the usage of C++11 according to
https://gcc.gnu.org/install/prerequisites.html :P
Yes, we should be able
On Fri, 28 Apr 2023 at 23:02, Jakub Jelinek wrote:
> On Fri, Apr 28, 2023 at 09:35:49AM +0100, Jonathan Wakely wrote:
> > Yes, for both, thanks for the fix.
> >
> > After it lands on the gcc-13 branch I'll also update the manual with:
> >
> > --- a/libstdc++-v3/doc/xml/manual/abi.xml
> > +++ b/li
On Tue, 2 May 2023 at 09:45, Jakub Jelinek wrote:
> Hi!
>
> The following patch regenerates the ABI files (I've only changed the
> Linux files which were updated recently (last month)).
>
> Tested on x86_64-linux, ok for trunk and later 13.2?
>
OK, thanks.
I currently get:
FAIL: libstdc++-abi/a
committed, thanks for the patch :)
On Fri, Apr 28, 2023 at 6:37 PM Li, Pan2 via Gcc-patches
wrote:
>
> Kindly ping for this ICE fix.
>
> Pan
>
> -Original Message-
> From: Wang, Yanzhang
> Sent: Wednesday, April 26, 2023 9:06 PM
> To: gcc-patches@gcc.gnu.org
> Cc: juzhe.zh...@rivai.ai; k
> -Original Message-
> From: Christophe Lyon
> Sent: Tuesday, May 2, 2023 3:05 PM
> To: Kyrylo Tkachov ; gcc-patches@gcc.gnu.org;
> Richard Earnshaw ; Richard Sandiford
>
> Subject: Re: [PATCH 03/22] arm: [MVE intrinsics] Rework vreinterpretq
>
>
>
>
> On 5/2/23 12:26, Kyrylo Tkacho
Hi!
During patch backporting, I've noticed that while most cp_walk_tree calls
with cp_fold_r callback callers were changed from &pset to cp_fold_data
&data, the VEC_INIT_EXPR gimplifications has not, so it still passes just
address of a hash_set and so if during the folding we ever touch
data->fla
On 5/2/23 11:18, Kyrylo Tkachov wrote:
Hi Christophe,
-Original Message-
From: Christophe Lyon
Sent: Tuesday, April 18, 2023 2:46 PM
To: gcc-patches@gcc.gnu.org; Kyrylo Tkachov ;
Richard Earnshaw ; Richard Sandiford
Cc: Christophe Lyon
Subject: [PATCH 00/22] arm: New framework for
When instrumentation is requested via -fsanitize-coverage=trace-pc, GCC
emits calls to __sanitizer_cov_trace_pc callback into each basic block.
This callback is supposed to be implemented by the user, and should be
able to identify the containing basic block by inspecting its return
address. Tailca
Hi Romain:
Pushed to trunk, thanks for catching that, that's definitely should
use log2 no matter C++03 or C++11,
but I think GCC allows the usage of C++11 according to
https://gcc.gnu.org/install/prerequisites.html :P
On Tue, May 2, 2023 at 8:22 PM Romain Naour via Gcc-patches
wrote:
>
> GCC s
The atomic fastpath bypasses the code that releases the sort
array which was lazily allocated during unwinding. We now
check after deregistering if there is an array to free.
libgcc/ChangeLog:
* unwind-dw2-fde.c: Free sort array in atomic fast path.
---
libgcc/unwind-dw2-fde.c | 6 ++
Hi Richard,
On Fri, 28 Apr 2023 at 14:41, Richard Biener via Gcc-patches <
gcc-patches@gcc.gnu.org> wrote:
> This adds a scatter vectorization capability to the vectorizer
> without target support by decomposing the offset and data vectors
> and then performing scalar stores in the order of vecto
> On May 2, 2023, at 9:18 AM, Roger Sayle wrote:
>
>
> On 02 May 2023 13:40, Paul Koning wrote:
>>> On May 1, 2023, at 7:37 PM, Roger Sayle
>> wrote:
>>>
>>> ...
>>> The shiftsi.cc regression on xstormy16 is fixed by adding
>>> -fno-split-wide-types.
>>> In fact, if all the regression tests
On Linux/x86_64,
e7ce7c4905fd254760b1cd187752a03bc0c148ba is the first bad commit
commit e7ce7c4905fd254760b1cd187752a03bc0c148ba
Author: Longjun Luo
Date: Sun Apr 30 12:28:06 2023 -0600
[PATCH] libcpp: suppress builtin macro redefined warnings for __LINE__
caused
FAIL: c-c++-common/cpp/
On 5/2/23 12:26, Kyrylo Tkachov wrote:
Hi Christophe,
-Original Message-
From: Christophe Lyon
Sent: Tuesday, April 18, 2023 2:46 PM
To:gcc-patches@gcc.gnu.org; Kyrylo Tkachov;
Richard Earnshaw; Richard Sandiford
Cc: Christophe Lyon
Subject: [PATCH 03/22] arm: [MVE intrinsics] Rework
Hi!
On Tue, May 02, 2023 at 02:18:43PM +0100, Roger Sayle wrote:
> On 02 May 2023 13:40, Paul Koning wrote:
> > > On May 1, 2023, at 7:37 PM, Roger Sayle
> > wrote:
> > > The shiftsi.cc regression on xstormy16 is fixed by adding
> > > -fno-split-wide-types.
> > > In fact, if all the regression te
May I please ping this one? Thanks...
https://gcc.gnu.org/pipermail/gcc-patches/2023-March/613247.html
On Thu, Mar 2, 2023 at 6:21 PM Lewis Hyatt wrote:
>
> The PR complains that we do not handle UTF-8 in the suffix for a user-defined
> literal, such as:
>
> bool operator ""_π (unsigned long long
On 02 May 2023 13:40, Paul Koning wrote:
> > On May 1, 2023, at 7:37 PM, Roger Sayle
> wrote:
> >
> > ...
> > The shiftsi.cc regression on xstormy16 is fixed by adding
> > -fno-split-wide-types.
> > In fact, if all the regression tests pass, I'd suggest that
> > flag_split_wide-types = false sho
Prathamesh Kulkarni writes:
> On Tue, 2 May 2023 at 17:32, Richard Sandiford
> wrote:
>>
>> Prathamesh Kulkarni writes:
>> > On Tue, 2 May 2023 at 14:56, Richard Sandiford
>> > wrote:
>> >> > [aarch64] Improve code-gen for vector initialization with single
>> >> > constant element.
>> >> >
>>
The PR109666 fix r14-386-g07c52d1eec967 incidentally also fixes this PR.
PR c++/109506
gcc/testsuite/ChangeLog:
* g++.dg/cpp0x/nsdmi-template26.C: New test.
---
gcc/testsuite/g++.dg/cpp0x/nsdmi-template26.C | 22 +++
1 file changed, 22 insertions(+)
create mode
> On May 1, 2023, at 7:37 PM, Roger Sayle wrote:
>
> ...
> The shiftsi.cc regression on xstormy16 is fixed by adding
> -fno-split-wide-types.
> In fact, if all the regression tests pass, I'd suggest that
> flag_split_wide-types = false
> should be the default on xstormy16 now that we've moved
On Tue, 2 May 2023 at 17:32, Richard Sandiford
wrote:
>
> Prathamesh Kulkarni writes:
> > On Tue, 2 May 2023 at 14:56, Richard Sandiford
> > wrote:
> >> > [aarch64] Improve code-gen for vector initialization with single
> >> > constant element.
> >> >
> >> > gcc/ChangeLog:
> >> > * config
gcc/ChangeLog:
* doc/invoke.texi: Update documentation based on param.opt file.
---
gcc/doc/invoke.texi | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 2f40c58b21c..b92b8576027 100644
--- a/gcc/doc/invoke
On 28/04/2023 17:54, Kyrylo Tkachov wrote:
-Original Message-
From: Andrea Corallo
Sent: Friday, April 28, 2023 12:30 PM
To: gcc-patches@gcc.gnu.org
Cc: Kyrylo Tkachov ; Richard Earnshaw
; Stam Markianos-Wright
Subject: [PATCH 09/10] arm testsuite: XFAIL or relax registers in some t
On Sun, Apr 30, 2023 at 11:14 PM Andrew Pinski via Gcc-patches
wrote:
>
> While looking at differences between what minmax_replacement
> and match_simplify_replacement does. I noticed that they sometimes
> chose different edges to remove. I decided we should be able to do
> better and be able to r
On Sun, Apr 30, 2023 at 11:14 PM Andrew Pinski via Gcc-patches
wrote:
>
> When I added diamond shaped form bb to match_simplify_replacement,
> I copied the code to move the statement rather than factoring it
> out to a new function. This does the refactoring to a new function
> to avoid the duplic
On Sun, Apr 30, 2023 at 11:13 PM Andrew Pinski via Gcc-patches
wrote:
>
> This ports the clrsb builtin part of builtin_zero_pattern
> to match.pd. A simple pattern to port.
>
> OK? Bootstrapped and tested on x86_64-linux-gnu with no regressions.
>
> gcc/ChangeLog:
>
> * match.pd (a != 0 ?
1 - 100 of 123 matches
Mail list logo
