[Bug middle-end/95189] [9/10 Regression] memcmp being wrongly stripped like strcmp

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189 Davin McCall changed: What|Removed |Added CC||davmac at davmac dot org --- Comment #28

[Bug fortran/98490] Unexpected out of bounds in array constructor with implied do loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98490 --- Comment #6 from Steve Kargl --- On Sat, Jan 02, 2021 at 04:12:27AM +, jvdelisle at charter dot net wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98490 > > --- Comment #5 from Jerry DeLisle --- > Patch regresses several test

[Bug fortran/98490] Unexpected out of bounds in array constructor with implied do loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98490 --- Comment #5 from Jerry DeLisle --- Patch regresses several test cases.

[Bug fortran/98490] Unexpected out of bounds in array constructor with implied do loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98490 Jerry DeLisle changed: What|Removed |Added CC||jvdelisle at charter dot net ---

[Bug tree-optimization/98497] New: [Potential Perf regression] jne to hot branch instead je to cold

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98497 Bug ID: 98497 Summary: [Potential Perf regression] jne to hot branch instead je to cold Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal

Re: Fix testsuite/g++.dg/cpp1y/constexpr-66093.C execution failure...

On Jan 1, 2021, Mike Stump wrote: > On Jan 1, 2021, at 3:37 PM, Alexandre Oliva wrote: >> >> On Dec 29, 2020, Mike Stump wrote: >> >>> a[i-1] = i; >> >> 'fraid that won't pass: >> >> for (int i = 0; i < n; i++) { >> assert (a[i] == i); >> } > Ok, how about your version with the comment

[Bug fortran/96986] [8/9/10/11 Regression] Explicit interface required: volatile argument for ENTRY subroutine

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96986 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org

Re: Fix testsuite/g++.dg/cpp1y/constexpr-66093.C execution failure...

On Jan 1, 2021, at 3:37 PM, Alexandre Oliva wrote: > > On Dec 29, 2020, Mike Stump wrote: > >> a[i-1] = i; > > 'fraid that won't pass: > >for (int i = 0; i < n; i++) { >assert (a[i] == i); >} Ok, how about your version with the comment updated?

Re: libgo patch committed: Update to Go1.16beta1 release

On Fri, Jan 1, 2021 at 3:15 PM Ian Lance Taylor via Gcc-patches wrote: > > As far as I know all the build problems introduced by the update to > Go1.16beta1 are now fixed. > > Please let me know if I missed anything. > You missed this one for x32: diff --git

Re: Fix testsuite/g++.dg/cpp1y/constexpr-66093.C execution failure...

On Dec 29, 2020, Mike Stump wrote: > a[i-1] = i; 'fraid that won't pass: for (int i = 0; i < n; i++) { assert (a[i] == i); } we could make it: a[i-1] = i-1; but... yuck. IMHO it's a lot less surprising to have an init loop that matches the check. >> +++

[Bug bootstrap/98493] [11 regression] bootstrap build fails in go part of build after r11-6371

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98493 Ian Lance Taylor changed: What|Removed |Added CC||ian at airs dot com

[Bug go/98496] [11 Regression] bootstrap broken in libgo on i686-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98496 Ian Lance Taylor changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED

Re: libgo patch committed: Update to Go1.16beta1 release

As far as I know all the build problems introduced by the update to Go1.16beta1 are now fixed. Please let me know if I missed anything. Sorry for the difficulties, it's hard to test on so many systems. Ian On Fri, Jan 1, 2021 at 3:14 PM Ian Lance Taylor wrote: > > On Fri, Jan 1, 2021 at 1:32

[Bug fortran/96986] [8/9/10/11 Regression] Explicit interface required: volatile argument for ENTRY subroutine

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96986 anlauf at gcc dot gnu.org changed: What|Removed |Added Keywords||diagnostic

Re: libgo patch committed: Update to Go1.16beta1 release

