Hi,
Gently ping it.
https://gcc.gnu.org/pipermail/gcc-patches/2024-May/653180.html
Thanks
Gui Haochen
在 2024/5/31 11:25, HAO CHEN GUI 写道:
> Hi,
> This patch optimizes vector construction with two vector doubleword loads.
> It generates an optimal insn sequence as "xxlor" has lower latency than
Some casts were missing leading to missed of bad vectorizations where
casting was done scalar followed by a vector creation from the
individual elements.
gcc/ChangeLog:
* config/s390/vector.md (VEC_HALF_NARROWED): New mode iterator.
(vec_half_narrowed): ditto.
(trunc2): Ne
The DIV instructions of MIPS won't be trapped themself if the divisor
is zero. The compiler will emit a conditional trap instruct for it.
So the signal will be SIGTRAP instead of SIGFPE.
gcc/testsuite
* c-c++-common/ubsan/overflow-div-3.c: Use SIGTRAP for MIPS.
---
gcc/testsuite/c-c++-co
If the address register is dead after load/store operation it looks
beneficial to use LDMIA/STMIA instead of pair of LDR/STR instructions,
at least if optimizing for size.
Changes v2 -> v3:
- switching to mixed approach (insn+peep2)
- keep memory attributes in peepholes
- handle stmia corner ca
Ping.
I fear that time to make GCC 11.5 is running out.
-Matthias
On Tuesday, 18 June 2024 08:22:13 GMT+2 Matthias Kretz wrote:
> Tested on x86_64-linux-gnu (also -m32 and -mx32), aarch64-linux-gnu, and
> arm- linux-gnueabi(hf).
>
> OK for trunk and backports? OK, to go for GCC 11.5 as early as
Hi!
Here is a version of the c_update_type_canonical fixes which passed
bootstrap/regtest.
The non-trivial part is the handling of the case when
build_qualified_type (TYPE_CANONICAL (t), TYPE_QUALS (x))
returns a type with NULL TYPE_CANONICAL. That should happen only
if TYPE_CANONICAL (t) == t, b
On Wed, 19 Jun 2024, Tamar Christina wrote:
> > -Original Message-
> > From: Richard Biener
> > Sent: Wednesday, June 19, 2024 12:55 PM
> > To: Tamar Christina
> > Cc: gcc-patches@gcc.gnu.org; nd ; bin.ch...@linux.alibaba.com
> > Subject: Re: [PATCH][ivopts]: use affine_tree when compari
On Wed, 19 Jun 2024, Tamar Christina wrote:
> > -Original Message-
> > From: Richard Biener
> > Sent: Wednesday, June 19, 2024 1:14 PM
> > To: Tamar Christina
> > Cc: gcc-patches@gcc.gnu.org; nd ; bin.ch...@linux.alibaba.com
> > Subject: Re: [PATCH][ivopts]: perform affine fold on unsign
HAO CHEN GUI writes:
> Hi,
> This patch replaces rtx_cost with insn_cost in forward propagation.
> In the PR, one constant vector should be propagated and replace a
> pseudo in a store insn if we know it's a duplicated constant vector.
> It reduces the insn cost but not rtx cost. In this case, t
Hi.
I came around to this, and whipped up the proposed patch. However, it
does seem a bit verbose, and I'm wondering if it's cleaner to just
leave things as they are.
The attached patch passes tests and there's no difference in
performance. I am wondering, whether it's better to get rid of
all/
Victor Do Nascimento writes:
> The introduction of the optional RCPC3 architectural extension for
> Armv8.2-A upwards provides additional support for the release
> consistency model, introducing the Load-Acquire RCpc Pair Ordered, and
> Store-Release Pair Ordered operations in the form of LDIAPP a
Hi Richard,
在 2024/6/20 16:05, Richard Sandiford 写道:
> I'm not sure "profitability" means much in the case of debug insns.
> There again, I suppose having no limit on the complexity of debug
> insns would risk quadraticness and (even without that) would tend
> to increase the size of the on-disk d
From: Piotr Trojanek
Recognize references to attributes Put_Image and Object_Size as
language-defined in Ada 2022 and implementation-defined in earlier
versions of Ada. Other attributes listed in Ada 2022 RM, K.2 and
currently implemented in GNAT are correctly categorized.
This change only affec
From: Steve Baird
In some cases, gnatprep would correctly emit an error message and then
incorrectly exit with a return code of zero, indicating success.
In some cases, a correct message about an error detected by the integrated
preprocessor would be accompanied by an incorrect message indicating
From: Viljar Indus
Previously this switch was emitting only info messages
which was both confusing in terms of the name of the
switch that was used internally and externally.
gcc/ada/
* doc/gnat_ugn/building_executable_programs_with_gnat.rst: Update
documentation for -gnatw.v.
From: Eric Botcazou
The Has_Controlled_Component flag is computed twice during freezing when
expansion is enabled: in Freeze_Array_Type and Expand_Freeze_Array_Type
for array types, and in Freeze_Record_Type and Expand_Freeze_Record_Type
for record types.
This removes the latter computation in b
From: Viljar Indus
There was a general concept of info messages being a subset of
warnings. However that is no longer the case. Messages with an
info insertion character should be treated just as info messages.
gcc/ada/
* atree.ads: Remove Warning_Info_Messages.
* errout.adb: Re
From: Viljar Indus
Previously the messages produced by this warning switch
were info messages that were suppressed with the same
methods as regular warnings. Since info messages are now
separated as a completely different class of messages then
these messages should be converted back to warnings
From: Viljar Indus
Add a separate switch -gnatis to suppress info messages
separately from warning messages that are controlled by
-gnatws.
gcc/ada/
* doc/gnat_ugn/building_executable_programs_with_gnat.rst: Add
entry for -gnatis.
* errout.adb (Error_Msg_Internal): Stop
From: Piotr Trojanek
Code cleanup; semantics is unaffected.
gcc/ada/
* freeze.adb (Find_Aspect_No_Parts): Tune whitespace.
* sem_ch13.adb (Check_Aspect_At_End_Of_Declarations): Fix style.
Tested on x86_64-pc-linux-gnu, committed on master.
---
gcc/ada/freeze.adb | 8 +++
From: Richard Kenner
gcc/ada/
* debug.adb: Add documentation for -gnatd_w.
Tested on x86_64-pc-linux-gnu, committed on master.
---
gcc/ada/debug.adb | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/gcc/ada/debug.adb b/gcc/ada/debug.adb
index 602a8fa0b63..97f88b76
From: Ronan Desplanques
The purpose of this patch is to make it possible to set up code
coverage for the GNAT front end in gnat1 using GNATcoverage. It is
not obvious how to have GNATcoverage instrument gnat1's main function,
and since the front end has a clear entry point (Gnat1drv), we add
manu
From: Eric Botcazou
gcc/ada/
* mutably_tagged.ads: Fix minor issues in comments throughout.
Tested on x86_64-pc-linux-gnu, committed on master.
---
gcc/ada/mutably_tagged.ads | 21 ++---
1 file changed, 10 insertions(+), 11 deletions(-)
diff --git a/gcc/ada/mutably_ta
From: Eric Botcazou
The Storage_Model pragma no longer exists.
gcc/ada/
* doc/gnat_rm/gnat_language_extensions.rst (Pragma Storage_Model):
Rename to Storage Model.
* doc/gnat_rm/implementation_defined_aspects.rst: Alphabetize.
* gnat_rm.texi: Regenerate.
From: Eric Botcazou
It's an assertion on the name of an instance of a generic child unit and
it needs to cope with a renaming of the unit.
gcc/ada/
* sem_ch12.adb (Instantiate_Formal_Package): Accept renamings of a
generic parent that is a child unit for the abbreviated instance
From: Eric Botcazou
The front-end maintains a set of 4 flags on (base) types that are used to
parameterize the implementation of controlled operations, and these flags
need to be propagated through composition and derivation. This is done
on a per-flag basis in the current implementation with a
From: Eric Botcazou
It was implemented apparently because a very early version of AI12-0164
that standardizes GNAT's Max_Queue_Length opted for the subtly different
moniker, but later versions of the AI use Max_Entry_Queue_Length instead.
gcc/ada/
* aspects.ads (Aspect_Id): Remove Aspec
From: Eric Botcazou
They are still tailored to Ada 95 while the level of recommended support for
Bit Ordering was changed in Ada 2005.
gcc/ada/
* doc/gnat_rm/implementation_advice.rst (Representation Clauses):
Remove >> marker and add end of sentence after code-block directive.
From: Eric Botcazou
The problem is that the freeze node of the type to which the real literal
is resolved is placed inside the expression function instead of outside.
gcc/ada/
* freeze.adb (Freeze_Expression): Also attach pending freeze nodes
to the parent in the case of an inte
From: Steve Baird
In some cases, a reduction expression that references the (nonexistent)
"+" operator of a generic formal private type is incorrectly accepted.
gcc/ada/
* sem_attr.adb (Resolve_Attribute.Proper_Op): When resolving the
name of the reducer subprogram in a reductio
From: Eric Botcazou
In Ada 2012, primitive equality operators of untagged record types compose
like those of tagged record types, but this has never been implemented for
untagged record types with a variant part.
gcc/ada/
* exp_ch4.adb (Expand_Composite_Equality): In the untagged record
From: Yannick Moy
Inlining in GNATprove may fail on a call to a subprogram with a formal
of an array type with fixed lower bound (a GNAT extension), because the
appropriate conversion is not used. Fix it.
Also fix the function that inserts an unchecked conversion, in cases where
it could skip sl
From: Piotr Trojanek
Code cleanup; behavior is unaffected.
gcc/ada/
* freeze.adb (Check_Current_Instance): This routine is only called
with parameter E being a type entity, so there is no need to check
for types just before the equality with E.
* sem_ch13.adb (An
From: Gary Dismukes
The compiler crashes on an instantiation of a generic child unit G1.GC
that has a formal private extension P_Ext of a private type P declared
in the parent G1 whose full type has a component C, when analyzing a
selected component ACC.C whose prefix is of an access type coming
From: Yannick Moy
SPARK RM 6.9(21) forbids a ghost type to have concurrent parts.
This was not enforced, instead only the type itself was checked to
be concurrent. Now fixed.
gcc/ada/
* ghost.adb (Check_Ghost_Type): Fix checking.
Tested on x86_64-pc-linux-gnu, committed on master.
---
From: Steve Baird
The argument to pragma Extensions_Allowed to enable all extensions is
no longer "All", but instead "All_Extensions".
gcc/ada/
* doc/gnat_rm/gnat_language_extensions.rst: Update documentation.
* doc/gnat_rm/implementation_defined_pragmas.rst: Update
docu
From: Bob Duff
...in preparation for implementing type inference for generic
parameters.
The main change is to do the "matching" computation early, and produce a
*constant* data structure (Gen_Assocs_Rec) to represent the matching
between each triple of unanalyzed formal, analyzed formal, and
co
From: Eric Botcazou
This was initially implemented as part of AI12-001 but immediately disabled
because it breaks Florist on 32-bit platforms. However, it is possible to
reenable it in almost all cases without affecting Florist, and the -gnatd_l
switch can now be used to disable it again.
gcc/a
From: Eric Botcazou
The code is legal and, therefore, must be accepted by the compiler, but it
must raise Program_Error at run time due to operands not having inferable
discriminants and a warning be given at compile time (RM B.3.3(22-23)).
gcc/ada/
* exp_ch4.adb (Expand_Array_Equality.
This patch deals with consequences but not the root cause though.
There are 5 cases which are subjects to rewrite:
case #1:
mov ip, r1
add r2, ip
# ip is dead here
can be rewritten as:
adds r2, r1
case #2:
add ip, r1
mov r1, ip
# ip is dead here
can be rewritten as:
add r1, ip
ca
LGTM.
juzhe.zh...@rivai.ai
From: demin.han
Date: 2024-06-20 11:28
To: gcc-patches
CC: juzhe.zhong; kito.cheng; pan2.li; jeffreyalaw; rdapp.gcc
Subject: [PATCH v2] RISC-V: Remove integer vector eqne pattern
We can unify eqne and other comparison operations.
Tested on RV32 and RV64.
gcc/Chan
Status
==
GCC 12.4 has been released and the branch is again open for regression
and documentation fixes.
Quality Data
Priority#Change from last report
------
P1 0
P2588- 31
P3 76- 1
On Thu, 20 Jun 2024, Aldy Hernandez wrote:
> Hi.
>
> I came around to this, and whipped up the proposed patch. However, it
> does seem a bit verbose, and I'm wondering if it's cleaner to just
> leave things as they are.
>
> The attached patch passes tests and there's no difference in
> performa
Hello Richard:
All review comments are incorporated.
Common infrastructure using generic code for pair mem fusion of different
targets.
rs6000 target specific code implement virtual functions defined by generic code.
Target specific code are added in rs6000-mem-fusion.cc.
Bootstrapped and regt
Status
==
The gcc-11 branch nears its retirement with the last release from it,
GCC 11.5, on the horizon.
Please look through bugzilla and see which of your regression fixes
for GCC 12 are also applicable for the GCC 11 branch and do the
necessary backporting. Please error on the safe side s
Hello Richard:
On 19/06/24 3:26 pm, Richard Sandiford wrote:
> Ajit Agarwal writes:
>> On 19/06/24 2:52 pm, Richard Sandiford wrote:
>>> Ajit Agarwal writes:
On 19/06/24 2:40 pm, Richard Sandiford wrote:
> Ajit Agarwal writes:
>> Hello Richard:
>>
>> On 19/06/24 1:54 pm, Ri
Hi Segher,
Following your review comments in [1], this patch is
separated from Xionghu's patch v4 [2] and mainly targetted
for 32-bit element size, it changes with the generic call
altivec_vmrg*w in vec_widen_[su]mult_{hi,lo}* expanders as
well. If this patch looks good to you, I'll post the othe
On Tue, 18 Jun 2024 at 07:22, Matthias Kretz wrote:
>
> Tested on x86_64-linux-gnu (also -m32 and -mx32), aarch64-linux-gnu, and arm-
> linux-gnueabi(hf).
>
> OK for trunk and backports? OK, to go for GCC 11.5 as early as possible?
OK for all branches, thanks.
>
> --- 8< ---
On Wed, Jun 19, 2024 at 5:04 AM Roger Sayle wrote:
>
>
> This patch tweaks ix86_ternlog_idx to allow any SUBREG that matches
> the register_operand predicate, and is split out as an independent
> piece of a patch that I have to clean-up redundant ternlog patterns
> in sse.md. It turns out that so
On Jun 19, 2024, "Richard Earnshaw (lists)" wrote:
> It looks like adding
> if ((unsigned)b[i] >= 8*sizeof (TYPE##BITS##_t)) \
> __builtin_unreachable(); \
Ah, yes, nice, good idea, thanks!
Here's the patch that implements that, co-attributed to you, as IMHO
On Thu, 20 Jun 2024, YunQiang Su wrote:
> The DIV instructions of MIPS won't be trapped themself if the divisor
> is zero. The compiler will emit a conditional trap instruct for it.
> So the signal will be SIGTRAP instead of SIGFPE.
It's an OS kernel bug if you get SIGTRAP for integer division
On Thu, Jun 20, 2024 at 12:57 PM Maciej W. Rozycki wrote:
>
> On Thu, 20 Jun 2024, YunQiang Su wrote:
>
> > The DIV instructions of MIPS won't be trapped themself if the divisor
> > is zero. The compiler will emit a conditional trap instruct for it.
> > So the signal will be SIGTRAP instead of SI
This version differs by using INCLUDE_STRING instead of .
(+whitespace and year)
___
This patch implements lockfile used for incremental LTO.
Bootstrapped/regtested on x86_64-pc-linux-gnu
gcc/ChangeLog:
* Makefile.in: Add lockfile.o.
* lockfile.cc: New file.
* lockfile.
> >else if (ret_elt_bits > arg_elt_bits)
> > modifier = WIDEN;
> >
> > + if (supportable_convert_operation (code, ret_type, arg_type, &code1))
> > +{
> > + g = gimple_build_assign (lhs, code1, arg);
> > + gsi_replace (gsi, g, false);
> > + return;
> > +}
>
> Given
Added the following hint on testing for target avr.
Johann
--
diff --git a/htdocs/simtest-howto.html b/htdocs/simtest-howto.html
index 3afbdb0b..ea69c9ed 100644
--- a/htdocs/simtest-howto.html
+++ b/htdocs/simtest-howto.html
@@ -304,5 +304,22 @@ to exercise the just-built gcc on every test-sui
cc0 has been removed long ago, removed mentions.
Johann
diff --git a/htdocs/simtest-howto.html b/htdocs/simtest-howto.html
index ea69c9ed..f18a78f6 100644
--- a/htdocs/simtest-howto.html
+++ b/htdocs/simtest-howto.html
@@ -164,13 +164,7 @@ to exercise the just-built gcc on every test-suite
in t
Outside of suggested changes, this version:
- uses #define INCLUDE_*
- is rebased onto current trunk - 'fprintf (mstream,' lines
- --verbose 'recompiling++' count is moved into correct if branch
___
This patch implements Incremental LTO as ltrans cache.
The cache is active when directory $GCC_LT
On Thu, Jun 20, 2024 at 7:47 AM Feng Xue OS wrote:
>
> >> + if (lane_reducing_op_p (op.code))
> >> + {
> >> + unsigned group_size = slp_node ? SLP_TREE_LANES (slp_node) :
> >> 0;
> >> + tree op_type = TREE_TYPE (op.ops[0]);
> >> + tree new_vec
Hi,
On Thu, 20 Jun 2024 at 12:51, Alexandre Oliva wrote:
>
> On Jun 19, 2024, "Richard Earnshaw (lists)" wrote:
>
> > It looks like adding
>
> > if ((unsigned)b[i] >= 8*sizeof (TYPE##BITS##_t)) \
> > __builtin_unreachable(); \
>
> Ah, yes, nice, good idea, than
On Sun, Jun 16, 2024 at 9:31 AM Feng Xue OS wrote:
>
> For lane-reducing operation(dot-prod/widen-sum/sad) in loop reduction, current
> vectorizer could only handle the pattern if the reduction chain does not
> contain other operation, no matter the other is normal or lane-reducing.
>
> Actually,
On Thu, 20 Jun 2024, Michal Jires wrote:
> This version differs by using INCLUDE_STRING instead of .
> (+whitespace and year)
OK (though I'm not happy to see more std::string use)
Richard.
> ___
>
> This patch implements lockfile used for incremental LTO.
>
> Bootstrapped/regtested on x86_64-
On Thu, Jun 20, 2024 at 1:32 PM Georg-Johann Lay wrote:
>
> cc0 has been removed long ago, removed mentions.
OK
> Johann
>
> diff --git a/htdocs/simtest-howto.html b/htdocs/simtest-howto.html
> index ea69c9ed..f18a78f6 100644
> --- a/htdocs/simtest-howto.html
> +++ b/htdocs/simtest-howto.html
>
This series is a resubmission of the late-combine work. I've fixed
some bugs that Jeff's cross-target CI found last time and some others
that I hit since then.
I've also removed a source of quadraticness (oops!). Doing that
in turn drove some tweaks to the rtl-ssa scan routines.
The complexity
No-op moves are given the code NOOP_MOVE_INSN_CODE if we plan
to delete them later. Such insns shouldn't be costed, partly
because they're going to disappear, and partly because targets
won't recognise the insn code.
gcc/
* rtl-ssa/changes.cc (rtl_ssa::changes_are_worthwhile): Don't
*minus_plus_one had no constraints, which meant that it could be
matched after RA with operands 0, 1 and 2 all being different.
The associated split instead requires operand 0 to be tied to
operand 1.
gcc/
* config/sh/sh.md (*minus_plus_one): Add constraints.
---
gcc/config/sh/sh.md | 6 +
All uses of xs_hi_nonmemory_operand allow constraint "i",
which means that they allow consts, symbol_refs and label_refs.
The definition of xs_hi_nonmemory_operand accounted for consts,
but not for symbol_refs and label_refs.
gcc/
* config/stormy16/predicates.md (xs_hi_nonmemory_operand):
The iq2000 test and branch instructions had patterns like:
[(set (pc)
(if_then_else
(eq (and:SI (match_operand:SI 0 "register_operand" "r")
(match_operand:SI 1 "power_of_2_operand" "I"))
(const_int 0))
(match_operand 2 "pc_or_label_ope
This patch adds a combine pass that runs late in the pipeline.
There are two instances: one between combine and split1, and one
after postreload.
The pass currently has a single objective: remove definitions by
substituting into all uses. The pre-RA version tries to restrict
itself to cases that
rtl-ssa has routines for scanning forwards or backwards for something
under the control of an exclusion set. These searches are currently
used for two main things:
- to work out where an instruction can be moved within its EBB
- to work out whether recog can add a new hard register clobber
The e
On Thu, 20 Jun 2024, Richard Biener wrote:
> > > The DIV instructions of MIPS won't be trapped themself if the divisor
> > > is zero. The compiler will emit a conditional trap instruct for it.
> > > So the signal will be SIGTRAP instead of SIGFPE.
> >
> > It's an OS kernel bug if you get SIGTRAP
On 6/20/24 05:31, Richard Biener wrote:
On Thu, 20 Jun 2024, Aldy Hernandez wrote:
Hi.
I came around to this, and whipped up the proposed patch. However, it
does seem a bit verbose, and I'm wondering if it's cleaner to just
leave things as they are.
The attached patch passes tests and ther
On Thu, Jun 13, 2024 at 03:16:44PM +0800, Kewen.Lin wrote:
> Hi,
>
> Gentle ping:
>
> https://gcc.gnu.org/pipermail/gcc-patches/2024-June/653363.html
Hello since this is a treewide update I am not the best person to approve just
this single patch. But it does look good to me as this is what you
> Am 20.06.2024 um 16:05 schrieb Andrew MacLeod :
>
>
>> On 6/20/24 05:31, Richard Biener wrote:
>>> On Thu, 20 Jun 2024, Aldy Hernandez wrote:
>>>
>>> Hi.
>>>
>>> I came around to this, and whipped up the proposed patch. However, it
>>> does seem a bit verbose, and I'm wondering if it's c
This unfortunately means we can never increase __cpp_lib_chrono again
for the old string ABI, but I don't see any alternative (except
supporting chrono::tzdb for the old string, which will be a lot of work
that I don't want to do!)
-- >8 --
The header is incomplete for the old std::string ABI, b
I think the new conditions are correct. They're certainly an improvment
on just checking __is_scalar without considering what we're assigning it
to.
Tested x86_64-linux.
-- >8 --
As noted in the PR, the optimization used for scalar types in std::fill
and std::fill_n is non-conforming, because it
We know that valarray's value_type must be DefaultConstructible, so we
don't need to test that. I think __is_trivial is sufficient to tell us
we can use memset to value-initialize the elements.
Tested x86_64-linux.
-- >8 --
This removes the use of the std::__is_scalar trait from ,
where it can b
We still have __is_arithmetic in after this,
but that needs a lot more work to remove its uses from and
.
Tested x86_64-linux.
-- >8 --
This removes the std::__is_pointer and std::__is_scalar traits, as they
conflicts with a Clang built-in.
Although Clang has a hack to make the class template
Tested x86_64-linux.
-- >8 --
This removes the std::__is_void trait, as it conflicts with a Clang
built-in. There is only one use of the trait, which can easily be
replaced by simpler code.
Although Clang has a hack to make the class template work despite using
a reserved name, removing std::__i
Tested x86_64-linux.
-- >8 --
This replaces all uses of the std::__is_pointer type trait with uses of
the new __is_pointer built-in. Since the class template was only used to
enable some performance optimizations for algorithms, we can use the
built-in when __has_builtin(__is_pointer) is true (wh
Tested x86_64-linux.
-- >8 --
Dispatching to partial specializations doesn't really seem to offer much
benefit here. The __is_trivial(T) condition is a compile-time constant
so the untaken branches are dead code and don't cost us anything.
libstdc++-v3/ChangeLog:
* include/bits/valarray
Tested x86_64-linux.
-- >8 --
This member function was previously deprecated, but that was reverted by
P2875R4, approved earlier this year in Tokyo. Since it's not going to be
deprecated in C++26, and so presumably not removed, there is no point in
giving deprecated warnings for C++23 mode.
libs
Tested x86_64-linux.
-- >8 --
These tests compile very slowly in debug mode.
libstdc++-v3/ChangeLog:
PR libstdc++/90276
* testsuite/25_algorithms/pstl/alg_modifying_operations/rotate_copy.cc:
Increase timeout for debug mode.
*
testsuite/25_algorithms/pstl/alg_mo
Tested x86_64-linux.
-- >8 --
LWG 3305 was approved earlier this year in Tokyo. We need to give an
error if using std::any_cast, but std::any_cast is valid
(but always returns null).
libstdc++-v3/ChangeLog:
* include/std/any (any_cast(any*), any_cast(const any*)): Add
static ass
Tested x86_64-linux.
-- >8 --
These were deprecated in C++17 and std::wstring_convert is planned for
removal in C++26.
libstdc++-v3/ChangeLog:
* include/bits/locale_conv.h (wstring_convert): Add deprecated
attribute for C++17 and later.
(wbuffer_convert): Likewise.
Tested x86_64-linux.
-- >8 --
This addresses one known failure due to a bug in the upstream tests, and
a number of timeouts due to the algorithms running much more slowly with
debug mode checks enabled.
libstdc++-v3/ChangeLog:
PR libstdc++/90276
* testsuite/25_algorithms/pstl/al
Tested x86_64-linux.
-- >8 --
libstdc++-v3/ChangeLog:
* include/backward/backward_warning.h: Adjust comments to
suggest as another alternative to .
* include/backward/strstream (strstreambuf, istrstream)
(ostrstream, strstream): Add deprecated attribute.
---
...
On Thu, Jun 20, 2024 at 09:06:11AM +0200, Juergen Christ wrote:
> Some casts were missing leading to missed of bad vectorizations where
> casting was done scalar followed by a vector creation from the
> individual elements.
>
> gcc/ChangeLog:
>
> * config/s390/vector.md (VEC_HALF_NARROWED):
This introduces testsuite support infra for removing extensions.
Since z* extensions don't have ordering requirements the logic for
adding/removing those extensions has also been consolidated.
This fixes RVWMO compile testcases failing on Ztso targets by removing
the extension from the -march stri
Hi!
On Wed, Jun 19, 2024 at 08:29:37PM +0200, Jakub Jelinek wrote:
> Right now the patch only supports a single huge string literal in there,
> not concatenation of multiple strings, dunno if we shouldn't add support
> for that so that we don't run into the line length limits for column
> numberin
> Am 20.06.2024 um 17:40 schrieb Stefan Schulze Frielinghaus
> :
>
> On Thu, Jun 20, 2024 at 09:06:11AM +0200, Juergen Christ wrote:
>> Some casts were missing leading to missed of bad vectorizations where
>> casting was done scalar followed by a vector creation from the
>> individual element
Hi!
On Thu, Jun 20, 2024 at 06:22:07PM +0800, Kewen.Lin wrote:
> Following your review comments in [1], this patch is
> separated from Xionghu's patch v4 [2] and mainly targetted
> for 32-bit element size, it changes with the generic call
> altivec_vmrg*w in vec_widen_[su]mult_{hi,lo}* expanders a
Michal Jires writes:
No performance data?
> +
> +static const md5_checksum_t INVALID_CHECKSUM = {
> + 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
> +};
There are much faster/optimized modern hashes for good collision detection over
MD5 especially when it's not needed to be cryptographicall
Andi Kleen writes:
PING^3 for the musttail patchkit at
https://gcc.gnu.org/pipermail/gcc-patches/2024-June/653319.html
(except the C++ patch which got approved)
Thanks!
-Andi
> Andi Kleen writes:
>
> PING^2
>
>> Need reviewers for the tree and middle-end parts, as well as the C frontend.
>>
Richard Biener writes:
> On Mon, 17 Jun 2024, Richard Sandiford wrote:
>
>> Richard Biener writes:
>> > On Fri, 14 Jun 2024, Richard Biener wrote:
>> >
>> >> On Fri, 14 Jun 2024, Richard Sandiford wrote:
>> >>
>> >> > Richard Biener writes:
>> >> > > On Fri, 14 Jun 2024, Richard Sandiford wrote
Use INT_MIN rather than -1 in `comparison_qty' where a comparison is not
with a register, because the value of -1 is actually a valid reference
to register 0 in the case where it has not been assigned a quantity.
Using -1 makes `REG_QTY (REGNO (folded_arg1)) == ent->comparison_qty'
comparison
On Sun, 24 Oct 2004, Roger Sayle wrote:
> It's a long story...
And now even longer...
> However, David Anglin suggested an alternate strategy of subtracting
> max_reg from the stored quantity values themselves. Elaborating on
> that theme, the patch below reorganizes the encoding used for quan
On Thu, 20 Jun 2024, Jakub Jelinek wrote:
> 2024-06-19 Jakub Jelinek
> Martin Uecker
>
> PR c/114930
> PR c/115502
> gcc/c/
> * c-decl.cc (c_update_type_canonical): Assert t is main variant
> with 0 TYPE_QUALS. Simplify and don't use check_qualified_type.
>
On Linux/x86_64,
9a76db24e044c8058497051a652cca4228cbc8e9 is the first bad commit
commit 9a76db24e044c8058497051a652cca4228cbc8e9
Author: Roger Sayle
Date: Thu Jun 20 16:30:15 2024 +0100
i386: Allow all register_operand SUBREGs in x86_ternlog_idx.
caused
FAIL: gcc.target/i386/pr89984-2.c
Hi Richard,
I had a quick look through the patch and noticed a couple of minor typos.
Otherwise looks like a nice cleanup!
On 20/06/2024 14:34, Richard Sandiford wrote:
> rtl-ssa has routines for scanning forwards or backwards for something
> under the control of an exclusion set. These searches
Last patch in this round of bitmanip work... At least I think I'm going
to pause here and switch gears to other projects that need attention :-)
This patch introduces the ability to generate bitmanip instructions for
rv64 when operating on SI objects when we know something about the range
of
1 - 100 of 124 matches
Mail list logo
