Bootstrapped and Regtested on x86_64-linux-gnu{-m32,-m64}, OK for trunk?
BRs,
Lin
> -Original Message-
> From: Hu, Lin1
> Sent: Friday, March 28, 2025 1:55 PM
> To: gcc-patches@gcc.gnu.org
> Cc: Liu, Hongtao ; ubiz...@gmail.com; Wang, Hongyu
>
> Subject: [PATCH] i386: Add attr_isa for v
For vaes patterns with jm constraint and gpr16 attr, it requires "isa"
attr to distinct avx/avx512 alternatives in ix86_memory_address_reg_class.
Also adds missing type and mode attributes for those vaes patterns.
gcc/ChangeLog:
PR target/119473
* config/i386/sse.md
(vaesd
On Mar 27, 2025, Jakub Jelinek wrote:
> Here is a fix, tested on x86_64-linux, ok for trunk?
> 2025-03-27 Jakub Jelinek
> * g++.dg/strub-internal-pr112938.C: Add dg-warning for c++20.
LGTM, thanks
--
Alexandre Oliva, happy hackerhttps://blog.lx.oliva.nom.br/
Free Softwar
From: Arthur Cohen
Regression checks for Rust-GCC#1399
gcc/testsuite/ChangeLog:
* rust/compile/multiline-string.rs: New test.
* rust/execute/torture/multiline-string.rs: New test.
---
gcc/testsuite/rust/compile/multiline-string.rs| 14 ++
.../rust/execute/tortur
From: Arthur Cohen
gcc/testsuite/ChangeLog:
* rust/compile/derive_macro4.rs: Make PhantomData a lang item.
---
gcc/testsuite/rust/compile/derive_macro4.rs | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/gcc/testsuite/rust/compile/derive_macro4.rs
b/gcc/testsuite
On Fri, Mar 21, 2025 at 08:25:10PM +0100, Richard Biener wrote:
> > --- gcc/cobol/parse.y.jj2025-03-21 17:49:43.571440176 +0100
> > +++ gcc/cobol/parse.y 2025-03-21 20:15:24.852414777 +0100
> > @@ -4331,7 +4331,8 @@ value_clause: VALUE all LITERAL[lit] {
> >cbl_field
>> > diff --git a/gcc/testsuite/g++.dg/tree-ssa/pr80331.C
>> > b/gcc/testsuite/g++.dg/tree-ssa/pr80331.C
>> > new file mode 100644
>> > index 000..85034504f2f
>> > --- /dev/null
>> > +++ b/gcc/testsuite/g++.dg/tree-ssa/pr80331.C
>> > @@ -0,0 +1,8 @@
>> > +// { dg-do compile }
>> > +// {
I believe these don't get detected by DejaGnu's regexp.
Found by dg-lint.
Pushed to trunk as r15-8994-g1ee9caf2f84832.
libstdc++-v3/ChangeLog:
* testsuite/17_intro/shared_with_static_deps.cc: Fix malformed
dg-require-static-libstdcxx directive.
* testsuite/17_intro/static
Pushed to trunk as r15-8993-gc88abca94a6abb.
gcc/testsuite/ChangeLog:
* g++.dg/abi/pure-virtual1.C: Fix dg-require-weak directive.
* g++.target/i386/mangling-alias1.C: Fix dg-require-ifunc
directive.
---
gcc/testsuite/g++.dg/abi/pure-virtual1.C| 2 +-
gcc/testsuite
On 3/20/25 9:20 AM, Andre Vehreschild wrote:
Hi all,
attached patch fixes a 15-regression where an element of an actual
temporary array, i.e., elemental([ e1, e2...]) passed to the formal polymorphic
dummy leads to a double free of the derived types components. This patch
prevents this by preven
From: Arthur Cohen
gcc/rust/ChangeLog:
* expand/rust-derive-copy.cc: Use new LangItemPath for derive(Copy).
---
gcc/rust/expand/rust-derive-copy.cc | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/gcc/rust/expand/rust-derive-copy.cc
b/gcc/rust/expand/rust-deriv
From: Philip Herron
Fixes Rust-GCC#3229
gcc/rust/ChangeLog:
* rust-gcc.cc (operator_to_tree_code): ! expressions are BIT_NOT_EXPR
Signed-off-by: Philip Herron
---
gcc/rust/rust-gcc.cc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/rust/rust-gcc.cc b/gcc/rust/
From: Owen Avery
gcc/rust/ChangeLog:
* ast/rust-ast-visitor.cc
(DefaultASTVisitor::visit): Visit fields of InlineAsm.
gcc/testsuite/ChangeLog:
* rust/compile/nr2/exclude: Remove
inline_asm_parse_output_operand.rs.
Signed-off-by: Owen Avery
---
gcc/rust/ast/ru
Given that this is all below "contrib", I've taken the liberty of
pushing this updated version to trunk, as r15-8992-g8d6de758cca6d1.
Changed in v2:
- eliminated COMMON_MISSPELLINGS in favor of retesting with a regexp
that adds underscores
- add a list of KNOWN_DIRECTIVES, and complain if we see
This patch fixes both 119471 and the remainder of 110992.
At issue is we do not recognize that if
"a * b != 0" , then neither "a" nor "b" can be zero.
This is fairly trivial with range-ops. op1_range and op2_range for
operator_mult are taught that if the LHS does not contain zero, than
ne
~90 new DRs. More updates tomorrow.
Pushed.
-- >8 --
commit eabbf82b95871f4cc1561b9d5bd9ba88a849a61f
Author: Marek Polacek
Date: Thu Mar 27 19:08:35 2025 -0400
cxx-dr-status: Update from C++ Core Language Issue TOC, Revision 116
diff --git a/htdocs/projects/cxx-dr-status.html
b/htdocs/
I've spent more than my fair share of my life fiddling with autoconf
installations, so I just hand-editted the patches to elide the
unwanted changes.
Now committed on both trunk and releases/14.
Thanks,
Roland
Hi Paul-Antoine,
This pattern enables the combine pass to merge a vec_duplicate into a plus-mult
or minus-mult RTL instruction.
Before this patch, we have two instructions, e.g.:
vfmv.v.fv6,fa0
vfmadd.vv v9,v6,v7
After, we get only one:
vfmadd.vf v9,fa0,v7
On SPEC201
This is the initial group of testcases programmatically converted from the
autom4te UAT tests in the cobolworx repository.
These tests behave as intended on an x86_64-linux platform.
>From c8d32f79a27e034979f838e7f611cb4ea049639f Mon Sep 17 00:00:00 2001
From: Bob Dubner
Date: Thu, 27 Mar 2025 1
On Thu, Mar 27, 2025 at 09:28:31PM +0100, Uros Bizjak wrote:
> plus_constant expects integer as its third argument, not rtx.
>
> gcc/ChangeLog:
>
> * config/i386/i386.cc (ix86_redzone_clobber): Use integer, not rtx
> as the third argument of plus_constant.
Oops, thanks for catching this.
Hi Jakub, all,
Am 27.03.25 um 20:04 schrieb Jakub Jelinek:
On Thu, Mar 27, 2025 at 07:34:14PM +0100, Jakub Jelinek wrote:
The following patch runs the test only in the -O3 -g case (just using -O3
there would run it twice, once with
-O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -
On Thu, 27 Mar 2025 09:33:40 +
Iain Sandoe wrote:
> As noted in the commit log, the macOS version of cmath (at least) has
> conflicts with parse.y. Tested on x86_64,aarch64 linux,
> x86_64-darwin. OK for trunk?
> thanks,
> Iain
LGTM, Iain. Any header file that isn't needed, isn't needed.
On Wed, Mar 19, 2025 at 12:00:00PM -0400, Jason Merrill wrote:
> On 3/17/25 6:55 PM, Marek Polacek wrote:
> > Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
> >
> > -- >8 --
> > We crash while we call warning_at ("inline function used but never defined")
> > since it invokes dump_tem
plus_constant expects integer as its third argument, not rtx.
gcc/ChangeLog:
* config/i386/i386.cc (ix86_redzone_clobber): Use integer, not rtx
as the third argument of plus_constant.
Bootstrapped and regression tested on x86_64-pc-linux-gnu {,-m32}.
Uros.
diff --git a/gcc/config/i386/i
On Mar 27, 2025, at 12:29 PM, Jakub Jelinek wrote:
>
> On Thu, Mar 27, 2025 at 12:05:21AM +, Sam James wrote:
>> The test was being ignored because dg.exp looks for .C in g++.dg/.
>>
>> gcc/testsuite/ChangeLog:
>> PR middle-end/112938
>>
>> * g++.dg/strub-internal-pr112938.cc: Mov
On Thu, Mar 27, 2025 at 12:05:21AM +, Sam James wrote:
> The test was being ignored because dg.exp looks for .C in g++.dg/.
>
> gcc/testsuite/ChangeLog:
> PR middle-end/112938
>
> * g++.dg/strub-internal-pr112938.cc: Move to...
> * g++.dg/strub-internal-pr112938.C: ...here.
The Tasking_Runtime_Initialize routine installs the tasking version of the
RTS_Lock manipulation routines and thus needs to be called very early before
the elaboration of all the Ada units of the program, including those of the
runtime itself.
This is guaranteed by the binder when the tasking r
On Mar 26, 2025, at 11:34 AM, David Malcolm wrote:
>
> This patch kit:
> * adds minimal Python bindings for libgdiagnostics.so (below contrib)
> * implements a new dg-lint tool (below contrib) to detect for
>common mistakes in our testsuite, using Python 3 (and the above
>bindings)
> *
Hi!
The following (first) testcase is accepted by clang (if clang::musttail)
and rejected by gcc, because we discover the call is noreturn and then bail
out because we don't want noreturn tailcalls.
The general reason not to support noreturn tail calls is for cases like
abort where we want nicer b
On Mar 20, 2025, at 8:11 AM, Alex Coplan wrote:
> On 09/02/2024 15:32, Alex Coplan wrote:
>> On 04/05/2022 09:59, Martin Liška wrote:
>>> Supports change in libsanitizer where it newly reports:
>>> READ of size 4 at 0xc3d4 tags: 02/01(00) (ptr/mem) in thread T0
>>>
>>> So the 'tags' conta
Hi!
The following testcase is rejected, because IPA-SRA decides to
turn bar.constprop call into bar.constprop.isra which returns void.
While there is no explicit lhs on the call, as it is a musttail call
the tailc pass checks if IPA-VRP returns singleton from that function
and the function returns
This patch backports the ASSUME support that was rewritten in GCC 15.
Its slightly more complicated than the port to GCC 14 was in that a few
classes have been rewritten. I've isolated them all to tree-assume.cc
which contains the pass.
It has to also bring in the ssa_cache and lazy_ssa_cache
On Thu, Mar 27, 2025 at 07:34:14PM +0100, Jakub Jelinek wrote:
> The following patch runs the test only in the -O3 -g case (just using -O3
> there would run it twice, once with
> -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer
> -finline-functions
> and once with
> -O3 -g
>
> The -O
Tested x86_64-pc-linux-gnu, applying to trunk.
-- >8 --
gcc/testsuite/ChangeLog:
* g++.dg/template/explicit-args6.C: Remove an extra set of {} in
a dg-message.
---
gcc/testsuite/g++.dg/template/explicit-args6.C | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/g
On Thu, Mar 27, 2025 at 06:11:25PM +, Sam James wrote:
> >> diff --git a/gcc/testsuite/gfortran.dg/cray_pointers_2.f90
> >> b/gcc/testsuite/gfortran.dg/cray_pointers_2.f90
> >> index 4351874825ed..a7e15bad850a 100644
> >> --- a/gcc/testsuite/gfortran.dg/cray_pointers_2.f90
> >> +++ b/gcc/tests
From: Arthur Cohen
gcc/rust/ChangeLog:
* ast/rust-ast-collector.cc (TokenCollector::visit): Visit tuple
pattern items as
separated by commas.
---
gcc/rust/ast/rust-ast-collector.cc | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/gcc/rust/ast/rust-ast-col
The tests call sigsetjmp and use sigjmp_buf type. Thus the tests
cannot be compiled on baremetal newlib targets which do not have
sigsetjmp.
Pushed to trunk as obvious.
gcc/testsuite/ChangeLog:
* gcc.misc-tests/gcov-31.c: Require effective target sigsetjmp.
* gcc.misc-tests/gcov
On Wed, 26 Mar 2025, Roland McGrath wrote:
> The libcpp code uses `#ifdef HAVE_SETLOCALE` but its configure doesn't
> have the corresponding check.
>
> Ok for trunk and 14 branch?
OK, but watch out for what look like spurious changes in the generated
configure (maybe resulting from a patched au
On Wed, Mar 26, 2025 at 05:57:51PM +, Jonathan Wakely wrote:
> On Wed, 26 Mar 2025 at 17:42, Jason Merrill wrote:
> >
> > On 3/26/25 6:14 AM, Jonathan Wakely wrote:
> > > My r15-8904-ge200f53a555651 changed the std::vector initializer-list
> > > constructor so that it calls a new _M_range_init
Harald Anlauf writes:
> Sam,
>
> who approved the fortran testsuite changes?
We've been doing them as obvious by consensus since last year. I'm sorry
for the error.
>
> Am 27.03.25 um 14:28 schrieb Sam James:
>> These just fix inconsistent/unusual style to avoid noise when grepping
>> and also
Marek Polacek writes:
> On Thu, Mar 27, 2025 at 12:38:55AM +, Sam James wrote:
>> A handful of cosmetic ones in here but most meant the directive wasn't
>> doing anything.
>
> This patch breaks g++.dg/template/explicit-args6.C for me.
See PR119490. I can XFAIL it, but I think it may be a rea
On Thu, Mar 27, 2025 at 12:38:55AM +, Sam James wrote:
> A handful of cosmetic ones in here but most meant the directive wasn't
> doing anything.
This patch breaks g++.dg/template/explicit-args6.C for me.
> gcc/testsuite/ChangeLog:
>
> * g++.dg/cpp0x/udlit-namespace-ambiguous.C: Fix w
When the dg brackets were added, they forgot to add the brackets for the
scan-assembler-times directive.
Committed as obvious.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vls/merge-4.c: Fix typo
Signed-off-by: Edwin Lu
---
gcc/testsuite/gcc.target/riscv/rvv/autovec/vls/mer
Revert part of my change from r15-8973-g1307de1b4e7d5e; as Harald points
out, the comment explains why this is there. It's a hack but it needs to
stay for now. (I did have this marked as a TODO in my branch and didn't
leave a proper note as to why, so it's my fault.)
gcc/testsuite/ChangeLog:
Sam,
who approved the fortran testsuite changes?
Am 27.03.25 um 14:28 schrieb Sam James:
These just fix inconsistent/unusual style to avoid noise when grepping
and also people picking up bad habits when they see it (as similar
mistakes can be harmful).
This one should be reverted. The reason
From: badumbatish
gcc/rust/ChangeLog:
* backend/rust-compile-asm.cc (CompileAsm::add_stmt):
Deleted
(CompileAsm::CompileAsm):
Successfully produce pseudo-nop
(CompileAsm::visit): Likewise
(CompileAsm::asm_build_asm_stmt): Likewise
(CompileA
Hi all,
attached patch fixes freeing of procedure pointers that are stored in a derived
type's component. GFortran did that already for polymorphic types but missed
out on the others.
Regtested ok on x86_64-pc-linux-gnu / F41. Ok for mainline?
Regards,
Andre
--
Andre Vehreschild * Email:
This pattern enables the combine pass to merge a vec_duplicate into a plus-mult
or minus-mult RTL instruction.
Before this patch, we have two instructions, e.g.:
vfmv.v.fv6,fa0
vfmadd.vv v9,v6,v7
After, we get only one:
vfmadd.vf v9,fa0,v7
On SPEC2017's 503.bwaves_r, de
On 3/27/25 10:11, Paul-Antoine Arras wrote:
I updated the patch (see attachment) with that in mind. Let me know what
you think.
I know that very long
"BT_FN_VOID_INT_INT_PTRCONSTPTRPTR_CONSTPTR_PTRCONSTSTRING..."
identifier follows the conventions used elsewhere, but it's not very
readable,
This patch introduces the TARGET_REJECT_FUNCTION_CLONE_VERSION hook
which is used to determine if a target_clones version string parses.
If true is returned, a warning is emitted and from then on the version
is ignored.
This is as specified in the Arm C Language Extension. The purpose of this
is
> "Richard" == Richard Biener writes:
Sorry about the delay on this.
>> - mod_type_die = subrange_type_die (type, low, high, bias, context_die);
>> + mod_type_die = subrange_type_die (type, low, high, bias, mod_scope);
Richard> that looks good. But why not for the ARRAY_TYPE case
On Thu, Mar 27, 2025 at 12:20 PM Jonathan Wakely wrote:
> Import the new 2025b tzdata.zi file.
>
> libstdc++-v3/ChangeLog:
>
> * src/c++20/tzdata.zi: Import new file from 2025b release.
> ---
>
> A much smaller change for 2025b, and no update to the leapseconds file.
>
LGTM
>
> Tested x8
This patch is an overhaul of how FMV name mangling works. Previously
mangling logic was duplicated in several places across both target
specific and independent code. This patch changes this such that all
mangling is done in targetm.mangle_decl_assembler_name (including for the
dispatched symbol a
From: Philip Herron
Negative polarity means we can just ignore if any trait items are not
implemented.
Fxies #3030
gcc/rust/ChangeLog:
* hir/rust-ast-lower-item.cc (ASTLoweringItem::visit): the polarity was
reversed
* typecheck/rust-hir-type-check-item.cc: check the polarity
Yeoul,
Thanks for the writeup.
So, basically, This writeup insisted on introducing a new “structure scope”
(similar as the instance scope in C++) into C language ONLY for counted_by
attribute:
1. Inside counted_by attribute, the name lookup starts:
A. Inside the current structure first (t
This changes function version structures to maintain the default version
as the first declaration in the linked data structures by giving priority
to the set containing the default when constructing the structure.
This allows for removing logic for moving the default to the first
position which w
gcc/ChangeLog:
* attribs.cc (make_attribute): Change arguments.
* attribs.h (make_attribute): Change arguments.
---
gcc/attribs.cc | 18 ++
gcc/attribs.h | 2 +-
2 files changed, 7 insertions(+), 13 deletions(-)
diff --git a/gcc/attribs.cc b/gcc/attribs.cc
inde
On 25/03/2025 18:55, Sandra Loosemore wrote:
On 3/25/25 09:25, Paul-Antoine Arras wrote:
On 24/03/2025 21:17, Sandra Loosemore wrote:
[snip]
Besides, I am not sure how to encode complex types like (**const *).
Does that require creating new definitions in gcc/builtin-types.def
and gcc/fortran/
This is for testing the x86 mangling of FMV versioned function
assembly names.
gcc/testsuite/ChangeLog:
* g++.target/i386/mv-symbols1.C: New test.
* g++.target/i386/mv-symbols2.C: New test.
* g++.target/i386/mv-symbols3.C: New test.
* g++.target/i386/mv-symbols4.C
This change refactors FMV handling in the frontend to allows greater
reasoning about versions in shared code.
This is needed for target_version semantics and allowing target_clones
and target_versions to both be used for the declaration there are now
two questions that need to be answered for the
This is a reimplementation of get_target_clone_attr_len,
get_attr_str, and separate_attrs using string_slice and auto_vec to make
memory management and use simpler.
This also adds get_version which is a helper function to get the version
string from a decl.
gcc/c-family/ChangeLog:
* c-a
(already Ok-ed off-list, since I forgot to Cc: )
On Thu, 2025-03-27 at 14:40:57 +0100, Gerald Pfeifer wrote:
> On Thu, 27 Mar 2025, Michal Jires wrote:
> > + Introduced incremental Link-Time Optimizations to significantly
> > reduce
> > +average recompilation time with small code changes whi
This adds the assembler_name member to cgraph_function_version_info
to store the base assembler name for the function to be mangled. This is
used in later patches for refactoring FMV mangling.
gcc/ChangeLog:
* cgraph.cc (cgraph_node::insert_new_function_version): Record
assembler
This changes the ambiguation error for C++ to cover cases of differently
annotated FMV function sets whose signatures only differ by their return
type.
It also adds tests covering many FMV errors for Aarch64, including
redeclaration, and mixing target_clones and target_versions.
gcc/cp/ChangeLog
This changes behavior of target_clones and target_version attributes
to be inline with what is specified in the Arm C Language Extension.
Notably this changes the scope and signature of multiversioned functions
to that of the default version, and changes the resolver to be
created at the implemen
This patch removes the warning for target_version and target_clones
in aarch64 as it is now spec compliant.
gcc/ChangeLog:
* config/aarch64/aarch64.cc (aarch64_process_target_version_attr):
Remove warning.
* config/aarch64/aarch64.opt: Mark -Wno-experimental-fmv-target
Notably this respects target_version semantics where an unannotated
function can be the default version.
gcc/ChangeLog:
* attribs.cc (is_function_default_version): Add target_version logic.
---
gcc/attribs.cc | 27 ---
1 file changed, 20 insertions(+), 7 deletion
This patch introduces the TARGET_REJECT_FUNCTION_CLONE_VERSION hook
which is used to determine if a target_clones version string parses.
If true is returned, a warning is emitted and from then on the version
is ignored.
This is as specified in the Arm C Language Extension. The purpose of this
is
This patch adds support for the combination of target_clones and
target_version in the definition of a versioned function.
This patch changes is_function_default_version to consider a function
declaration annotated with target_clones containing default to be a
default version.
This takes advanta
These flags are used to make sure mangling is done correctly.
gcc/ChangeLog:
* cgraph.h (struct cgraph_node): Add dispatcher_resolver_function and
is_target_clone.
---
gcc/cgraph.h | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/gcc/cgraph.h b/gcc/cgr
This tests the mangling of function assembly names when annotated with
target_clones attributes.
gcc/testsuite/ChangeLog:
* g++.target/powerpc/mvc-symbols1.C: New test.
* g++.target/powerpc/mvc-symbols2.C: New test.
* g++.target/powerpc/mvc-symbols3.C: New test.
*
This is a quick refactor of the riscv target processing code
to take a string_slice rather than a decl.
The reason for this is to enable it to work with target_clones
where merging logic requires reasoning about each version string
individually in the front end.
This refactor primarily serves ju
This is similar to clone_function_name and its siblings but takes an
identifier tree node rather than a function declaration.
This is to be used in conjunction with the identifier node stored in
cgraph_function_version_info::assembler_name to mangle FMV functions in
later patches.
gcc/ChangeLog:
Previously, the `record` argument in maybe_version_function allowed the
call to cgraph_node::record_function_versions to be skipped. However,
this was only skipped when both decls were already marked as versioned,
in which case we trigger the early exit in record_function_versions
instead. Theref
The string_slice inherits from array_slice and is used to refer to a
substring of an array that is memory managed elsewhere without modifying
the underlying array.
For example, this is useful in cases such as when needing to refer to a
substring of an attribute in the syntax tree.
This commit al
Hi All,
This is an update on the patch series enabling ACLE compliant FMV
behaviour for targets supporting target_version and a refactor of FMV
in the front end.
This patch series leaves much of the logic that enables FMV for x86
in place, often gated behind TARGET_HAS_FMV_TARGET_ATTRIBUTE.
I wou
In r15-8956-ge90d6c2639c392, I missed one, so while it did fix a problem,
it also exposed another because the braces were now unbalanced.
There's IMO more to do here with ideally whitespace before the } when
using scan-assembler-times but let's do that later.
gcc/testsuite/ChangeLog:
* g
Michal Jires writes:
> This adds missing documentation for LTO flags.
>
> Ok?
>
> gcc/ChangeLog:
>
> * doc/invoke.texi: (Optimize Options):
> Add incremental LTO flags.
> ---
> gcc/doc/invoke.texi | 26 +++---
> 1 file changed, 23 insertions(+), 3 deletions(-)
>
>
Because ranges can have any signed integer-like type as difference_type,
it's not valid to use std::min(diff1, diff2). Instead of calling
std::min with an explicit template argument, this adds a new __mindist
helper that determines the common type and uses that with std::min.
libstdc++-v3/ChangeLo
On 3/25/25 3:37 PM, Marek Polacek wrote:
Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk/14?
-- >8 --
Since r15-8011 cp_build_indirect_ref_1 won't do the *&TARGET_EXPR ->
TARGET_EXPR folding not to change its value category. That fix is
correct but it made us stop extending the life
Some targets (like arm) need some flags to enable _Float16 support.
gcc/testsuite/ChangeLog:
PR target/119133
* gcc.dg/torture/pr119133.c: Add options for float16.
---
gcc/testsuite/gcc.dg/torture/pr119133.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/gcc/testsuite/gcc.dg
On 3/27/25 3:35 AM, Nathaniel Shead wrote:
Bootstrapped and regtested (so far just dg.exp and modules.exp) on
x86_64-pc-linux-gnu, OK for trunk if full regtest succeeds?
Rather than updating copy_fndecl_with_name, we could also just fix
modules specifically by overwriting DECL_ABSTRACT_P before
From: Pierre-Emmanuel Patry
gcc/rust/ChangeLog:
* resolve/rust-finalize-imports-2.0.h: Add parent member functions
from default resolver.
Signed-off-by: Pierre-Emmanuel Patry
---
gcc/rust/resolve/rust-finalize-imports-2.0.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a
> I still was seeing
>
> ;;0--> b 0: i 101 {[sp-0x3c]=[sp-0x3c]+0x1;clobber flags;}:nothing
>
> so the following adds a standard alu insn reservation mimicing that
> from the znver.md description allowing both load and store.
>
> Bootstrap and regtest running on x86_64-unknown-linux-gnu
The following fixes up the ssemov2 type introduction, amending
the znver4_sse_mov_fp_load reservation. This fixes
;; 14--> b 0: i1436 xmm6=vec_concat(xmm6,[ax+0x8]) :nothing
Bootstrapped and tested on x86_64-unknown-linux-gnu, OK?
PR target/119010
* config/i386/zn
On Fri, Mar 21, 2025 at 11:01 AM Iain Sandoe wrote:
>
> It seems that libiberty already has replacements for most of the
> mem* functions, but they are not published via include/libiberty.h.
>
> Tested on x86_64 Linux, Darwin aarch64 Linux, OK for trunk?
OK.
Richard.
> thanks,
> Iain
>
> --- 8<
Like the other instances. This avoids
;; 1--> b 0: i6540 {xmm2=const_vector;unspec[xmm2] 38;}:nothing
Bootstrapped and tested on x86_64-unknown-linux-gnu, OK?
PR target/119010
* config/i386/sse.md (*vmov_constm1_pternlog_false_dep):
Add mode attribute.
---
gc
Like the other DFmode cases.
Bootstrapped and tested on x86_64-unknown-linux-gnu, OK?
PR target/119010
* config/i386/zn4zn5.md (znver4_sse_div_pd,
znver4_sse_div_pd_load, znver5_sse_div_pd_load): Handle DFmode.
---
gcc/config/i386/zn4zn5.md | 6 +++---
1 file changed, 3 i
I have a handful more of these left but those introduce FAILs, while
these all introduce new PASSes.
libstdc++-v3/ChangeLog:
* testsuite/std/format/string_neg.cc: Add missing brace for dg-error.
gcc/testsuite/ChangeLog:
* gcc.dg/analyzer/fd-datagram-socket.c: Fix 'dg-message' sp
On Thu, 27 Mar 2025, Michal Jires wrote:
> + Introduced incremental Link-Time Optimizations to significantly reduce
> +average recompilation time with small code changes while using LTO.
How about rephrasing this to "Incremental Link-Time Optimizations
significantly reduce average recompilat
This fixes some 'scan-tree-dump-times' (vs '-time') typos and one or
two others I noticed in passing.
gcc/testsuite/ChangeLog:
* g++.dg/warn/Winvalid-memory-model.C: Fix typo in comment.
* gcc.dg/builtin-dynamic-object-size-19.c: Ditto.
* gcc.dg/builtin-object-size-19.c: D
On 27/03/2025 13:24, Jonathan Wakely wrote:
Sure thing; is the attached patch OK (on top of the other two)?
Yes, looks good, thanks!
Thank you, the 3 patches have now been committed to trunk.
--
Giuseppe D'Angelo
smime.p7s
Description: S/MIME Cryptographic Signature
On Wed, Mar 26, 2025 at 02:34:51PM -0400, David Malcolm wrote:
> Found by dg-lint.
>
> gcc/testsuite/ChangeLog:
> * gcc.target/ia64/mfused-madd-vect.c: Fix missing trailing " }" in
> dg-do directive.
> * gcc.target/ia64/mfused-madd.c: Likewise.
> * gcc.target/ia64/mno-fused
The following handles TI, OI and XI mode in the respective EVEX
compare reservations that do not use memory (I've not yet run into
ones with). The znver automata has separate reservations for
integer compares (but only for zen1, for zen2 and zen3 there are
no compare reservations at all), but I do
They were using ssecvt instead of sseicvt, I've also added handling
for sseicvt2 which was introduced without fixing up automata, and
the relevant instruction uses DFmode. IMO this is a quite messy
area that could need TLC in the machine description itself.
Bootstrapped and tested on x86_64-unkno
There's the znver4_sse_test reservation which matches the memory-less
SSE compares but currently requires prefix_extra == 1. The old
znver automata in this case sometimes uses znver1-double instead of
znver1-direct, but it's quite a maze. The following simply drops
the prefix_extra requirement, b
The following adds missing reservations for the store variant of
sselog reservations covering
;; 112--> b 0: i1499 [dx-0x10]=vec_select(xmm10,parallel):nothing
Bootstrapped and tested on x86_64-unknown-linux-gnu, OK?
PR target/119010
* config/i386/zn4zn5.md (znver4_sse_l
These just fix inconsistent/unusual style to avoid noise when grepping
and also people picking up bad habits when they see it (as similar
mistakes can be harmful).
gcc/testsuite/ChangeLog:
* c-c++-common/goacc/pr69916.c: Fix unusual whitespace in dg-*.
* g++.old-deja/g++.abi/vtabl
Pushed.
Sam James (3):
testsuite: harmless dg-* whitespace fixes
testsuite: fix typos in comments
testsuite: fix dg-* typos
gcc/testsuite/c-c++-common/goacc/pr69916.c| 2 +-
gcc/testsuite/g++.dg/warn/Winvalid-memory-model.C | 2 +-
gcc/testsuite/g++.old-deja/g++.abi/vtable2
movv8si_internal uses sselog1 and V4SFmode for an instruction like
(insn 363 2437 371 97 (set (reg:V8SI 46 xmm10 [1125])
(const_vector:V8SI [
(const_int 0 [0]) repeated x8
])) "ComputeNonbondedUtil.C":185:21 2402 {movv8si_internal}
this wasn't catched by the ex
1 - 100 of 134 matches
Mail list logo