On Fri, Jan 1, 2021 at 1:32 AM Andreas Schwab wrote: > > --- a/libgo/go/internal/cpu/cpu_gccgo.c > +++ b/libgo/go/internal/cpu/cpu_gccgo.c > @@ -200,3 +200,29 @@ struct queryResult kdsaQuery() { > } > > #endif /* defined(__s390x__) */ > + > +#ifdef __aarch64__ > + > +uint64_t getisar0(void) >

Re: libgo patch committed: Update to Go1.16beta1 release

On Thu, Dec 31, 2020 at 11:48 AM Rainer Orth wrote: > > > I've committed a patch to update libgo to the Go 1.16beta1 release. > > > > This patch does not include support for the new //go:embed directive > > that will be available in Go 1.16.1 (https://golang.org/issue/41191) > > Support for that

Re: libgo patch committed: Update to Go1.16beta1 release

On Thu, Dec 31, 2020 at 7:40 AM Matthias Klose wrote: > > On 12/31/20 12:14 AM, Ian Lance Taylor via Gcc-patches wrote: > > I've committed a patch to update libgo to the Go 1.16beta1 release. > > > > This patch does not include support for the new //go:embed directive > > that will be available

gcc-9-20210101 is now available

Snapshot gcc-9-20210101 is now available on https://gcc.gnu.org/pub/gcc/snapshots/9-20210101/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 9 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

Time to update all licenses in code to 2021

Update copyright years. · gcc-mirror/gcc@8d9254f (github.com) Sent from Mail for Windows 10

[Bug fortran/96986] [8/9/10/11 Regression] Explicit interface required: volatile argument for ENTRY subroutine

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96986 --- Comment #3 from Fritz Reese --- (In reply to anlauf from comment #2) ... > So I'd say the code in comment#0 is invalid, although the compiler is not > required to diagnose this. > > If you agree, we will close the issue as INVALID. The

Re: A problem with field decl offsets in newly minted types

The offsets seem to actually be created. However, they are almost immediately are being deleted. Any ideas what's going on? Has some kind of memory management gizmo gone awry? Gary PS For anybody who has been following my travails with the instance interleaving structure reorganization

[Bug fortran/89891] [meta-bug] Accessing memory in rejected statements or expressions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89891 Bug 89891 depends on bug 98263, which changed state. Bug 98263 Summary: valgrind error in gfc_find_derived_vtab https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98263 What|Removed |Added

[Bug fortran/96381] gfc_find_vtab can use a character type typespec as a derived type (causing invalid access)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96381 anlauf at gcc dot gnu.org changed: What|Removed |Added CC||dcb314 at hotmail dot com

[Bug fortran/98263] valgrind error in gfc_find_derived_vtab

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98263 anlauf at gcc dot gnu.org changed: What|Removed |Added Resolution|--- |DUPLICATE

[Bug fortran/96986] [8/9/10/11 Regression] Explicit interface required: volatile argument for ENTRY subroutine

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96986 --- Comment #2 from anlauf at gcc dot gnu.org --- F2018 has: ! 15.4.2.2 Explicit interface ! Within the scope of a procedure identifier, the procedure shall have an ! explicit interface if it is not a statement function and ! (3) the procedure

[Bug rtl-optimization/97836] wrong code at -O1 on x86_64-pc-linux-gnu by r11-5029

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97836 Jan Hubicka changed: What|Removed |Added Summary|[11 Regression] wrong code |wrong code at -O1 on

[Bug go/98496] New: [11 Regression] bootstrap broken in libgo on i686-gnu

Component: go Assignee: ian at airs dot com Reporter: doko at debian dot org CC: cmang at google dot com Target Milestone: --- seen with trunk 20210101 ../../../src/libgo/go/runtime/os_gccgo.go:43:12: error: reference to undefined name 'startupRandomData' 43

Re: libgo patch committed: Update to Go1.16beta1 release

