Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'cpplib' has been submitted
by the German team of translators. The file is available at:
https://translationproject.org/latest/cpplib/de.po
(This file, 'cpplib-15.1-b2025031
On Mon, Mar 10, 2025 at 3:59 PM Martin Jambor wrote:
>
> Hi,
>
> when reading the function ao_compare::compare_ao_refs I came accross
> what I believe to ba a copy-and-paste error which this patch fixes.
>
> Bootstrapped, LTO-bootstrapped and tested on x86_64-linux. OK for
> master?
By the way h
libstdc++-v3/ChangeLog:
* include/bits/locale_facets_nonio.tcc (time_put::do_put): Fix
typo in comment.
---
Pushed to trunk as obvious.
libstdc++-v3/include/bits/locale_facets_nonio.tcc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libstdc++-v3/include/bits
From: Kushal Pal
gcc/rust/ChangeLog:
* checks/errors/borrowck/rust-bir-builder-internal.h:
Use `make_*` functions to create BIR::Statements.
* checks/errors/borrowck/rust-bir.h: Make a complete constructor
and introduce `make_*` functions to create various
Thanks, forgot to mention, these patches are bootstrapped and regtested on
x86_64-pc-linux-gnu{-m32,-m64}.
BRs,
Lin
> -Original Message-
> From: Liu, Hongtao
> Sent: Thursday, March 20, 2025 9:43 AM
> To: Hu, Lin1 ; gcc-patches@gcc.gnu.org
> Cc: ubiz...@gmail.com
> Subject: RE: [PATCH 0
On Wed, Mar 19, 2025 at 12:11:56PM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> When -fprofile-generate is used musttail often fails because the
> compiler adds instrumentation after the tail calls.
>
> This patch prevents adding exit extra edges after musttail because for a
> tail call the e
From: Pierre-Emmanuel Patry
Make those functions public so they can be used within a lambda on GCC
4.8.
gcc/rust/ChangeLog:
* ast/rust-ast-visitor.h: Make visit functions public.
Signed-off-by: Pierre-Emmanuel Patry
---
gcc/rust/ast/rust-ast-visitor.h | 1 -
1 file changed, 1 deletio
From: Philip Herron
Qualified path expressions usually are ::... but the as is optional
this adds the extra checking in hir lowering to not hit that nullptr.
Fixes #3082
gcc/rust/ChangeLog:
* hir/rust-ast-lower-type.cc (ASTLowerQualifiedPathInType::visit):
check for valid as se
> -Original Message-
> From: Richard Biener
> Sent: Wednesday, March 19, 2025 10:24
> To: gcc-patches@gcc.gnu.org
> Cc: Jakub Jelinek ; rdub...@symas.com
> Subject: [PATCH 2/2] [cobol] make sources coretypes.h and tree.h clean
>
> The following removes HOWEVER_GCC_DEFINES_TREE and the alt
On Wed, Mar 19, 2025 at 6:34 PM Andi Kleen wrote:
>
> From: Andi Kleen
>
> When -fprofile-generate is used musttail often fails because the
> compiler adds instrumentation after the tail calls.
>
> This patch prevents adding exit extra edges after musttail because for a
> tail call the execution
> -Original Message-
> From: Liu, Hongtao
> Sent: Thursday, March 20, 2025 9:29 AM
> To: Hu, Lin1 ; gcc-patches@gcc.gnu.org
> Cc: ubiz...@gmail.com
> Subject: RE: [PATCH 0/4] Fix AVX10.2 SAT CVT.
>
>
>
> > -Original Message-
> > From: Hu, Lin1
> > Sent: Wednesday, March 19, 2
Ping.
On 3/5/25 20:21, Jørgen Kvalsvik wrote:
Ping.
On 2/21/25 19:15, Jørgen Kvalsvik wrote:
Ping
On 2/12/25 16:30, Jørgen Kvalsvik wrote:
I have applied fixes for everything in the last review, plus some GNU
style fixes that I had missed previously. We have tested and used a
build with this
> -Original Message-
> From: Jiang, Haochen
> Sent: Wednesday, March 19, 2025 3:38 PM
> To: gcc-patches@gcc.gnu.org
> Cc: Liu, Hongtao ; ubiz...@gmail.com
> Subject: [PATCH 00/27] Use avx10.x as the only option for AVX10 with 512 bit
> vector support while remove avx10.x-256/512 option
From: Andi Kleen
There are multiple reports (see PR 119376) now where semantic differences
in the gcc musttail implementation break existing programs written for the clang
variant.
Even though that can be all hopefully fixed eventually,
for the gcc 15 release it seems safer to disable clang::mus
From: Andi Kleen
When -fprofile-generate is used musttail often fails because the
compiler adds instrumentation after the tail calls.
This patch prevents adding exit extra edges after musttail because for a
tail call the execution leaves the function and can never come back
even on a unwind or e
> -Original Message-
> From: Hu, Lin1
> Sent: Wednesday, March 19, 2025 3:49 PM
> To: gcc-patches@gcc.gnu.org
> Cc: Liu, Hongtao ; ubiz...@gmail.com
> Subject: [PATCH 0/4] Fix AVX10.2 SAT CVT.
>
> Hi, all
>
> This series of patches fixes three issues in AVX10.2 SAT CVT:
>
> 1. Adds e
Hi,
This patch merges the D front-end and run-time libraries with the
upstream dmd 2.108.1 release.
D front-end changes:
- Import dmd v2.108.1.
D runtime changes:
- Import druntime v2.108.1.
Phobos changes:
- Import phobos v2.108.1.
Bootstrapped and regression tested
From: Owen Avery
gcc/rust/ChangeLog:
* resolve/rust-late-name-resolver-2.0.cc
(Late::visit): Visit GenericArgs and GenericArg, the former
because the latter involves a non-virtual member function call.
* resolve/rust-late-name-resolver-2.0.h
(Late::visit):
This moves is_floating_point over to using FLOAT_TYPE_P instead
of manually checking. Note before it would return true for all
COMPLEX_TYPE but complex types' inner type could be integral.
Also fixes up the comment to be in more of the GNU style.
Bootstrapped and tested on x86_64-linux-gnu.
gcc/
This is a set of 4 patches that do some small cleanups of rust-gcc.cc
The first patch might fix a bug in some cases but I am not 100% sure since
I suspect complex types here might only be floating point types but who knows.
The rest are using GCC's checks better or just other small changes that hel
Inside a BLOCK node, all of the variables of the scope/block
are chained together and that connects them to the block.
This just adds a comment to that effect as reading the code
it is not so obvious why they need to be chained together.
gcc/rust/ChangeLog:
PR rust/119342
* rust-g
Since r15-3992-g698e0ec89bc096 we optimize x<=y && x>=y to x==y.
Honour signaling NaNs by using option -fsignaling-nans in order to
prevent this.
gcc/testsuite/ChangeLog:
* gcc.target/s390/zvector/autovec-double-signaling-eq-z13.c:
Honour sNaNs.
---
.../gcc.target/s390/zvector/au
The default is -std=gnu++17 now, not -std=gnu++14.
libstdc++-v3/ChangeLog:
* doc/xml/manual/test.xml: Fix default for -std option.
* doc/html/manual/test.html: Regenerate.
---
Pushed to trunk.
libstdc++-v3/doc/html/manual/test.html | 4 ++--
libstdc++-v3/doc/xml/manual/test.xml
Am 19.03.25 um 23:25 schrieb Steve Kargl:
On Wed, Mar 19, 2025 at 11:08:58PM +0100, Harald Anlauf wrote:
the attached patch addresses an actually very long-standing issue
with bogus bounds checks for components of nested derived types in
assignments when an intermediate level has the POINTER at
On Wed, Mar 19, 2025 at 11:08:58PM +0100, Harald Anlauf wrote:
>
> the attached patch addresses an actually very long-standing issue
> with bogus bounds checks for components of nested derived types in
> assignments when an intermediate level has the POINTER attribute
> instead of the ALLOCATABLE
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
Because we build an array type to represent an array new, we hit a VLA
error in compute_array_index_type for a variable length array new. To avoid
this, let's build the MINUS_EXPR and index type directly.
I also noticed that the non-consta
On Wed, 19 Mar 2025 at 18:27, François Dumont wrote:
>
> Hi
>
> Now that __cpp_lib_ranges_to_container support have been added to
> std::set we can activate those checks.
>
> libstdc++: Activate a __cpp_lib_ranges_to_container dependent test
>
> Now that std::set has support for __cpp_li
Dear all,
the attached patch addresses an actually very long-standing issue
with bogus bounds checks for components of nested derived types in
assignments when an intermediate level has the POINTER attribute
instead of the ALLOCATABLE attribute. It turned out that the
check for a reallocatable l
From: Pierre-Emmanuel Patry
We did not check the optional was valid, this lead to rogue dereference
and undefined behaviors.
gcc/rust/ChangeLog:
* resolve/rust-late-name-resolver-2.0.cc (Late::visit): Add optional
check.
Signed-off-by: Pierre-Emmanuel Patry
---
gcc/rust/resol
On Wed, 19 Mar 2025 15:24:19 +0100 (CET)
Richard Biener wrote:
> The following removes HOWEVER_GCC_DEFINES_TREE and the alternate
> definition of tree from symbols.h and instead ensures that both
> coretypes.h and tree.h are included where required. This required
> putting GCCs own 'NONE' in a s
On Wed, 19 Mar 2025 12:13:47 -0500 (CDT)
Robert Dubner wrote:
> In file included from ../../gcc/cobol/scan.l:42:
> cobol/parse.h:932:12: error: 'NONE' conflicts with a previous
> declaration 932 | NONE = 881,/* NONE */
Here, NONE names a COBOL token because (I assume wit
From: Owen Avery
gcc/rust/ChangeLog:
* resolve/rust-default-resolver.cc
(DefaultResolver::visit): Remove some empty overloads which
DefaultASTVisitor::visit should be able to handle.
* resolve/rust-default-resolver.h
(DefaultResolver::visit): Likewise.
gc
From: Owen Avery
This runs the standard compile/**.rs tests
with name resolution 2.0 enabled. The exclude file
can be used to exclude tests which are not yet working
with name resolution 2.0.
gcc/testsuite/ChangeLog:
* rust/compile/nr2/compile.exp: New test.
* rust/compile/nr2/e
On Sat, May 11, 2024 at 12:44 PM NightStrike wrote:
> On Thu, May 9, 2024 at 1:47 PM David Malcolm wrote:
> >
> > From: Tim Lange
> >
> > This patch adds the reproducers reported in PR 110014 as test cases. The
> > false positives in those cases are already fixed with PR 109577.
> >
> > 2023-06
> This looks wrong to me. Even tail calls can be terminated with exit,
> perform longjmp, do other things for which stmt_can_terminate_bb_p
> should return true. stmt_can_terminate_bb_p is used in many places, not
> just in the predict instrumentation.
Okay so the check should be only used for s
The following patch fixes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119270
The patch was successfully bootstrapped and tested on x86_64 and aarch64.
commit 6c443e128802bd93158a3db7c4edf5fc1fc76c8d
Author: Vladimir N. Makarov
Date: Wed Mar 19 16:06:41 2025 -0400
[PR119270][IRA]: Ignor
For building ghdl, the compiler needs to be patched to know the "vhdl"
language. Could that patch be applied to the upstream GCC, so that not
everybody needs to patch GCC to build ghdl?
Thanks, Matthias
Make vhdl known to the PPC backend. See
see https://github.com/ghdl/ghdl/blob/master/doc/
Andi Kleen writes:
> diff --git a/gcc/input.cc b/gcc/input.cc
> index fabfbfb6eaa..d3b12037ba8 100644
> --- a/gcc/input.cc
> +++ b/gcc/input.cc
> @@ -1325,6 +1325,8 @@ dump_line_table_statistics (void)
>if (s.num_expanded_macros != 0)
> fprintf (stderr, "Average number of tokens per macr
From: Kushal Pal
gcc/rust/ChangeLog:
* checks/errors/borrowck/rust-bir-place.h:
Used `IndexVec` with ScopeId as index.
Signed-off-by: Kushal Pal
---
.../checks/errors/borrowck/rust-bir-place.h | 25 +--
1 file changed, 12 insertions(+), 13 deletions(-)
diff
Then we can also remove the added -std=gnu17
Tested on x86_64-unknown-linux-gnu, pushed.
PR testsuite/113634
* gcc.dg/Wfree-nonheap-object-7.c: Adjust calloc and realloc
declarations, remove -std=gnu17.
---
gcc/testsuite/gcc.dg/Wfree-nonheap-object-7.c | 6 +++---
1 file
diagnostic_context's dtor assumed that it owned the m_urlifier pointer
and would delete it.
As of r15-5988-g5a022062d22e0b this isn't always the case -
auto_urlify_attributes is used in various places in the C/C++ frontends
and in the middle-end to temporarily override the urlifier with an
on-stac
From: Pierre-Emmanuel Patry
We can let the default visitor visit those nodes anyway so we're sure
all nodes can be reached.
gcc/rust/ChangeLog:
* resolve/rust-default-resolver.cc (DefaultResolver::visit): Remove
empty visit function implementations.
* resolve/rust-defaul
From: Arthur Cohen
gcc/rust/ChangeLog:
* resolve/rust-early-name-resolver-2.0.cc (Early::resolve_glob_import):
New function.
(Early::resolve_simple_import): Likewise.
(Early::resolve_rebind_import): Likewise.
(Early::build_import_mapping): Likewise.
* res
From: Pierre-Emmanuel Patry
Box definition is part of the standard library and cannot be found during
name resolution. This simple definition prevent any error from being
emitted.
gcc/testsuite/ChangeLog:
* rust/compile/box_syntax_feature_gate.rs: Add box land item
definition.
From: Kushal Pal
This commit adds location_t to BIR::Statement where type is ASSIGNMENT
this information will be later used for reporting borrow-checking
errors.
gcc/rust/ChangeLog:
* checks/errors/borrowck/rust-bir-builder-expr-stmt.cc
(ExprStmtBuilder::visit): Added location p
From: Philip Herron
We need to resolve the never type which is its own special AST node so it
doesnt magically get handled like the regular builtin type paths such as
i32.
Fixes #3035
gcc/rust/ChangeLog:
* resolve/rust-ast-resolve-type.cc (ResolveType::visit):
handle never type
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the French team of translators. The file is available at:
https://translationproject.org/latest/gcc/fr.po
(This file, 'gcc-15.1-b20250316.fr.po',
From: Philip Herron
This was resolved in: 18422c9c386 which was missing the name
resolution step for unit-types.
Fixes #2203
gcc/testsuite/ChangeLog:
* rust/compile/nr2/exclude:
* rust/compile/issue-2203.rs: New test.
Signed-off-by: Philip Herron
---
gcc/testsuite/rust/compi
On Wed, 19 Mar 2025 at 13:09, Jonathan Wakely wrote:
>
> On Sat, 1 Mar 2025 at 05:24, XU Kailiang wrote:
> >
> > Formatting a time point with %c was implemented by calling
> > std::vprint_to with format string constructed from locale's D_T_FMT
> > string, but in some locales this string does not
On 3/16/25 11:20 AM, Andrew Pinski wrote:
gcc/ChangeLog:
PR rtl-optimization/118914
* combine.cc (recog_for_combine): Add old_nregs and new_nregs
argument (defaulting to 0). Update call to recog_for_combine_1.
(combine_split_insns): Add old_nregs and new_nregs arg
From: Pierre-Emmanuel Patry
It requires the standard library and Copy to work correctly which we
cannot provide. Stopping the compiler before the name resolution allow us
to prevent an error whilst resolving Copy and keep the test's goal.
gcc/testsuite/ChangeLog:
* rust/compile/function
Hi Jason!
On 2013-05-03T16:24:43-0400, Jason Merrill wrote:
> Last year Florian fixed the compiler to detect overflow in array new
> size calculations and pass (size_t)-1 in that case. But C++11 specifies
> that in case of overflow the program throws std::bad_array_new_length
> (http://www.op
From: Pierre-Emmanuel Patry
We can reduce code duplication by using the default visitor functions
from within the scoped lambda function.
gcc/rust/ChangeLog:
* resolve/rust-default-resolver.cc (DefaultResolver::visit): Use
default visitor instead.
Signed-off-by: Pierre-Emmanuel
Since January, GCC has been miscompiling Newlib libm on AMD GCN due to
undefined behaviour in the RESIZE_VECTOR macro. It was "working" but expanding
the size of a vector would no longer zero the additional lanes, as it expected.
See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119325
---
newlib
From: Owen Avery
gcc/rust/ChangeLog:
* checks/errors/rust-hir-pattern-analysis.cc: Add includes.
(PatternChecker::visit): Use name resolver 2.0 when enabled.
Signed-off-by: Owen Avery
---
.../checks/errors/rust-hir-pattern-analysis.cc | 16 +++-
1 file changed, 1
From: Arthur Cohen
gcc/rust/ChangeLog:
* Make-lang.in: Add new object file.
* ast/rust-item.h: Constify method.
* resolve/rust-early-name-resolver-2.0.cc (Early::go): Call into
the imports finalizer.
(Early::resolve_glob_import): Remove old resolution.
On Wed, 19 Mar 2025, Jakub Jelinek wrote:
> Hi!
>
> Even in C23/C2Y any initialization of flexible array member is still
> invalid, so we should emit a pedwarn on it. But we no longer do for
> initialization with {}. The reason is that for C17 and earlier,
> we already emitted a pedwarn on the
From: badumbatish
gcc/rust/ChangeLog:
* resolve/rust-ast-resolve.cc (NameResolution::go):
Fix warnings from const auto& to const auto
---
gcc/rust/resolve/rust-ast-resolve.cc | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/gcc/rust/resolve/rust-ast-resolv
Hi Andre,
Thanks for the review - I'll act on the points that you raised.
The Linaro people reported a failure in reduce_1.f90 execution, which I
believe is due to incorrect casting of 'dim' and a wrong specification of
its kind. I am waiting to hear back from them as to whether or not I have
fix
Gentle ping for https://gcc.gnu.org/pipermail/gcc-patches/2025-March/676875.html
Hi
Now that __cpp_lib_ranges_to_container support have been added to
std::set we can activate those checks.
libstdc++: Activate a __cpp_lib_ranges_to_container dependent test
Now that std::set has support for __cpp_lib_ranges_to_container we can
activate a test using it in a fancy
From: Kushal Pal
gcc/rust/ChangeLog:
* checks/errors/borrowck/rust-bir-builder-expr-stmt.cc
(ExprStmtBuilder::setup_loop): Use value of ScopeId.
(ExprStmtBuilder::visit): Use continue scope id instead of
continue basic block id.
* checks/errors/borrowck/ru
From: jjasmine
gcc/rust/ChangeLog:
* backend/rust-compile-expr.cc (CompileExpr::visit):
Local testing for build_string and debug()
---
gcc/rust/backend/rust-compile-expr.cc | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/gcc/rust/backend/rust-compile-expr
From: Owen Avery
gcc/rust/ChangeLog:
* checks/errors/rust-const-checker.cc: Add includes.
(ConstChecker::visit): Use name resolver 2.0 to lookup
function definitions when name resolution 2.0 is enabled.
gcc/testsuite/ChangeLog:
* rust/compile/nr2/exclude: Remove
This message appears to have been posted twice, and I don't see a [PATCH
1/2]
Am I missing something?
Bob D.
> -Original Message-
> From: Richard Biener
> Sent: Wednesday, March 19, 2025 10:24
> To: gcc-patches@gcc.gnu.org
> Cc: Jakub Jelinek ; rdub...@symas.com
> Subject: [PATCH 2/2] [
From: Owen Avery
gcc/rust/ChangeLog:
* resolve/rust-toplevel-name-resolver-2.0.cc
(TopLevel::visit): Handle ConstGenericParam.
* resolve/rust-toplevel-name-resolver-2.0.h
(TopLevel::visit): Likewise.
Signed-off-by: Owen Avery
---
gcc/rust/resolve/rust-toplevel-
From: badumbatish
gcc/rust/ChangeLog:
* expand/rust-macro-builtins-asm.cc (parse_reg_operand_in): Fix
compiler error on ast wrong implicit construct push_back
---
gcc/rust/expand/rust-macro-builtins-asm.cc | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gcc
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_template_bindings -> tsubst -> ... -> convert_like ->
... -> c_common_truthvalue_conve
On Wed, 19 Mar 2025 at 13:09, Jonathan Wakely wrote:
>
> On Sat, 1 Mar 2025 at 05:24, XU Kailiang wrote:
> >
> > Formatting a time point with %c was implemented by calling
> > std::vprint_to with format string constructed from locale's D_T_FMT
> > string, but in some locales this string does not
From: Owen Avery
gcc/rust/ChangeLog:
* typecheck/rust-hir-type-check-pattern.cc: Add includes.
(TypeCheckPattern::visit): Use name resolver 2.0 if enabled.
* resolve/rust-name-resolution-context.cc
(NameResolutionContext::lookup): Make const qualified.
*
From: Owen Avery
gcc/rust/ChangeLog:
* backend/rust-compile-item.cc
(CompileItem::visit): Check canonical path of StaticItem
properly when name resolution 2.0 is enabled.
* resolve/rust-toplevel-name-resolver-2.0.cc
(TopLevel::visit): Insert static items i
From: Owen Avery
gcc/rust/ChangeLog:
* resolve/rust-toplevel-name-resolver-2.0.cc
(TopLevel::visit): Handle ExternalStaticItem.
* resolve/rust-toplevel-name-resolver-2.0.h
(TopLevel::visit): Likewise.
Signed-off-by: Owen Avery
---
gcc/rust/resolve/rust-toplevel
From: Pierre-Emmanuel Patry
We might have some duplicated name in some pattern and we should
therefore not assert the non duplication of identifiers.
gcc/rust/ChangeLog:
* resolve/rust-late-name-resolver-2.0.cc (Late::visit): Remove
assertion and explicitely tells why we ignore
From: Owen Avery
Not thrilled with some of this boilerplate, but it does seem like an
improvement.
gcc/rust/ChangeLog:
* ast/rust-expr.h
(InlineAsmOperand): Replace multiple mutually-exclusive tl::optional
fields with a std::unique_ptr and modify nested classes to allow
Like the main driver (as well as gccgo, gccrs, gcov, etc) the gnat driver
prints the standard version message in response to the --version switch, but
it is not properly formatted.
Tested on x86-64/Linux, applied on the mainline.
2025-03-19 Eric Botcazou
* gnatvsn.adb (Gnat_Free_So
From: Owen Avery
gcc/rust/ChangeLog:
* checks/lints/rust-lint-marklive.cc
(MarkLive::visit_path_segment): Use name resolver 2.0 when
enabled.
(MarkLive::visit): Likewise.
Signed-off-by: Owen Avery
---
gcc/rust/checks/lints/rust-lint-marklive.cc | 31 +++
From: Owen Avery
gcc/rust/ChangeLog:
* resolve/rust-toplevel-name-resolver-2.0.cc
(TopLevel::visit): Handle TypeAlias.
* resolve/rust-toplevel-name-resolver-2.0.h
(TopLevel::visit): Likewise.
gcc/testsuite/ChangeLog:
* rust/compile/nr2/exclude: Remove ty
On Wed, Mar 19, 2025 at 12:13:47PM -0500, Robert Dubner wrote:
> I applied the patch and I am trying to compile it; there is a problem.
>
>
> In file included from ../../gcc/cobol/scan.l:42:
> cobol/parse.h:932:12: error: 'NONE' conflicts with a previous declaration
> 932 | NONE = 881,
From: Owen Avery
gcc/rust/ChangeLog:
* resolve/rust-forever-stack.h
(ForeverStack::to_canonical_path): Make const.
(ForeverStack::to_rib): Add const overload.
(ForeverStack::reverse_iter): Add const overloads.
(ForeverStack::ConstDfsResult): Add.
(
From: Pierre-Emmanuel Patry
gcc/testsuite/ChangeLog:
* rust/compile/nr2/exclude: Remove cast_generics.rs, issue-1131.rs,
issue-1383.rs and unsafe10.rs
Signed-off-by: Pierre-Emmanuel Patry
---
gcc/testsuite/rust/compile/nr2/exclude | 4
1 file changed, 4 deletions(-)
diff
From: Philip Herron
The resolution with ! was fixed in: 09cfe530f9c this adds a
test case to show the other issue is also fixed.
Fixes #2951
gcc/testsuite/ChangeLog:
* rust/compile/nr2/exclude: nr2 is crashing here
* rust/compile/issue-2951.rs: New test.
Signed-off-by: Philip
From: Arthur Cohen
gcc/rust/ChangeLog:
* resolve/rust-finalize-imports-2.0.cc (FinalizeImports::go): Turn
static method into method.
(FinalizeImports::visit): New.
* resolve/rust-finalize-imports-2.0.h (class FinalizeImports): Make
FinalizeImports a visito
From: Arthur Cohen
gcc/rust/ChangeLog:
* resolve/rust-late-name-resolver-2.0.cc (Late::visit): Add debug call.
* resolve/rust-toplevel-name-resolver-2.0.cc (TopLevel::visit): Store
imports using the new classes.
* resolve/rust-toplevel-name-resolver-2.0.h: Use new
From: Pierre-Emmanuel Patry
We want to begin experimenting with this new name resolution 2.0
algorithm as soon as possible. This test highlight a problem where the
compiler should emit an error and should be fixed soon.
gcc/testsuite/ChangeLog:
* rust/compile/name_resolution21.rs: Move
On Wed, Mar 19, 2025 at 12:04:05PM -0500, Robert Dubner wrote:
> This message appears to have been posted twice, and I don't see a [PATCH
> 1/2]
One copy went to you, one to gcc-patches, which is why you got two copies.
The 1/2 patch was
https://gcc.gnu.org/pipermail/gcc-patches/2025-March/678260
From: Arthur Cohen
gcc/rust/ChangeLog:
* resolve/rust-toplevel-name-resolver-2.0.cc: Comment out handle_use
call and error emission.
* resolve/rust-toplevel-name-resolver-2.0.h: Create ImportKind class.
---
.../rust-toplevel-name-resolver-2.0.cc| 37 +++-
Previously we optimized expressions of the form a < 0 ? -1 : 0 to
(signed)a >> 31 during vcond expanding. Since r15-1638-gaac00d09859cc5
this is done in match.pd. The implementation in the back end as well as
in match.pd are basically the same but still distinct. For the tests in
vcond-shift.c t
From: Owen Avery
gcc/rust/ChangeLog:
* util/optional.h
(optional): Add assertions to dereference operator overloads
when C++14 is available.
Signed-off-by: Owen Avery
---
gcc/rust/util/optional.h | 86
1 file changed, 79 inserti
From: Arthur Cohen
gcc/rust/ChangeLog:
* resolve/rust-early-name-resolver-2.0.cc (Early::visit_attributes):
Store errors for later.
---
gcc/rust/resolve/rust-early-name-resolver-2.0.cc | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/gcc/rust/r
From: "benjamin.thos"
add a resolve expr visitor on error propagation to avoid internal
compiler error when used with generics
gcc/rust/ChangeLog:
* resolve/rust-ast-resolve-expr.cc (ResolveExpr::visit): Add
implementation of error propagation visitor
* resolve/rust-ast-
From: Owen Avery
gcc/rust/ChangeLog:
* backend/rust-compile-expr.cc
(CompileExpr::visit): Use name resolver 2.0 to lookup label
definitions for break and continue statements when name
resolution 2.0 is enabled.
Signed-off-by: Owen Avery
---
gcc/rust/backend/rus
From: badumbatish
gcc/rust/ChangeLog:
* backend/rust-compile-asm.cc (CompileAsm::asm_construct_inputs):
Provide input operand for gccrs
* expand/rust-macro-builtins-asm.cc (parse_reg_operand_in):
Move expr to In
(expand_inline_asm_strings):
Add com
From: Arthur Cohen
This commit adds basic handling for the `#[prelude_import]` attribute,
without doing anything functionality wise.
gcc/rust/ChangeLog:
* checks/errors/rust-feature-gate.cc (FeatureGate::visit): Add base
feature gating for `#[feature(prelude_import)]`.
*
From: JoanVC
Fixes gccrs#3141.
gcc/rust/ChangeLog:
* backend/rust-compile-expr.cc: Fix range checking for both integers
and floats.
* hir/tree/rust-hir-expr.h: Add "negative_number" boolean to
LiteralExpr class.
gcc/testsuite/ChangeLog:
* rust/compile/issue-3141.rs:
From: Arthur Cohen
This could trigger an assertions as `get_type` on `SelfParam` asserts that
the self param does have a given type, which is not always the case.
gcc/rust/ChangeLog:
* resolve/rust-default-resolver.cc (DefaultResolver::visit): Do not
visit self's type if it does
From: Kushal Pal
gcc/rust/ChangeLog:
* checks/errors/borrowck/rust-bir-builder-expr-stmt.cc
(ExprStmtBuilder::visit): Use strong type as index and
remove access to numeric value.
* checks/errors/borrowck/rust-bir-builder-internal.h
(struct BuilderContext):
From: Arthur Cohen
This method was used only for stripping PathPattern AST nodes during
`cfg-strip`, which seems like a misnomer and makes it a good candidate
for simplification.
gcc/rust/ChangeLog:
* ast/rust-path.h (class PathInExpression): Remove `remove_all_segments`
method,
From: badumbatish
gcc/rust/ChangeLog:
* backend/rust-compile-asm.cc (strip_double_quotes):
Move strip double quotes to parse phase
(CompileAsm::asm_construct_string_tree): Likewise
* backend/rust-compile-asm.h (strip_double_quotes): Likewise
* expand/rust-
From: Owen Avery
This may load conditionally compiled modules too eagerly.
gcc/rust/ChangeLog:
* resolve/rust-toplevel-name-resolver-2.0.cc
(TopLevel::visit): Load unloaded modules before attempting to
visit their items.
gcc/testsuite/ChangeLog:
* rust/compile/
From: Owen Avery
gcc/rust/ChangeLog:
* typecheck/rust-hir-type-check-enumitem.cc: Add includes.
(TypeCheckEnumItem::visit): Fetch canonical paths properly when
name resolution 2.0 is enabled.
* typecheck/rust-hir-type-check-implitem.cc: Add includes.
(Type
1 - 100 of 221 matches
Mail list logo
