This libgo patch avoids the libc memmove and memclr functions when the
type being moved or cleared may contain pointer values. This is
necessary to ensure that Go's concurrent garbage collector doesn't see
corrupt pointer values.
The libc memmove and memclr don't reliably operate on full memory
wo
This libgo patch passe the correct pointer to the system call in
recvmsgRaw. The code in recvmsgRaw, introduced in CL 384695
(https://gcc.gnu.org/pipermail/gcc-patches/2022-February/590289.html),
incorrectly passed &rsa to the recvmsg system call. But in recvmsgRaw
rsa is already a pointer passed b
Drop down from SVE2 to SVE1 as that's the minimum
required for the test, and since it's a mid-end test
add the aarch64_sve_hw check.
Regtested on aarch64-none-linux-gnu and no issues.
committed to master.
Thanks,
Tamar
gcc/testsuite/ChangeLog:
PR tree-optimization/120817
* gcc.
This fixes a small typo in the Label attributes docs.
Committed as obvious.
Thanks,
Tamar
gcc/ChangeLog:
* doc/extend.texi: Fix typo in unsed attribute docs.
---
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index
69c6512074642ece47f1f9a3d7bdde20ec800d40..6e80ef8a2055c2015973
This was a followup to make the error message a little better.
Committed.
commit c69afa2f1bd7455457ab4e028a6bc51211b2dd20 (HEAD -> master,
origin/master, origin/HEAD)
Author: Jerry DeLisle
Date: Thu May 29 10:02:00 2025 -0700
Fortran: Make minor adjustment to error message.
MAINTAINERS: Update my email address
2025-05-09 Peter Bergner
/
* MAINTAINERS: Update my email address and add myself to DCO.
Signed-off-by: Peter Bergner
---
MAINTAINERS | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index b1e7fadf1
Dear all,
the attached patch fixes a 15/16 regression for parsing DO CONCURRENT
when there was another statement following on the same line after a
semicolon, because gfc_match_eos was called twice instead of just once.
The patch was OK'ed by Jerry in the PR, regtested and pushed to mainline
so
---
htdocs/gcc-15/changes.html | 23 ++-
1 file changed, 22 insertions(+), 1 deletion(-)
diff --git a/htdocs/gcc-15/changes.html b/htdocs/gcc-15/changes.html
index f112af58..d851a744 100644
--- a/htdocs/gcc-15/changes.html
+++ b/htdocs/gcc-15/changes.html
@@ -1295,7 +1295,28 @
Hi All,
When the input is already a subreg and we try to make a paradoxical
subreg out of it for copysign this can fail if it violates the subreg
relationship.
Use force_lowpart_subreg instead of lowpart_subreg to then force the
results to a register instead of ICEing.
Bootstrapped Regtested on
Hi All,
These loops will now vectorize the entry finding
loops. As such we get more failures because they
were not expecting to be vectorized.
Fixed by adding #pragma GCC novector.
Bootstrapped Regtested on aarch64-none-linux-gnu,
arm-none-linux-gnueabihf, x86_64-pc-linux-gnu
-m32, -m64 and no
On Thu, Jan 30, 2025 at 3:23 PM Ian Lance Taylor wrote:
>
> This patch from pgerell at GitHub adds some casts to libbacktrace to
> avoid undefined shifts. These shifts are OK on all real systems but
> may as well get it right. Bootstrapped and ran libbacktrace tests on
> x86_64-pc-linux-gnu. Commi
I pushed the following fix as obvious after testing the build and verifying
the warning was silenced.
Peter
rs6000: Add cast to avoid pointer to integer comparison warning [PR117674]
libgcc/
PR target/117674
* config/rs6000/linux-unwind.h (ppc_backchain_fallback): Add cast to
This patch updates the attributes for the relatively few builtin
functions defined by the Go frontend to the current ones in
builtins.def. This fixes PR 118746. Bootstrapped and ran Go
testsuite on x86_64-pc-linux-gnu. Committed to mainline.
Ian
PR go/118746
* go-gcc.cc (class Gcc_backend): De
Add a test for the target independent bug, PR rtl-optimization/111673.
PR rtl-optimization/111673
* gcc.target/i386/pr111673.c: New file.
--
H.J.
From 149da4e8927509a4e72eb01ee8277b6952757c7c Mon Sep 17 00:00:00 2001
From: "H.J. Lu"
Date: Sun, 2 Feb 2025 06:46:29 +0800
Subject: [PATCH] x86: Add
Update
commit dd6247cb8fc11a15e23e949092f89d24ff329209
Author: H.J. Lu
Date: Fri Jan 31 12:29:04 2025 +0800
x86: Handle TARGET_INDIRECT_BRANCH_REGISTER for -fno-plt
to change "if (TARGET_X32 ...)" back to "else if (TARGET_X32 ...)".
PR target/118713
* config/i386/i386-expand.cc (ix86_exp
This patch from pgerell at GitHub adds some casts to libbacktrace to
avoid undefined shifts. These shifts are OK on all real systems but
may as well get it right. Bootstrapped and ran libbacktrace tests on
x86_64-pc-linux-gnu. Committed to mainline.
Ian
libbacktrace: add casts to avoid undefined
Dear all,
I've pushed the following minor improvement of an error message
as suggested by the reporter as obvious after regtesting in the
gfortran.dg/gomp subdirectory.
Thanks,
Harald
From 96f4ba4d19a765902af7b79aa77d52c62fa2f82c Mon Sep 17 00:00:00 2001
From: Harald Anlauf
Date: Mon, 20 Jan 2
Dear all,
I've committed the attached obvious patch to reject an invalid NULL
in ALLOCATE after it was OK'ed in the PR by Steve.
Regtested on x86_64-pc-linux-gnu. Pushed as r15-6925-g892304f1fe .
Thanks,
Harald
From 892304f1fe3e808b9f498353c144f1ae0591 Mon Sep 17 00:00:00 2001
From: H
PR 118286 points out that some libgo tests are starting to fail
because they use test certificates that expired on January 1. This
libgo patch is a backport of https://go.dev/cl/640237 in the main
repo. It uses the existing config.Time field to avoid these test
failures. Bootstrapped and ran Go t
PR 117812 reports a libbacktrace test failure when building with a
2018 version of zstd, because ZSTD_CLEVEL_DEFAULT is not defined.
This patch avoids using it, replacing it with the default value 3.
The test doesn't really care what compression level is used anyhow.
Bootstrapped and ran libbacktra
This patch to the Go frontend changes traversal to always traverse
method declarations (method definitions were already traversed). This
removes one existing case that explicitly traversed method
declarations, in favor of the common approach.
Note that the gc Go compiler rejects method declaratio
The libbacktrace code accidentally use WIN32_MEAN_AND_LEAN when it
should have use WIN32_LEAN_AND_MEAN. This was pointed out by awmorgan
on GitHub. I've committed this patch to fix it.
Ian
* fileline.c: Use WIN32_LEAN_AND_MEAN, not WIN32_MEAN_AND_LEAN.
* pecoff.c: Likew
This patch to the Go frontend increases the size of a temporary buffer
to avoid a new warning. The warning was breaking bootstrapping with
Go.
GCC has a new -Wformat-truncation warning that triggers on some Go
frontend code:
../../gcc/go/gofrontend/go-encode-id.cc: In function 'std::string
go_en
As requested by the Debian security team.
* SECURITY.txt: Remove Debian.
---
SECURITY.txt | 1 -
1 file changed, 1 deletion(-)
diff --git a/SECURITY.txt b/SECURITY.txt
index 126603d4c22..b38425ea223 100644
--- a/SECURITY.txt
+++ b/SECURITY.txt
@@ -180,7 +180,6 @@ Reporting private secur
After commit 8833389e90d676baabb35c3e7a021a4f5444a5ba.
gcc/c-family/
* c.opt.urls: Regenerate.
---
gcc/c-family/c.opt.urls | 3 +++
1 file changed, 3 insertions(+)
diff --git a/gcc/c-family/c.opt.urls b/gcc/c-family/c.opt.urls
index 3bfe2b86b24..04f8e2ee008 100644
--- a/gcc/c-family/c.
Hi all,
Looks like this immediate variable was missed out when I last fixed the
namespace issues in arm_neon.h. Fixed in the obvious manner.
Bootstrapped and tested on aarch64-none-linux-gnu.
Pushing to trunk.
Thanks,
Kyrill
Signed-off-by: Kyrylo Tkachov
* config/aarch64/arm_neon.h (vxarq_u
This patch by Pavel Safonov recognizes the new DWARF section names
used on macos Sequoia. Bootstrapped and ran libbacktrace tests on
x86_64-pc-linux-gnu. Committed to mainline.
Ian
* macho.c (dwarf_section_names): Add __debug_addr and
__debug_line_str.
d97243588c8b5cbe8b657fd51f08038c42c81908
d
Because libbacktrace merges adjacent address ranges where possible,
and because the GNU linker can deduplicate functions leaving debuginfo
that refers to address ranges in other compilation units, it is
possible for libbacktrace to have overlapping address ranges, in
particular to overlap ranges wi
PR ipa/111613
* gcc.c-torture/pr111613.c: Rename to..
* gcc.c-torture/execute/pr111613.c: ...this.
(cherry picked from commit 5e5d7a88932b132437069f716160f8b20862890b)
---
I actually thought I'd backported this already. Pushed as obvious, as
the test issue was only introduc
Dear all,
I've pushed the attached simple patch for initialization of local variables
to silence warnings for LTO builds after Sam James' confirmation as
https://gcc.gnu.org/g:2b23a444bcf7eb67cb04b431d8fd4fa6f65222de
Thanks,
Harald
From 2b23a444bcf7eb67cb04b431d8fd4fa6f65222de Mon Sep 17 00:00:
Hi all,
The constraint Dm is intended to match vectors of minus 1, but actually
checks for CONST1_RTX. This doesn't have a bad effect in practice as its
only use in the aarch64_wrffr pattern for the setffr instruction which
is a VNx16BI operation and -1 and 1 are the same there. That pattern
can o
This patch to the Go frontend avoids assuming that ATTRIBUTE_UNUSED is
defined. While it is defined when building the Go frontend as part of
GCC, it is meant to work with other compilers as well. Bootstrapped
and ran Go testsuite on x86_64-pc-linux-gnu. Committed to mainline.
Ian
e89ddb749517ea
This patch, based on one by Kirill Müller, adds -Wpointer-arith to the
libbacktrace warning options, and adds casts to avoid the cases where
the warning currently fires. Bootstrapped and ran libbacktrace
testsuite on x86_64-pc-linux-gnu. Committed to mainline.
Ian
* configure.ac (ACX_PROG_CC_WA
This patch to the Go frontend determines that panic arguments are
empty interfaces. After https://go.dev/cl//536643 passing NULL as the
expected type permitted an untyped constant expression to remain
untyped. This change will fix them to take on the empty interface
type.
The panic and print/prin
This libbacktrace patch uses __has_attribute for fallthrough. It also
fixes some FALLTHROUGH comments to use ATTRIBUTE_FALLTHROUGH.
Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed
to mainline.
Ian
* internal.h: Use __has_attribute to check for fallthrough
attribute.
* elf.c
On Wed, Jul 17, 2024 at 5:40 PM Ian Lance Taylor wrote:
>
> This libbacktrace patch improves backtrace_print when there is no
> debug info. It falls back to calling backtrace_syminfo, and uses that
> to print an offset from a symbol if it can. This is a partial fix for
> https://github.com/ianla
This libbacktrace patch improves backtrace_print when there is no
debug info. It falls back to calling backtrace_syminfo, and uses that
to print an offset from a symbol if it can. This is a partial fix for
https://github.com/ianlancetaylor/libbacktrace/issues/59.
Bootstrapped and ran libbacktrace
This patch adds some notes about dl_iterate_phdr to the libbacktrace
README file. In general dl_iterate_phdr is not async-signal-safe and
does call malloc, so programs that want to use libbacktrace functions
from a signal handler or within malloc must make an initiali
libbacktrace call in order to
libbacktrace could get an infinite recursion in an odd case in which a
.gnu_debugdata section was added to a debug file, and mini_debuginfo
was put into the debug file, and the debug file was put into a
/usr/lib/debug directory to be found by build ID. This combination
doesn't really make sense bu
Mach-O and PE/COFF don't record symbol sizes in the symbol table.
Adjust the libbacktrace testsuite so that it doesn't fail if the
symbol size is unknown, only if it is incorrect. Ran libbacktrace
tests on macOS on the compile farm and on x86_64-pc-linux-gnu.
Committed to mainline.
Ian
The libbacktrace symbol table code was incorrectly discarding global
Mach-O symbols. This patch fixes the problem. Tested on macOS on the
compile farm, and also on x86_64-pc-linux-gnu. Committed to mainline.
Ian
For PR libbacktrace/97082
* macho.c (MACH_O_N_EXT): Don't
On Thu, Jul 11, 2024 at 7:19 PM Andrew Pinski wrote:
>
> On Thu, Jul 11, 2024 at 4:14 PM Ian Lance Taylor wrote:
> >
> > The libbacktrace testsuite was not passing when run with current
> > versions of clang. Add the optnone attribute to make it pass. Add
> > -Wno-attributes and -Wno-unknown-at
On Thu, Jul 11, 2024 at 4:18 PM Andrew Pinski wrote:
>
> On Thu, Jul 11, 2024 at 4:14 PM Ian Lance Taylor wrote:
> >
> > The libbacktrace testsuite was not passing when run with current
> > versions of clang. Add the optnone attribute to make it pass. Add
> > -Wno-attributes and -Wno-unknown-at
On Thu, Jul 11, 2024 at 4:14 PM Ian Lance Taylor wrote:
>
> The libbacktrace testsuite was not passing when run with current
> versions of clang. Add the optnone attribute to make it pass. Add
> -Wno-attributes and -Wno-unknown-attributes to disable warnings about
> unrecognized function attribu
The libbacktrace testsuite was not passing when run with current
versions of clang. Add the optnone attribute to make it pass. Add
-Wno-attributes and -Wno-unknown-attributes to disable warnings about
unrecognized function attributes. Bootstrapped and ran libbacktrace
testsuite on x86_64-pc-linu
This small libbacktrace patch suggests compiling with -g (and, on
macOS, running dsymutil), if there is no debug info. Ran libbacktrace
testsuite. Committed to mainline.
Ian
* elf.c (elf_nodebug): Suggest -g.
* macho.c (macho_nodebug): Suggest -g and dsymutil.
This minor libbacktrace patch removes trailing whitespace. Ran
libbacktrace tests. Committed to mainline.
Ian
* dwarf.c: Remove trailing whitespace.
* macho.c: Likewise.
3f660179d6a0ebcd83d6a546f48a163d1a685f72
diff --git a/libbacktrace/dwarf.c b/libbacktrace/dwarf.c
index ed067
Hi All,
The PR was about SVE codegen, the testcase accidentally used neoverse-n1
instead of neoverse-v1 as was the original report.
This updates the tool options.
Regtested on aarch64-none-linux-gnu and no issues.
committed under the obvious rule.
Thanks,
Tamar
gcc/testsuite/ChangeLog:
>> Hmm, now all avx512 tests SIGILL when testing with -m32:
>>
>> Dump of assembler code for function __get_cpuid_count:
>> => 0x08049500 <+0>: kmovd %eax,%k2
>> 0x08049504 <+4>: kmovd %edx,%k1
>> 0x08049508 <+8>: pushf
>> 0x08049509 <+9>: pushf
>> 0x0804950a <+10>:
On Thu, Jul 4, 2024 at 9:41 AM H.J. Lu wrote:
>
>
> On Thu, Jul 4, 2024, 9:12 AM Hongtao Liu wrote:
>>
>> On Thu, Jul 4, 2024 at 6:17 AM H.J. Lu wrote:
>> >
>> >
>> > On Wed, Jul 3, 2024, 9:37 PM Richard Biener
>> > wrote:
>> >>
>> >> On Wed, Jul 3, 2024 at 9:25 AM liuhongt wrote:
>> >> >
>>
On Thu, Jul 4, 2024, 9:12 AM Hongtao Liu wrote:
> On Thu, Jul 4, 2024 at 6:17 AM H.J. Lu wrote:
> >
> >
> > On Wed, Jul 3, 2024, 9:37 PM Richard Biener
> wrote:
> >>
> >> On Wed, Jul 3, 2024 at 9:25 AM liuhongt wrote:
> >> >
> >> > The patch can avoid SIGILL on non-AVX512 machine due to kmovd
On Thu, Jul 4, 2024 at 6:17 AM H.J. Lu wrote:
>
>
> On Wed, Jul 3, 2024, 9:37 PM Richard Biener
> wrote:
>>
>> On Wed, Jul 3, 2024 at 9:25 AM liuhongt wrote:
>> >
>> > The patch can avoid SIGILL on non-AVX512 machine due to kmovd is
>> > generated in dynamic check.
>> >
>> > Committed as an obv
On Wed, Jul 3, 2024, 9:37 PM Richard Biener
wrote:
> On Wed, Jul 3, 2024 at 9:25 AM liuhongt wrote:
> >
> > The patch can avoid SIGILL on non-AVX512 machine due to kmovd is
> > generated in dynamic check.
> >
> > Committed as an obvious fix.
>
> Hmm, now all avx512 tests SIGILL when testing with
On Wed, Jul 3, 2024 at 9:25 AM liuhongt wrote:
>
> The patch can avoid SIGILL on non-AVX512 machine due to kmovd is
> generated in dynamic check.
>
> Committed as an obvious fix.
Hmm, now all avx512 tests SIGILL when testing with -m32:
Dump of assembler code for function __get_cpuid_count:
=> 0x
The patch can avoid SIGILL on non-AVX512 machine due to kmovd is
generated in dynamic check.
Committed as an obvious fix.
gcc/testsuite/ChangeLog:
PR target/115748
* gcc.target/i386/avx512-check.h: Move runtime check into a
separate function and guard it with target ("no-
Fix test for APX ZU. Add attribute for no-inline and target APX, and
target-support check.
Bootstrapped and regtested on x86_64-pc-linux-gnu{-m32,}.
Committed as an obvious patch.
gcc/testsuite/ChangeLog:
* gcc.target/i386/apx-zu-1.c: Add attribute for noinline,
I've committed this libbacktrace patch to not fail on the case where
there are no bits available when looking backward. This can happen at
the very end of the frame if no bits are actually required. The test
case is long and may be proprietary, so not including it.
Bootstrapped and ran libbacktra
Use reg_or_subregno instead.
Bootstrapped and regtested on x86_64-pc-linux-gnu{-m32,}.
Committed as an obvious patch.
gcc/ChangeLog:
PR target/115452
* config/i386/i386-features.cc (scalar_chain::convert_op): Use
reg_or_subregno instead of REGNO to avoid ICE.
gcc/testsui
gcc/testsuite/ChangeLog:
* gcc.dg/vect/pr112325.c:Add additional option --param
max-completely-peeled-insns=200 for power64*-*-*.
---
gcc/testsuite/gcc.dg/vect/pr112325.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/gcc/testsuite/gcc.dg/vect/pr112325.c
b/gcc/testsuite/gcc.
For power10, there're extra 3 REG_EQUIV notes with (fix:SI. to avoid
the failure. Check (fix:SI is from the pattern not NOTE.
gcc/testsuite/ChangeLog:
PR target/115365
* gcc.dg/pr100927.c: Don't scan fix:SI from the note.
---
gcc/testsuite/gcc.dg/pr100927.c | 2 +-
1 file changed
When I applied Roger's patch [1], there's ICE due to it.
The patch fix the latent bug.
[1] https://gcc.gnu.org/pipermail/gcc-patches/2024-May/651365.html
Bootstrapped and regtested on x86_64-pc-linux-gnu{-m32,}.
Pushed to trunk.
gcc/ChangeLog:
* config/i386/sse.md
(___mask): Ali
Dear all,
the attached obvious patch fixes a frontend memleak that was introduced
recently, and which shows up when checking for inquiry references.
I came across it when working on pr115039.
Committed after regtesting as r15-391-g13b6ac4ebd04f0.
Thanks,
Harald
From 13b6ac4ebd04f0703d92828c9268
This libgo patch changes runtime/runtime.h to use the C99
header file rather than defining a bool type and true/false constants
itself. C99 was a long time ago and in case this file is always
compiled by the newly built GCC. This should fix GCC PR 114875.
Bootstrapped on x86_64-pc-linux-gnu. Co
I spotted this whitespace error during the review of
https://gcc.gnu.org/pipermail/gcc-patches/2024-April/648846.html.
Pushing as obvious after testing on aarch64-linux-gnu.
Thanks,
Alex
gcc/ChangeLog:
* config/aarch64/aarch64-ldp-fusion.cc (struct alias_walker):
Fix double spac
This patch to the Go frontend uses the correct size and comparison
when doing an index value overflow check. This has apparently been
wrong since I introduced the code ten years ago. This fixes GCC PR
114500. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu.
Committed to mainline.
Ian
1
This patch to the Go testsuite updates issue16016.go. This backports
https://go.dev/cl/574536 into the GCC testsuite. This fixes PR
go/114453. Bootstrapped and ran test. Committed to mainline.
Ian
5b6f599670994bef957bd15c683102468a7104f1
diff --git a/gcc/testsuite/go.test/test/fixedbugs/issue1
This patch to the Go frontend fixes an uninitialized variables in
lower_method_expression. This fixes GCC PR 114463. Bootstrapped and
ran Go testsuite on x86_64-pc-linux-gnu. Committed to mainline.
Ian
7b2a24f3964509bd5b74c4579c7ea5684e82aee1
diff --git a/gcc/go/gofrontend/MERGE b/gcc/go/gofron
Dear all,
I've committed the attached simple & obvious patch for an ICE due to
an invalid read in frontend optimization after regtesting and an OK
by Jerry in the PR.
Pushed: https://gcc.gnu.org/g:3be2b8f475f22c531d6cef1b041c0573b3ea5133
As this PR is marked as a regression, I plan to backport t
Hi All,
This is a backport of g:306713c953d509720dc394c43c0890548bb0ae07.
The AArch64 vector PCS does not allow simd calls with simdlen 1,
however due to a bug we currently do allow it for num == 0.
This causes us to emit a symbol that doesn't exist and we fail to link.
Bootstrapped Regtested o
On Fri, Mar 8, 2024 at 2:48 PM Fangrui Song wrote:
>
> On ELF64, it looks like BFD uses 8-byte alignment for compressed
> `.debug_*` sections while gold/lld/mold use 1-byte alignment. I do not
> know how the Solaris linker sets the alignment.
>
> The specification's wording makes me confused wheth
On ELF64, it looks like BFD uses 8-byte alignment for compressed
`.debug_*` sections while gold/lld/mold use 1-byte alignment. I do not
know how the Solaris linker sets the alignment.
The specification's wording makes me confused whether it really
requires 8-byte alignment, even if a non-packed `E
Reportedly when lld compresses debug sections, it fails to set the
alignment of the compressed section such that the compressed header
can be read directly. To me this seems like a bug in lld. However,
libbacktrace needs to work around it. This patch, originally by the
GitHub user ubyte, does th
Some of the libbacktrace tests link a program and then modify the
debug info in some way. When configured with --enable-shared the
linking, using libtool, generates a shell script. That causes the
tests to fail because they can't modify the debug info of a shell
script. This patch, originally by
This patch to libbacktrace corrects the LZMA block header parsing to
skip all the padding bytes, verifying that they are zero. This fixes
https://github.com/ianlancetaylor/libbacktrace/issues/118.
Bootstrapped and ran libbacktrace tests on x86_64-pc-linux-gnu. I was
able to verify that the proble
On Thu, Feb 29, 2024 at 7:47 PM Ian Lance Taylor wrote:
>
> This patch to libbacktrace reads symbol tables from debuginfo files.
> These become another symbol table to search. This is needed if people
> use --strip-all rather than --strip-debug when adding a debuglink
> section. This fixes
> htt
This patch to libbacktrace reads symbol tables from debuginfo files.
These become another symbol table to search. This is needed if people
use --strip-all rather than --strip-debug when adding a debuglink
section. This fixes
https://github.com/ianlancetaylor/libbacktrace/issues/113.
Bootstrapped
Hi All,
I had missed a conversion from unsigned long to uint64_t.
This fixes the failing test on -m32.
Regtested on x86_64-pc-linux-gnu with -m32 and no issues.
Committed as obvious.
Thanks,
Tamar
gcc/testsuite/ChangeLog:
* gcc.dg/vect/vect-early-break_110-pr113467.c: Change unsigned
This libgo patch bumps the version number for the GCC 14 release.
This is for GCC PR 113668. Bootstrapped and ran Go testsuite on
x86_64-pc-linux-gnu. Committed to mainline.
Ian
7b0597eba6b29387b56b8d6a4b38f3586e6b49a5
diff --git a/gcc/go/gofrontend/MERGE b/gcc/go/gofrontend/MERGE
index ec7e2ab1
This patch to the Go frontend adds Type::message_name to print types
in ways that makes sense to users. As we move toward generics, the
error messages need to be able to refer to types in a readable manner.
Today we use this new feature in AST dumps. Bootstrapped and ran Go
testsuite on x86_64-pc
This libgo patch generates better error messages then the Go GOARCH
and GOOS values can't be determined from the target. This indicates
that the target is not supported. This is for GCC PR 113530.
Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed
to mainline.
Ian
cfc6d9ae8143c
This patch to the Go frontend exports the type "any" as a builtin.
Otherwise we can't tell the difference between builtin type "any" and
a locally defined type "any".
This will require updates to the gccgo export data parsers in the main
Go repo and the x/tools repo. These updates are https://go.
Dear all,
commit r11-1235 for pr95331 addressed array bounds issues with
unlimited polymorphic array dummies, but caused regressions for
CLASS array dummies that lead to either wrong code with bounds-checking,
or an ICE. The solution is simple: add a check whether the dummy
is unlimited polymorph
This patch to the Go frontend stops passing the iota value to the
lowering pass. It is no longer used. The iota value is now handled
in the determine-types pass. Bootstrapped and ran Go testsuite on
x86_64-pc-linux-gnu. Committed to mainline.
Ian
896148947b9ff4845c8bc334f8eff30f91ff3c9a
diff -
Dear all,
I've pushed the attached obvious patch for a regression due to a
wrong array bounds check after regtesting on x86_64-pc-linux-gnu
and verification of the fix by the reporter in the PR.
https://gcc.gnu.org/g:94b2e6cb1cc4feb122bf77f19a657c97bffa9b42
Thanks,
Harald
From 94b2e6cb1cc4feb12
On Mon, Dec 18, 2023 at 5:32 PM Ian Lance Taylor wrote:
>
> This Go frontend patch moves the lowering pass after the type
> determination and the type checking passes. This lets us simplify
> some of the code that determines the type of an expression, which
> previously had to work correctly both
Hi All,
Should control enter the switch from one of the cases other than
the IVDEP one then the variable remains uninitialized.
This fixes it by initializing it to false.
Bootstrapped Regtested on aarch64-none-linux-gnu, x86_64-pc-linux-gnu
and no issues
Committed as obvious.
Thanks,
Tamar
gc
Hi All,
It looks like the previous patch had an unused variable.
It's odd that my bootstrap didn't catch it (I'm assuming
-Werror is still on for O3 bootstraps) but this fixes it.
Committed to fix bootstrap.
Thanks,
Tamar
gcc/ChangeLog:
* tree-vect-loop.cc (vectorizable_live_operation_
Dear all,
I've committed the attached, simple & obvious patch for a
gmp memory leak in gfc_get_nodesc_array_type that shows
up when running f951 under valgrind e.g. on testcase
gfortran.dg/class_optional_2.f90, after regtesting on
x86_64-pc-linux-gnu.
(Note that this does not address the underlyi
Hi All,
when configured with --enable-checking=release we get a false
positive on the use of vec_stmts as the compiler seems unable
to notice it gets initialized through the pass-by-reference.
This explicitly initializes the local.
Bootstrapped Regtested on x86_64-pc-linux-gnu and no issues.
Co
This Go frontend patch moves the lowering pass after the type
determination and the type checking passes. This lets us simplify
some of the code that determines the type of an expression, which
previously had to work correctly both before and after type
determination.
I'm doing this to help with
gcc/testsuite/
* gcc.c-torture/execute/931004-13.c (main): Fix mistakenly swapped
int/void types.
---
gcc/testsuite/gcc.c-torture/execute/931004-13.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gcc/testsuite/gcc.c-torture/execute/931004-13.c
b/gcc/tes
This patch to the Go frontend just moves Selector_expression up in
file. This is a mechanical change to expressions.cc. This will make
Selector_expression visible to Builtin_call_expression for later work.
This produces a very large "git --diff", but "git diff --minimal" is
clear. Bootstrapped a
This patch to the Go frontend changes the Expression
{numeric,string,boolean}_constant_value methods to be non-const. This
does not affect anything immediately, but will be useful for later CLs
in this series.
The only real effect is to Builtin_call_expression::do_export, which
remains const and
This Go frontend patches passes the Gogo IR pointer to
Runtime::make_call. This is a boilerplate change that doesn't affect
compiler output. It's not currently used but will be used by later
CLs in this series. Bootstrapped and ran Go testsuite on
x86_64-pc-linux-gnu. Committed to mainline.
Ia
This Go frontend patches adds an Expression::is_untyped method. This
method is not currently used by anything, but it will be used by later
changes in this series. Bootstrapped and ran Go testsuite on
x86_64-pc-linux-gnu. Committed to mainline.
Ian
ac50e9b72bf9bb6d5b28096bb164fb050db6e290
diff
This libgo patch adds a missing type conversion. The gofrontend
incorrectly accepted code that was missing a type conversion. The
test case for this is bug518.go in https://go.dev/cl/536537. Future
CLs in this series will detect the type error. Bootstrapped and ran
Go testsuite on x86_64-pc-lin
This patch to the Go frontend removes the traverse_assignments
support. The last caller was removed in https://go.dev/cl/18261 in
2016. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu.
Committed to mainline.
Ian
a6e74b0b3316f3f0b2096d6a175c31bed58ae4ed
diff --git a/gcc/go/gofrontend/MER
This patch to the Go frontend removes the name_ field from the
Type_switch_statement class. It's not used for anything.
Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed
to mainline.
Ian
1a1fba1e25779247a4969789885ce80b7b4a2359
diff --git a/gcc/go/gofrontend/MERGE b/gcc/go/gofr
This patch to the G frontend passes a pointer to the Gogo IR to the
determine types pass and the type verification pass. This is a
straight refactoring that does not change the compiler behavior. This
is in preparation for future CLs that rearrange the pass ordering.
This introduces one new call
ChangeLog:
* Makefile.def: Add distclean-sim dependency on distclean-gnulib.
* Makefile.in: Regenerate.
---
Makefile.def | 1 +
Makefile.in | 1 +
2 files changed, 2 insertions(+)
diff --git a/Makefile.def b/Makefile.def
index 870150183b9a..15c068e4ac40 100644
--- a/Makefile.def
1 - 100 of 1030 matches
Mail list logo
