On Thu, 11 Jan 2024, Frank Ch. Eigler wrote:
> diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html
:
> -overse...@gcc.gnu.org to add access to the GCC repository.
> +admin-reque...@sourceware.org to add access to the GCC
> repository.
Thanks, Frank. I just pushed this.
(Sorry, I had though
gcc.dg/debug/dwarf2/inline5.c has been XPASSing on Solaris (both SPARC
and x86, 32 and 64-bit) with the native assembler since 20210429.
According to gcc-testresults postings, the same is true on AIX.
XPASS: gcc.dg/debug/dwarf2/inline5.c scan-assembler-not (DIE
(0x([0-9a-f]*)) DW_TAG_
on 2024/2/6 14:01, Michael Meissner wrote:
> On Tue, Jan 23, 2024 at 04:44:32PM +0800, Kewen.Lin wrote:
...
>>> diff --git a/gcc/config/rs6000/rs6000-opts.h
>>> b/gcc/config/rs6000/rs6000-opts.h
>>> index 33fd0efc936..25890ae3034 100644
>>> --- a/gcc/config/rs6000/rs6000-opts.h
>>> +++ b/gcc/confi
Il 06/02/24 10:17, Jonathan Yong ha scritto:
On 2/6/24 05:31, NightStrike wrote:
On Mon, Feb 5, 2024, 06:53 Matteo Italia wrote:
Il 31/01/24 04:24, LIU Hao ha scritto:
在 2024-01-31 08:08, Jonathan Yong 写道:
On 1/24/24 15:17, Matteo Italia wrote:
Ping! That's a one-line fix, and you can find
From: Pan Li
There is another corn case when similar as below example:
void test (void)
{
__riscv_vaadd ();
}
We report error when overloaded function with empty args. For example:
test.c: In function 'foo':
test.c:8:3: error: no matching function call to '__riscv_vaadd' with empty args
on 2024/2/7 08:06, Michael Meissner wrote:
> On Thu, Jan 25, 2024 at 05:28:49PM +0800, Kewen.Lin wrote:
>> Hi Mike,
>>
>> on 2024/1/6 07:38, Michael Meissner wrote:
>>> The MMA subsystem added the notion of accumulator registers as an optional
>>> feature of ISA 3.1 (power10). In ISA 3.1, these ac
LGTM. Up to the release managers.
Thanks for tracking this down.
Aldy
On Tue, Feb 6, 2024 at 9:43 PM Jakub Jelinek wrote:
>
> Hi!
>
> ABSU_EXPR unary expr is special because it has a signed integer
> argument and unsigned integer result (of the same precision).
>
> The following testcase is mis
There has been some confusion in my understanding of how early breaks
work, the following clarifies some comments and undoes one change that
shouldn't have been necessary. It also fixes the dependence test
to avoit TBAA (we're moving stores down across loads).
I'm bootstrapping and testing this o
Hi!
cppreference has 2 more Kona papers listed and it seems eel.is/c++draft/
has those papers incorporated.
Ok for wwwdocs?
diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html
index c265edc0..65030980 100644
--- a/htdocs/projects/cxx-status.html
+++ b/htdocs/projects/c
Why is it 2 not 1 or other value ?
juzhe.zh...@rivai.ai
From: pan2.li
Date: 2024-02-07 17:27
To: gcc-patches
CC: juzhe.zhong; pan2.li; yanzhang.wang; kito.cheng
Subject: [PATCH v1] RISC-V: Bugfix for RVV overloaded intrinsic ICE in function
checker
From: Pan Li
There is another corn case w
From: Kushal Pal
Fixes #2812
gcc/rust/ChangeLog:
* parse/rust-parse-impl.h (Parser::parse_function):
Skip token if its a COMMA.
gcc/testsuite/ChangeLog:
* rust/compile/issue-2812.rs: New test.
Signed-off-by: Kushal Pal
---
gcc/rust/parse/rust-parse-impl.h |
From: Raiki Tamura
gcc/rust/ChangeLog:
* rust-lang.cc (run_rust_tests): Add test.
* rust-system.h: Add .
* util/make-rust-unicode.py: Output NFC_Quick_Check table.
* util/rust-codepoint.h (struct Codepoint): Add is_supplementary
method.
* util/rust
From: Jakub Dupak
gcc/rust/ChangeLog:
* typecheck/rust-hir-type-check-implitem.cc
(TypeCheckTopLevelExternItem::visit):
Add region constraints.
(TypeCheckImplItem::visit): Add region constraints.
* typecheck/rust-hir-type-check-implitem.h: Add region constraints.
From: Philip Herron
Fixes #2747
gcc/rust/ChangeLog:
* typecheck/rust-tyty-subst.cc
(SubstitutionRef::get_mappings_from_generic_args): fix
gcc/testsuite/ChangeLog:
* rust/compile/issue-2747.rs: New test.
---
gcc/rust/typecheck/rust-tyty-subst.cc| 3 ++-
gcc/testsuite/rus
From: Jakub Dupak
gcc/rust/ChangeLog:
* typecheck/rust-hir-type-check.h (class Lifetime): add interned
lifetime class
* typecheck/rust-typecheck-context.cc
(TypeCheckContext::TypeCheckContext): add
resolution tool
(TypeCheckContext::intern_lifetime): add method
From: Jakub Dupak
gcc/rust/ChangeLog:
* typecheck/rust-hir-trait-resolve.cc: add regions
* typecheck/rust-hir-type-check-base.cc
(TypeCheckBase::resolve_literal):
add regions, resolve generic lifetimes
* typecheck/rust-hir-type-check-expr.cc (TypeCheckExpr::visit
From: Philip Herron
Fixes #2772
gcc/testsuite/ChangeLog:
* rust/compile/issue-2772-1.rs: New test.
* rust/compile/issue-2772-2.rs: New test.
---
gcc/testsuite/rust/compile/issue-2772-1.rs | 20
gcc/testsuite/rust/compile/issue-2772-2.rs | 20 +++
From: Philip Herron
Fixes #2782
gcc/testsuite/ChangeLog:
* rust/compile/issue-2782.rs: New test.
Signed-off-by: Philip Herron
---
gcc/testsuite/rust/compile/issue-2782.rs | 12
1 file changed, 12 insertions(+)
create mode 100644 gcc/testsuite/rust/compile/issue-2782.rs
From: Philip Herron
gcc/rust/ChangeLog:
* typecheck/rust-hir-type-check.cc (TypeResolution::Resolve): refactor
* typecheck/rust-hir-type-check.h: new prototype
* typecheck/rust-typecheck-context.cc
(TypeCheckContext::compute_inference_variables): x
---
gcc/rust/typechec
From: Jakub Dupak
gcc/rust/ChangeLog:
* typecheck/rust-tyty-region.h: New file.
Signed-off-by: Jakub Dupak
---
gcc/rust/typecheck/rust-tyty-region.h | 110 ++
1 file changed, 110 insertions(+)
create mode 100644 gcc/rust/typecheck/rust-tyty-region.h
diff --gi
From: Philip Herron
We can point to generic parent types which means we need to do the shallow
resolve thing that rustc does. We have destructure which is similar to get
what the parameter type points to.
Fixes #2775
gcc/rust/ChangeLog:
* typecheck/rust-hir-type-check-pattern.cc (TypeC
From: Nobel Singh
Previously, the default ABI was set to Rust, which is not correct for
extern blocks and extern functions. This patch changes the default
ABI to C for these cases.
gcc/rust/ChangeLog:
* hir/rust-ast-lower-base.cc (ASTLoweringBase::lower_qualifiers):
Change defau
From: Kushal Pal
To use AST::Function instead of AST::TraitItemFunc and
AST::TraitItemMethod, we need to provide similar visitors during
lowering and resolving phase.
gcc/rust/ChangeLog:
* hir/rust-ast-lower-implitem.cc (ASTLowerTraitItem::visit):
Provide visitor for AST::Functi
From: Kushal Pal
gcc/testsuite/ChangeLog:
* rust/compile/issue-2040.rs:
Enclose 'const' in single quotes.
Signed-off-by: Kushal Pal
---
gcc/testsuite/rust/compile/issue-2040.rs | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/testsuite/rust/compile/issue
From: Nobel Singh
This patch moves the implementation of the implitem lowering
from rust-ast-lower-implitem.h into the rust-ast-lower-implitem.cc
file.
gcc/rust/ChangeLog:
* Make-lang.in: Add rust-ast-lower-implitem.cc to list of objects.
* hir/rust-ast-lower-implitem.h (RUST_AS
From: Philip Herron
Fixes #1483
gcc/testsuite/ChangeLog:
* rust/compile/issue-1483.rs: New test.
---
gcc/testsuite/rust/compile/issue-1483.rs | 28
1 file changed, 28 insertions(+)
create mode 100644 gcc/testsuite/rust/compile/issue-1483.rs
diff --git a/gcc/t
From: Jakub Dupak
gcc/rust/ChangeLog:
* hir/tree/rust-hir-item.h: Add missing getter
Signed-off-by: Jakub Dupak
---
gcc/rust/hir/tree/rust-hir-item.h | 5 +
1 file changed, 5 insertions(+)
diff --git a/gcc/rust/hir/tree/rust-hir-item.h
b/gcc/rust/hir/tree/rust-hir-item.h
index 7
From: Philip Herron
This patch introduces one regression because generics are getting better
understood over time. The code here used to apply generics with the same
symbol from previous segments which was a bit of a hack with out limited
inference variable support. The regression looks like it w
From: Jakub Dupak
gcc/rust/ChangeLog:
* typecheck/rust-tyty.cc (BaseType::BaseType): Store orig ref.
(BaseType::get_orig_ref): Add getter.
* typecheck/rust-tyty.h: Store orig ref.
Signed-off-by: Jakub Dupak
---
gcc/rust/typecheck/rust-tyty.cc | 10 --
gcc/rust/
From: Philip Herron
This keeps the resolution code in line with paths.
Addresses #2723
gcc/rust/ChangeLog:
* typecheck/rust-hir-type-check-type.cc: remove hack
---
gcc/rust/typecheck/rust-hir-type-check-type.cc | 16
1 file changed, 16 deletions(-)
diff --git a/gcc/r
From: Kushal Pal
gcc/rust/ChangeLog:
* ast/rust-ast.h: Replace TraitItem with AssociatedItem.
* ast/rust-item.h (class Trait): Likewise.
* expand/rust-expand-visitor.cc (ExpandVisitor::visit):
Likewise.
* parse/rust-parse-impl.h (Parser::parse_trait): Like
From: Kushal Pal
Trait functions now use AST::Function class, so classes
AST::TraitItemFunc, AST::TraitItemMethod, AST::TraitFunctionDecl,
AST::TraitMethodDecl and their related functions can be removed.
gcc/rust/ChangeLog:
* ast/rust-ast-collector.cc (TokenCollector::visit):
Re
From: Kushal Pal
Since we want to use AST::Function class for trait functions as well, we
need to check against specific conditions in ASTValidation phase.
gcc/rust/ChangeLog:
* checks/errors/rust-ast-validation.cc (ASTValidation::visit):
Add checks for Trait functions.
Signed-
From: Kushal Pal
gcc/rust/ChangeLog:
* parse/rust-parse-impl.h (Parser::parse_trait_item):
Handle macros in trait items similar to how its handled for trait
implementation items.
Signed-off-by: Kushal Pal
---
gcc/rust/parse/rust-parse-impl.h | 37 --
From: Kushal Pal
To use AST::Function for trait functions, we can parse trait functions
using available parse_function().
gcc/rust/ChangeLog:
* parse/rust-parse-impl.h (Parser::parse_trait_item):
Use parse_function() to parse trait functions.
Signed-off-by: Kushal Pal
---
gcc
On Wed, Feb 07, 2024 at 10:58:18AM +0100, Jakub Jelinek wrote:
> Hi!
>
> cppreference has 2 more Kona papers listed and it seems eel.is/c++draft/
> has those papers incorporated.
>
> Ok for wwwdocs?
Patch is OK. W3 validates fine too. Thanks,
> diff --git a/htdocs/projects/cxx-status.html b/
The following makes sure to wipe range info before folding the
COND_EXPRs we insert as part of replacing PHI nodes when combining
blocks in the if-conversion pass.
Bootstrapped and tested on x86_64-unknown-linux-gnu, pushed.
PR tree-optimization/113796
* tree-if-conv.cc (combine_b
On 14/01/2024 05:34, Sandra Loosemore wrote:
> On 1/10/24 14:28, Jonny Grant wrote:
>>
>> 2024-01-10 Jonathan Grant
>> gcc/ChangeLog:
>> * doc/extend.texi: Update builtin example for __builtin_FILE
>> __builtin_LINE __builtin_FUNCTION.
>>
>>
>>
>>>From 66290eb477dd1a99310ad9972c45391c2a
2024-02-07 Jonathan Grant
gcc/ChangeLog:
* doc/extend.texi: Update builtin descriptions for __builtin_FILE
__builtin_LINE __builtin_FUNCTION.
>From 9e0b662b5b036f37d7ca90db607bacbb0012e8b3 Mon Sep 17 00:00:00 2001
From: Jonathan Grant
Date: Wed, 7 Feb 2024 14:51:34 +
Subject: [PA
On Wed, 7 Feb 2024 12:43:53 +0100
arthur.co...@embecosm.com wrote:
> diff --git a/gcc/rust/typecheck/rust-hir-type-check-implitem.h
> b/gcc/rust/typecheck/rust-hir-type-check-implitem.h
> index 067465ec77a..4d178440775 100644
> --- a/gcc/rust/typecheck/rust-hir-type-check-implitem.h
> +++ b/gcc/
On Tue, Feb 06, 2024 at 01:28:06PM +0100, Aldy Hernandez wrote:
> The relation oracle grows the internal vector of SSAs as needed, but
> due to an oversight was not growing the basic block vector. This
> fixes the oversight.
>
> OK for trunk?
>
> PR tree-optimization/113735
>
> gcc/testsu
On 2/7/24 16:26, Bernhard Reutner-Fischer wrote:
On Wed, 7 Feb 2024 12:43:53 +0100
arthur.co...@embecosm.com wrote:
diff --git a/gcc/rust/typecheck/rust-hir-type-check-implitem.h
b/gcc/rust/typecheck/rust-hir-type-check-implitem.h
index 067465ec77a..4d178440775 100644
--- a/gcc/rust/typecheck
Tom Tromey writes:
> This reverts commit b7e5a29602143b53267efcd9c8d5ecc78cd5a62f.
>
> This patch caused problems for some users when building gdb, because
> it would cause 'guild' to be invoked with the wrong versin of guile.
> On the whole it seems simpler to just back this out.
>
> * Mak
Hi,
Is it okay to backport b7e4a4c626eeeb32c291d5bbbaa148c5081b6bfd to
releases/gcc-13?
Without this backport, I see these failures on arm-none-eabi:
FAIL:
gcc.dg/analyzer/null-deref-pr108251-smp_fetch_ssl_fc_has_early-O2.c
(test for excess errors)
FAIL: gcc.dg/analyzer/null-deref-pr108251-
Hi,
Is it okay to backport 3cbab07b08d2f3a3ed34b6ec12e67727c59d285c to
releases/gcc-13?
Without this backport, I see these failures on arm-none-eabi:
FAIL: gcc.dg/analyzer/switch-enum-1.c (test for bogus messages, line 26)
FAIL: gcc.dg/analyzer/switch-enum-1.c (test for bogus messages, line
Hi,
Is it okay to backport 71804526d3a71a8c0f189a89ce3aa615784bfd8b to
releases/gcc-13?
Without this backport, I see these failures on arm-none-eabi:
FAIL: g++.dg/contracts/contracts-ctor-dtor2.C(test for errors, line 23)
FAIL: g++.dg/contracts/contracts-ctor-dtor2.C(test for errors,
Hi,
Is it okay to backport 6e15e4e1abed02443a27a69455f4bfa49457c99e to
releases/gcc-13?
Without this backport, I see this failure on arm-none-eabi:
FAIL: g++.dg/contracts/contracts-tmpl-spec2.C output pattern test
Kind regards,
Torbjörn
On 2023-11-26 03:57, Andrew Pinski wrote:
Since co
Hi,
Is it okay to backport 0d24289d129639efdc79338a64188d6d404375e8 to
releases/gcc-13?
Without this backport, I see these failures on arm-none-eabi:
FAIL: g++.dg/warn/Wuse-after-free3.C -std=gnu++14 (test for excess errors)
FAIL: g++.dg/warn/Wuse-after-free3.C -std=gnu++17 (test for excess
Hi,
Is it okay to backport e39b3e02c27bd771a07e385f9672ecf1a45ced77 to
releases/gcc-13?
Without this backport, I see this failure on arm-none-eabi:
FAIL: 23_containers/vector/bool/110807.cc (test for excess errors)
Kind regards,
Torbjörn
On 2023-11-09 02:22, Jonathan Wakely wrote:
On Th
On Mon, Jan 22, 2024 at 7:21 PM Tom Tromey wrote:
> This reverts commit b7e5a29602143b53267efcd9c8d5ecc78cd5a62f.
>
> This patch caused problems for some users when building gdb, because
> it would cause 'guild' to be invoked with the wrong versin of guile.
>
Is "guild" here a typo? (I don't see
Hi,
Is it okay to backport 62b29347c38394ae32858f2301aa9aa65205984e,
2a4d9e4f533c77870cc0eb60fbbd8047da4c7386 and
ba0cde8ba2d93b7193050eb5ef3cc6f7a2cdfe61 to releases/gcc-13?
Without this backport, I see these failures on arm-none-eabi:
FAIL: 29_atomics/atomic/compare_exchange_padding.cc (te
On Wed, 7 Feb 2024 at 16:31, Torbjorn SVENSSON <
torbjorn.svens...@foss.st.com> wrote:
> Hi,
>
> Is it okay to backport 62b29347c38394ae32858f2301aa9aa65205984e,
> 2a4d9e4f533c77870cc0eb60fbbd8047da4c7386 and
> ba0cde8ba2d93b7193050eb5ef3cc6f7a2cdfe61 to releases/gcc-13?
>
> Without this backport,
On Wed, 7 Feb 2024 at 16:25, Torbjorn SVENSSON <
torbjorn.svens...@foss.st.com> wrote:
> Hi,
>
> Is it okay to backport e39b3e02c27bd771a07e385f9672ecf1a45ced77 to
> releases/gcc-13?
>
It would also need 807f47497f17ed50be91f0f879308cb6fa063966
Please test with that as well, and OK for both if a
> -Original Message-
> From: Torbjorn SVENSSON
> Sent: Wednesday, February 7, 2024 8:23 AM
> To: Andrew Pinski (QUIC) ; gcc-
> patc...@gcc.gnu.org
> Cc: Yvan Roux
> Subject: Re: [PATCH 1/2] Fix contracts-tmpl-spec2.C on targets where plain
> char is unsigned by default
>
> Hi,
>
> Is it
Tested on x86_64-pc-linux-gnu, does this look OK for trunk?
-- >8 --
The forward declarations of std::get in added in
r14-8710-g65b4cba9d6a9ff are causing an ICE in the test modules/hello-1
due to what seems to be a declaration merging issue in modules.
What seems to be happening is that in hel
On Wed, 7 Feb 2024 at 17:29, Patrick Palka wrote:
> Tested on x86_64-pc-linux-gnu, does this look OK for trunk?
>
OK.
Do we have a reduced testcase to track the modules bug that will still
exist in the FE?
>
> -- >8 --
>
> The forward declarations of std::get in added in
> r14-8710-g65b4cba
On 2024-02-07 18:13, Andrew Pinski (QUIC) wrote:
-Original Message-
From: Torbjorn SVENSSON
Sent: Wednesday, February 7, 2024 8:23 AM
To: Andrew Pinski (QUIC) ; gcc-
patc...@gcc.gnu.org
Cc: Yvan Roux
Subject: Re: [PATCH 1/2] Fix contracts-tmpl-spec2.C on targets where plain
char is u
On 2024-02-07 17:33, Jonathan Wakely wrote:
On Wed, 7 Feb 2024 at 16:31, Torbjorn SVENSSON
mailto:torbjorn.svens...@foss.st.com>>
wrote:
Hi,
Is it okay to backport 62b29347c38394ae32858f2301aa9aa65205984e,
2a4d9e4f533c77870cc0eb60fbbd8047da4c7386 and
ba0cde8ba2d93b719305
On 07/02/2024 07:59, Tejas Belagod wrote:
> This patch fixes a bug that causes indirect calls in PAC-enabled functions
> to be tailcalled incorrectly when all argument registers R0-R3 are used.
>
> Tested on arm-none-eabi for armv8.1-m.main. OK for trunk?
>
> 2024-02-07 Tejas Belagod
>
>
On Feb 6, 2024, at 8:58 AM, Torbjörn SVENSSON
wrote:
>
> Ok for trunk and releases/gcc-13?
Ok. If .* goes across newlines, you might want to not use ..
> -if {![regexp -- "/${compiler}(\\.exe)? -quiet.*$compiler_pattern"
> $gcc_output]} {
> +if {![regexp -- "/${compiler}(\\.exe)? .*-
On Wed, 7 Feb 2024, Jonathan Wakely wrote:
>
>
> On Wed, 7 Feb 2024 at 17:29, Patrick Palka wrote:
> Tested on x86_64-pc-linux-gnu, does this look OK for trunk?
>
>
> OK.
>
> Do we have a reduced testcase to track the modules bug that will still exist
> in the FE?
https://gcc.gnu.org
On 2/7/24 11:22, Torbjorn SVENSSON wrote:
Hi,
Is it okay to backport 71804526d3a71a8c0f189a89ce3aa615784bfd8b to
releases/gcc-13?
OK.
Without this backport, I see these failures on arm-none-eabi:
FAIL: g++.dg/contracts/contracts-ctor-dtor2.C (test for errors, line 23)
FAIL: g++.dg/contr
On Wed, Feb 07, 2024 at 05:21:10PM +0800, Kewen.Lin wrote:
> on 2024/2/6 14:01, Michael Meissner wrote:
> Sorry for the possible confusion here, the "tune_proc" that I referred to is
> the variable in the above else branch:
>
>enum processor_type tune_proc = (TARGET_POWERPC64 ? PROCESSOR_DEFAU
On Sun, Feb 04, 2024 at 01:47:12PM +0800, Kewen.Lin wrote:
> > diff --git a/gcc/config/rs6000/mma.md b/gcc/config/rs6000/mma.md
> > index 525a85146ff..f06e6bbb184 100644
> > --- a/gcc/config/rs6000/mma.md
> > +++ b/gcc/config/rs6000/mma.md
> > @@ -227,13 +227,22 @@ (define_int_attr apv [(U
On Tue, Feb 6, 2024 at 6:08 PM Jason Merrill wrote:
>
> Tested x86_64-pc-linux-gnu. Any thoughts?
It still makes sense to me, for what that's worth.
Ian
> -- 8< --
>
> The patch for PR22340 (r104978) moved the adding of TARGET_LIB_PATH to
> RPATH_ENVVAR from POSTSTAGE1_HOST_EXPORTS to HOST_EX
On Tue, 19 Dec 2023, Jeff Law wrote:
> Pushed to the trunk.
Is this minor follow-up okay, adding a full stop and shortening a bit?
Gerald
diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 6d917535..dbc77493 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/chan
On 2/6/24 19:23, Hans-Peter Nilsson wrote:
Date: Mon, 22 Jan 2024 14:33:59 -0500
From: Marek Polacek
On Mon, Jan 22, 2024 at 06:02:32PM +0100, Hans-Peter Nilsson wrote:
I don't really know whether this is the right way to treat
CONVERT_EXPR as below, but... Regtested native
x86_64-linux-gnu
On 2/6/24 16:59, Patrick Palka wrote:
Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK
for trunk?
-- >8 --
Since template argument coercion happens relative to the most general
template (for a class template at least), during NTTP type CTAD we might
need to consider outer ar
On 2/5/24 22:11, Marek Polacek wrote:
On Mon, Feb 05, 2024 at 10:14:34AM -0500, Jason Merrill wrote:
On 2/3/24 10:24, Marek Polacek wrote:
Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
I'm not certain OPT_Wc__20_extensions is the best thing for something
from [diff.cpp17]; would
On Linux/x86_64,
194d0956ef5992d4e453bde3eb5772dc077f610c is the first bad commit
commit 194d0956ef5992d4e453bde3eb5772dc077f610c
Author: Tamar Christina
Date: Wed Feb 7 10:57:05 2024 +
middle-end: add additional runtime test for [PR113467]
caused
FAIL: gcc.dg/vect/vect-early-break_1
Tested x86_64-pc-linux-gnu, applying to trunk.
Marek, I'll leave it to you to judge if there is anything else needed for
P2308.
-- 8< --
The new testcase from P2308 crashed trying to expand 'this' without an
object to refer to, because we stripped the TARGET_EXPR in
create_template_parm_object.
On Wed, Feb 07, 2024 at 05:38:46PM +0800, Kewen.Lin wrote:
> >>> -(define_insn_and_split "*movxo"
> >>> +(define_insn_and_split "*movxo_nodm"
> >>>[(set (match_operand:XO 0 "nonimmediate_operand" "=d,ZwO,d")
> >>> (match_operand:XO 1 "input_operand" "ZwO,d,d"))]
> >>> - "TARGET_MMA
> >>> +
There is a proposal to split the A extension into two parts: Zaamo and Zalrsc.
This patch adds basic support by making the A extension imply Zaamo and
Zalrsc.
Proposal: https://github.com/riscv/riscv-zaamo-zalrsc/tags
gcc/ChangeLog:
* common/config/riscv/riscv-common.cc: Add Zaamo and Za
All amo patterns can be represented with lrsc sequences.
Add these patterns as a fallback when Zaamo is not enabled.
gcc/ChangeLog:
* config/riscv/sync.md (atomic_): New expand
pattern.
(amo_atomic_): Rename amo pattern.
(atomic_fetch_): New lrsc sequence pattern.
Convert testsuite infrastructure to use Zalrsc and Zaamo rather than A.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/amo-table-a-6-amo-add-1.c: Use Zaamo rather than A.
* gcc.target/riscv/amo-table-a-6-amo-add-2.c: Ditto.
* gcc.target/riscv/amo-table-a-6-amo-add-3.c: Ditto.
On Mon, Feb 05, 2024 at 11:58:31AM +0800, Kewen.Lin wrote:
> Hi Mike,
I will comment on about 1/2 of the things, and come back with the other
comments.
> on 2024/1/6 07:42, Michael Meissner wrote:
> > This patch is a prelimianry patch to add the full 1,024 bit dense math
> > register> (DMRs) for
On 2/7/24 14:23, Gerald Pfeifer wrote:
On Tue, 19 Dec 2023, Jeff Law wrote:
Pushed to the trunk.
Is this minor follow-up okay, adding a full stop and shortening a bit?
Yes, of course.
Thanks.
jeff
My fix for bug 111059 and bug 111911 caused a conversion of a floating
constant to boolean to wrongly no longer be considered an integer
constant expression, because logic to insert a NOP_EXPR in
c_objc_common_truthvalue_conversion for an argument not an integer
constant expression itself now took
I think it relates to the location of frm args. For example, we use below to
get the operand index. And then pass to function_checker.
unsigned int frm_num = c.arg_num () - 2;
Unfortunately, the function checker treat argno as unsigned, thus we need to
ensure that c.arg_num () is not less than
Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
-- >8 --
Here the problem is that we give hard errors while substituting
template parameters during overload resolution of is_throwable
which has an invalid throw in decltype.
The backtrace shows that fn_type_unification -> instantiate_
On Wed, Feb 07, 2024 at 04:32:57PM -0500, Jason Merrill wrote:
> On 2/6/24 19:23, Hans-Peter Nilsson wrote:
> > > Date: Mon, 22 Jan 2024 14:33:59 -0500
> > > From: Marek Polacek
> >
> > > On Mon, Jan 22, 2024 at 06:02:32PM +0100, Hans-Peter Nilsson wrote:
> > > > I don't really know whether this
On Feb 6, 2024, Jason Merrill wrote:
> Reverting that hunk of the change fixed my problem with bubblestrapping GCC
> 12 with ccache on a host with a newer system libstdc++.
Did you have libcc1, gnattools and gotools enabled in your testing?
Those non-bootstrapped tools are most likely to be pro
On 2/4/24 9:58 PM, Jeff Law wrote:
On 2/2/24 15:48, Greg McGary wrote:
input: (sign_extend:DI (mem/c:SI (symbol_ref:DI ("minus_1") [flags
0x86] ) [1 minus_1+0 S4 A32]))
result: (subreg:DI (mem/c:SI (symbol_ref:DI ("minus_1") [flags 0x86]
) [1 minus_1+0 S4 A32]) 0)
Later, the high part
Committed, thanks Juzhe.
Pan
From: juzhe.zh...@rivai.ai
Sent: Thursday, February 8, 2024 2:43 PM
To: Li, Pan2 ; gcc-patches
Cc: Wang, Yanzhang ; kito.cheng
Subject: Re: RE: [PATCH v1] RISC-V: Bugfix for RVV overloaded intrinsic ICE in
function checker
LGTM
j
On Tue, Feb 6, 2024 at 11:49 AM H.J. Lu wrote:
>
> 1. The only supported TLS code sequence with ADD is
>
> addq foo@gottpoff(%rip),%reg
>
> Change je constraint to a memory operand in APX NDD ADD pattern with
> register source operand.
>
> 2. The instruction length of APX NDD instructions
Florian Weimer writes:
> ---
> htdocs/gcc-14/porting_to.html | 465
> ++
> 1 file changed, 465 insertions(+)
>
Can't approve but LGTM. Thank you for being so thorough - it'll be
helpful when showing upstreams.
> diff --git a/htdocs/gcc-14/porting_to.ht
86 matches
Mail list logo