../../../../libgo/go/golang.org/x/sys/cpu/cpu.go:200:9: error: reference to undefined name ‘initOptions’ 200 | initOptions() | ^ make[2]: *** [golang.org/x/sys/cpu.lo] Error 1 Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69

[Bug fortran/96381] gfc_find_vtab can use a character type typespec as a derived type (causing invalid access)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96381 --- Comment #4 from CVS Commits --- The master branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:d816b0c144d15e6570eb5b124b9f3ccbe3d40082 commit r11-6405-gd816b0c144d15e6570eb5b124b9f3ccbe3d40082 Author: Harald Anlauf Date:

[PATCH] libstdc++/98466 Fix _GLIBCXX_DEBUG N3644 integration

I think the PR is not limited to unordered containers iterator, it impacts all _GLIBCXX_DEBUG iterators. However unordered containers local_iterator was more complicated to handle. Because of c++/65816 I prefer to review _Node_iterator_default constructor to set _M_cur to nullptr even if in

Re: libgo patch committed: Update to Go1.16beta1 release

../../../libgo/go/internal/cpu/cpu_ppcx.go:13:5: error: redefinition of 'HWCap' 13 | var HWCap uint | ^ ../../../libgo/go/internal/cpu/cpu_ppc64x_linux.go:12:5: note: previous definition of 'HWCap' was here 12 | var HWCap uint | ^

Re: [PATCH] PR fortran/96381 - invalid read in gfc_find_derived_vtab

Hi Harald, It looks good to me - OK for master and backporting. Thanks Paul On Fri, 1 Jan 2021 at 16:14, Harald Anlauf via Fortran wrote: > Dear all, > > happy New Year! > > The testcase committed with the fix for PR93337 uncovered a latent issue > with an invalid read that was discovered

[Bug libstdc++/98473] std::vector::insert(pos, first, last) doesn't compile for T which has a deleted assignment operator

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98473 --- Comment #2 from Borislav Stanimirov --- (In reply to Jonathan Wakely from comment #1) > To meet the requirements of the standard we would need to insert them at the > end and then use std::rotate to reposition them. Or, to save move

[Bug fortran/93794] [8/9/10/11 Regression] ICE in gfc_conv_component_ref, at fortran/trans-expr.c:2497

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93794 --- Comment #7 from anlauf at gcc dot gnu.org --- (In reply to Paul Thomas from comment #6) > Hah! I am probably a week or two from getting to it. I have been working my > way through a backlog but have been held up for some days by unlimited >

[Bug fortran/96381] gfc_find_vtab can use a character type typespec as a derived type (causing invalid access)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96381 anlauf at gcc dot gnu.org changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot

[PATCH] PR fortran/96381 - invalid read in gfc_find_derived_vtab

Dear all, happy New Year! The testcase committed with the fix for PR93337 uncovered a latent issue with an invalid read that was discovered with an ASAN instrumented compiler but which could also be verified by running f951 under valgrind. According to my gdb sessions the invalid read happens

Re: libgo patch committed: Update to Go1.16beta1 release

On 12/31/20 12:14 AM, Ian Lance Taylor via Gcc-patches wrote: > I've committed a patch to update libgo to the Go 1.16beta1 release. > > This patch does not include support for the new //go:embed directive > that will be available in Go 1.16.1 (https://golang.org/issue/41191) > Support for that

[Bug c++/96746] Type Casting in template function should not be type-dependent if the type of the conversion result is not type-dependent.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96746 Masamitsu MURASE changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug target/98495] X86 _mm_extract_pi16 incorrectly sign extends result

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98495 H.J. Lu changed: What|Removed |Added URL||https://gcc.gnu.org/piperma

[PATCH] x86: Cast to unsigned short first for _mm_extract_pi16

_mm_extract_pi16 is intrinsic for pextrw, which should be zero-extended, not sign-extended. gcc/ PR target/98495 * config/i386/xmmintrin.h (_mm_extract_pi16): Cast to unsigned short first. gcc/testsuite/ PR target/98495 * gcc.target/i386/pr98495-1.c: New

[Bug target/98495] X86 _mm_extract_pi16 incorrectly sign extends result

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98495 H.J. Lu changed: What|Removed |Added Ever confirmed|0 |1 CC|

[Bug rtl-optimization/98438] Rather bad optimization of midpoint implementation for __int128 (and other types)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98438 Thomas Koenig changed: What|Removed |Added Status|WAITING |NEW Severity|normal

[Bug sanitizer/98206] UBSan: Casting from multiple inheritance base to derived class triggers undefined behavior sanitizer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98206 --- Comment #6 from Roland B --- Great! This also works well in the original (more complex) scenario (https://github.com/rbock/sqlpp11/issues/355).

[patch, shared memory coarray, committed] Fix SYNC IMAGES(*)

Hi, a rather obvious patch for SYNC IMAGES(*) failing because it did not deal with a -1 argument. Make SYNC IMAGES(*) work by handling size of -1 in library. libgfortran/ChangeLog: * caf_shared/sync.c (sync_table): Change size argument and index to int. *

Re: C++11 code in the gcc 10 branch

On Dez 31 2020, FX via Gcc wrote: > I also wanted to ask approval to commit this diff below, fixing > aarch64_get_extension_string_for_isa_flags()’s prototype to align it with the > actual function definition: > > diff --git a/gcc/config/aarch64/driver-aarch64.c >

Re: C++11 code in the gcc 10 branch

FX wrote: If Richard approves the second patch (and you’re stuck for time) - then send me the patch(es) as attachments with the commit credits you want, and I can apply them for you. Both patches only needed on gcc-10, if you can commit that’s great, many thanks. bootstrapped / smoke

[Bug fortran/93794] [8/9/10/11 Regression] ICE in gfc_conv_component_ref, at fortran/trans-expr.c:2497

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93794 --- Comment #6 from Paul Thomas --- (In reply to anlauf from comment #5) > > Paul, > > > > are you still working on this? > > Paul, > > this is still one of yours... Hi Harald, Hah! I am probably a week or two from getting to it. I have

Re: libgo patch committed: Update to Go1.16beta1 release

--- a/libgo/go/internal/cpu/cpu_gccgo.c +++ b/libgo/go/internal/cpu/cpu_gccgo.c @@ -200,3 +200,29 @@ struct queryResult kdsaQuery() { } #endif /* defined(__s390x__) */ + +#ifdef __aarch64__ + +uint64_t getisar0(void) + __asm__(GOSYM_PREFIX "internal_1cpu.getisar0") +

[Bug target/95381] [11 Regression]: Bootstrap on m68k fails with ICE: in operator[], at vec.h:867

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381 Matthias Klose changed: What|Removed |Added CC||doko at debian dot org --- Comment #15

Re: libgo patch committed: Update to Go1.16beta1 release

On aarch64: /usr/aarch64-suse-linux/bin/ld: ../aarch64-suse-linux/libgo/.libs/libgo.so: undefined reference to `internal_1cpu.getMIDR' collect2: error: ld returned 1 exit status make[2]: *** [Makefile:831: test2json] Error 1 Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key

Re: [08/23] Add an alternative splay tree implementation

That doesn't build with gcc 4.8: In file included from ../../gcc/splay-tree-utils.h:491:0, from ../../gcc/rtl-ssa.h:45, from ../../gcc/fwprop.c:29: ../../gcc/splay-tree-utils.tcc:24:1: error: prototype for 'typename base_splay_tree::node_type

[Bug target/95381] [11 Regression]: Bootstrap on m68k fails with ICE: in operator[], at vec.h:867

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381 --- Comment #14 from John Paul Adrian Glaubitz --- Quick update. The bug actually occurs with "--disable-bootstrap" which is how Matthias Klose configures gcc when building the gcc-snapshot package. Removing the configure flag makes the