[pushed] c++: location of lambda object and conversion call

Two things that had poor location info: we weren't giving the TARGET_EXPR for a lambda object any location, and the call to a conversion function was getting whatever input_location happened to be. Tested x86_64-pc-linux-gnu, applying to trunk. gcc/cp/ChangeLog: * call.c

[pushed] c++: check constexpr constructor body

The implicit constexpr patch revealed that our checks for constexpr constructors that could possibly produce a constant value (which otherwise are IFNDR) was failing to look at most of the function body. Fixing that required some library tweaks. Tested x86_64-pc-linux-gnu, applying to trunk.

[pushed] c++: is_this_parameter and coroutines proxies

Compiling coroutines/pr95736.C with the implicit constexpr patch broke because is_this_parameter didn't recognize the coroutines proxy for 'this'. Tested x86_64-pc-linux-gnu, applying to trunk. gcc/cp/ChangeLog: * semantics.c (is_this_parameter): Check DECL_HAS_VALUE_EXPR_P

[Bug c++/70690] [6/7 Regression] r235002 miscompiles tcmalloc

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70690 --- Comment #12 from CVS Commits --- The master branch has been updated by Jason Merrill : https://gcc.gnu.org/g:bd95d75f3412e1a7debab7c6c602ba409f274eb5 commit r12-5254-gbd95d75f3412e1a7debab7c6c602ba409f274eb5 Author: Jason Merrill Date:

[pushed] c++: c++20 constexpr default ctor and array init

The implicit constexpr patch revealed that marking the constructor in the PR70690 testcase as constexpr made the bug reappear, because build_vec_init assumed that a constexpr default constructor initialized the whole object, so it was equivalent to value-initialization. But this is no longer true

[pushed] c++: don't do constexpr folding in unevaluated context

The implicit constexpr patch revealed that we were doing constant evaluation of arbitrary expressions in unevaluated contexts, leading to failure when we tried to evaluate e.g. a call to declval. This is wrong more generally; only manifestly-constant-evaluated expressions should be evaluated

[pushed] c++: constexpr virtual and vbase thunk

C++20 allows virtual functions to be constexpr. I don't think that calling through a pointer to a vbase subobject is supposed to work in a constant expression, since an object with virtual bases can't be constant, but the call shouldn't ICE. Tested x86_64-pc-linux-gnu, applying to trunk.

Re: [PATCH 1/2] Add cumulative_args_t variants of TARGET_FUNCTION_ROUND_BOUNDARY and friends

On Sat, Nov 13, 2021 at 10:43 AM Maxim Blinov wrote: > > The two target hooks responsible for informing GCC about stack > parameter alignment are `TARGET_FUNCTION_ARG_BOUNDARY` and > `TARGET_FUNCTION_ARG_ROUND_BOUNDARY`, which currently only consider > the tree and machine_mode of a specific

Re: [PATCH 2/6] Add returns_zero_on_success/failure attributes

On Sun, 14 Nov 2021 at 02:07, David Malcolm via Gcc-patches wrote: > > This patch adds two new attributes. The followup patch makes use of > the attributes in -fanalyzer. > > gcc/c-family/ChangeLog: > * c-attribs.c (attr_noreturn_exclusions): Add > "returns_zero_on_failure" and

[Committed] gcc.dg/uninit-pred-9_b.c: Correct last adjustment for cris-elf

The change at r12-4790 should have done the same change for CRIS as was done for powerpc64*-*-*. (Probably MMIX too but that may have to wait until the next weekend.) Committed. gcc/testsuite: * gcc.dg/uninit-pred-9_b.c: Correct last adjustment, for CRIS. ---

Can I provide a hint to gcc for return value optimization?

I want give a hint to gcc that allows std::string to rvo. Is that possible? Any attribute for doing that? Sent from Mail for Windows

Re: [PATCH] Enhance unordered container merge

On 15/11/21 12:25 am, Jonathan Wakely wrote: On Sun, 14 Nov 2021 at 13:31, François Dumont via Libstdc++ wrote: libstdc++: Unordered containers merge re-use hash code. When merging between 2 unordered containers with same hasher we can re-use the cached hash code if any.

[Bug c++/95117] Segmentation fault with static await_ready() or await_resume()

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95117 Ofee Oficsu changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED

[Bug c/66918] Disable "inline function declared but never defined" warning

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66918 Ofee Oficsu changed: What|Removed |Added CC||oficsu at gmail dot com --- Comment #11

[committed] VAX: Implement the `-mlra' command-line option

Add the the `-mlra' command-line option for the VAX target, with the usual semantics of enabling Local Register Allocation, off by default. LRA remains unstable with the VAX target, with numerous ICEs throughout the testsuite and worse code produced overall where successful, however the

Re: [PATCH v2] Check optab before transforming atomic bit test and operations

On Mon, Nov 15, 2021 at 9:37 AM Hongtao Liu wrote: > > On Sat, Nov 13, 2021 at 2:21 AM H.J. Lu via Gcc-patches > wrote: > > > > On Fri, Nov 12, 2021 at 8:13 AM Jakub Jelinek wrote: > > > > > > On Fri, Nov 12, 2021 at 07:55:26AM -0800, H.J. Lu wrote: > > > > > I have following patch queued for

[Bug tree-optimization/103194] [12 Regression] ice in optimize_atomic_bit_test_and with __sync_fetch_and_and since r12-5102-gfb161782545224f5

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103194 Hongtao.liu changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #8

Re: [PATCH v2] Check optab before transforming atomic bit test and operations

On Sat, Nov 13, 2021 at 2:21 AM H.J. Lu via Gcc-patches wrote: > > On Fri, Nov 12, 2021 at 8:13 AM Jakub Jelinek wrote: > > > > On Fri, Nov 12, 2021 at 07:55:26AM -0800, H.J. Lu wrote: > > > > I have following patch queued for testing for this... > > > > > > > > 2021-11-12 Jakub Jelinek > > >

[Bug tree-optimization/103194] [12 Regression] ice in optimize_atomic_bit_test_and with __sync_fetch_and_and since r12-5102-gfb161782545224f5

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103194 --- Comment #7 from Hongtao.liu --- (In reply to H.J. Lu from comment #6) > Created attachment 51785 [details] > The v2 incomplete patch > > Hongtao, please finish it. Thanks. Yes.

[Bug debug/103241] New: Odd 0 length entries in location lists

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103241 Bug ID: 103241 Summary: Odd 0 length entries in location lists Product: gcc Version: 11.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug

[Bug c++/55918] Stack partially unwound when noexcept causes call to std::terminate

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55918 James Y Knight changed: What|Removed |Added CC||foom at fuhm dot net --- Comment #5

[Bug middle-end/54571] Missed optimization converting between bit sets

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54571 Andrew Pinski changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot gnu.org

[Bug tree-optimization/97711] Failure to optimise "x & 1 ? x - 1 : x" to "x & -2"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97711 --- Comment #5 from Andrew Pinski --- (In reply to Andrew Pinski from comment #4) > (In reply to Andrew Pinski from comment #3) > > Mine, the patch which fixes PR 103216 fixes this too. > > Note it does not fix it fully on the gimple level, we

[Bug libstdc++/103240] std::type_info::before gives wrong answer for ARM EABI

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103240 Jonathan Wakely changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org

[PATCH v5] c++: Add gnu::diagnose_as attribute

Sorry for taking so long. I hope we can still get this done for GCC 12. One open question: If we change std::__cxx11::basic_string to std::string with this feature, should DWARF strings change or not? I.e. should diagnose_as be conditional on (pp->flags & pp_c_flag_gnu_v3)? If these strings

[Bug tree-optimization/97711] Failure to optimise "x & 1 ? x - 1 : x" to "x & -2"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97711 --- Comment #4 from Andrew Pinski --- (In reply to Andrew Pinski from comment #3) > Mine, the patch which fixes PR 103216 fixes this too. Note it does not fix it fullly on the gimple level, we are left with: _1 = x_3(D) & 1; _7 = _1 != 0;

[Bug tree-optimization/97711] Failure to optimise "x & 1 ? x - 1 : x" to "x & -2"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97711 Andrew Pinski changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot gnu.org

[Bug libstdc++/103240] std::type_info::before gives wrong answer for ARM EABI

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103240 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug libstdc++/103240] New: std::type_info::before gives wrong answer for ARM EABI

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103240 Bug ID: 103240 Summary: std::type_info::before gives wrong answer for ARM EABI Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: ABI Severity: normal

[Bug target/21824] [meta-bug] bootstrap bugs for *-gnu*

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21824 --- Comment #3 from Eric Gallager --- (In reply to Eric Gallager from comment #2) > (In reply to Alfred M. Szmidt from comment #1) > > Could someone go over these bugs and commit the pending patches? > > Only bug 21823 is left now. OK, that's

[Bug target/21824] [meta-bug] bootstrap bugs for *-gnu*

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21824 Bug 21824 depends on bug 21823, which changed state. Bug 21823 Summary: MAXPATHLEN usage in [gcc]/fixincludes https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21823 What|Removed |Added

[Bug other/21823] MAXPATHLEN usage in [gcc]/fixincludes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21823 Eric Gallager changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug other/89863] [meta-bug] Issues in gcc that other static analyzers (cppcheck, clang-static-analyzer, PVS-studio) find that gcc misses

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89863 Bug 89863 depends on bug 80047, which changed state. Bug 80047 Summary: fixincludes/fixincl.c: PVS-Studio: Improper Release of Memory Before Removing Last Reference (CWE-401) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80047 What

[Bug bootstrap/80047] fixincludes/fixincl.c: PVS-Studio: Improper Release of Memory Before Removing Last Reference (CWE-401)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80047 Eric Gallager changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug tree-optimization/103216] missed optimization, phiopt/vrp?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103216 Andrew Pinski changed: What|Removed |Added Depends on||103218 URL|

[PATCH] PR tree-optimization/103216: optimize some A ? (b op CST) : b into b op (A?CST:CST2)

From: Andrew Pinski For this PR, we have: if (d_5 < 0) goto ; [INV] else goto ; [INV] : v_7 = c_4 | -128; : # v_1 = PHI Which PHI-OPT will try to simplify "(d_5 < 0) ? (c_4 | -128) : c_4" which is not handled currently. This adds a few patterns which allows to try to

[PATCH] [Commmitted] Move some testcases to torture from tree-ssa

From: Andrew Pinski While writing up some testcases, I noticed some newer testcases just had "dg-do compile/run" on them with dg-options of either -O1 or -O2. Since it is always better to run them over all optimization levels I put them in gcc.c-torture/compile or gcc.c-torture/execute.

Re: [PATCH] Enhance unordered container merge

On Sun, 14 Nov 2021 at 13:31, François Dumont via Libstdc++ wrote: > > libstdc++: Unordered containers merge re-use hash code. > > When merging between 2 unordered containers with same hasher we can > re-use > the cached hash code if any. Instead of introducing the

Use modref kills in tree-ssa-dse

Hi, this patch extends tree-ssa-dse to use modref kill summary to clear live_bytes. This makes it possible to remove calls that are killed in parts. I noticed that DSE duplicates the logic of tree-ssa-alias that is mathing bases of memory accesses. Here operands_equal_p (base1, base,

[PATCH] libstdc++: Implement P1328 "Making std::type_info::operator== constexpr"

Not committed yet ... This feature is present in the C++23 draft. The ARM EABI requires that the type_info::operator== function can be defined out-of-line (and suggests that should be the default). With this patch, we fail to conform to that in C++23 mode. I think we might want to move the logic

gcc-12-20211114 is now available

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

[Bug sanitizer/102911] AddressSanitizer: CHECK failed: asan_malloc_linux.cpp:46

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102911 Andrew Pinski changed: What|Removed |Added Resolution|--- |FIXED Target Milestone|---

Track nondeterminism and interposable calls in ipa-modref

Hi, This patch adds tracking of two new flags in ipa-modref: nondeterministic and calls_interposable. First is set when function does something that is not guaranteed to be the same if run again (volatile memory access, volatile asm or external function call). Second is set if function calls

[PATCH] Fortran: Mark internal symbols as artificial [PR88009,PR68800]

Hi! Amend fix for PR88009 to mark all these class components as artificial. gcc/fortran/ChangeLog: * class.c (gfc_build_class_symbol, generate_finalization_wrapper, (gfc_find_derived_vtab, find_intrinsic_vtab): Use stringpool for names. Mark internal symbols as

[Bug tree-optimization/103219] [12 Regression] ICE Segmentation fault at -O3 (during GIMPLE pass: unrolljam) since r12-4526-gd8edfadfc7a9795b

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103219 --- Comment #2 from Andrew Pinski --- (In reply to Aldy Hernandez from comment #1) > Looks like a latent bug elsewhere as we're not threading anything. For that > matter, test fails even with -fno-thread-jumps. Right, it is a dup of one of

[PATCH v1 2/2] RISC-V: Add instruction fusion (for ventana-vt1)

From: Philipp Tomsich The Ventana VT1 core supports quad-issue and instruction fusion. This implemented TARGET_SCHED_MACRO_FUSION_P to keep fusible sequences together and adds idiom matcheing for the supported fusion cases. gcc/ChangeLog: * config/riscv/riscv.c (enum

[PATCH v1 1/2] RISC-V: Add basic support for the Ventana-VT1 core

From: Philipp Tomsich The Ventana-VT1 core is compatible with rv64gc and Zb[abcs]. This introduces a placeholder -mcpu=ventana-vt1, so tooling and scripts don't need to change once full support (pipeline, tuning, etc.) will become public later. gcc/ChangeLog: *

[PATCH v1 0/2] Basic support for the Ventana VT1 w/ instruction fusion

This series provides support for the Ventana VT1 (a 4-way superscalar rv64gc_zba_zbb_zbc_zbs core) including support for the supported instruction fusion patterns. This includes the addition of the fusion-aware scheduling infrastructure for RISC-V and implements idiom recognition for the fusion

[Bug tree-optimization/103184] [12 Regression] ICE caused by r12-5102

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103184 H.J. Lu changed: What|Removed |Added CC||hjl.tools at gmail dot com --- Comment #6

[Bug c++/103239] missing reason why template argument deduction/substitution failed

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103239 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Known to fail|

[Bug tree-optimization/103184] [12 Regression] ICE caused by r12-5102

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103184 Andrew Pinski changed: What|Removed |Added CC||law at gcc dot gnu.org --- Comment #5

[Bug tree-optimization/103235] [12 Regression] Recent change to atomics triggers ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103235 Andrew Pinski changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug tree-optimization/103235] [12 Regression] Recent change to atomics triggers ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103235 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |12.0 Keywords|

Re: [PATCH] libgccjit: add some reflection functions in the jit C api

David: PING Le mardi 12 octobre 2021 à 22:09 -0400, Antoni Boucher a écrit : > David: PING > > Le lundi 27 septembre 2021 à 20:53 -0400, Antoni Boucher a écrit : > > I fixed an issue (it would show an error message when > > gcc_jit_type_dyncast_function_ptr_type was called on a type > >

[Bug c++/103236] [9/10/11/12 Regression] ICE: in tsubst_pack_expansion, at cp/pt.c:13162

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103236 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |9.5 Ever confirmed|0

[Bug tree-optimization/103237] [10/11/12 Regression] wrong code with -ftree-vectorize at -O1 on x86_64-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103237 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Summary|wrong code with

[committed] VAX: Add the `setmemhi' instruction

The MOVC5 machine instruction has `memset' semantics if encoded with a zero source length[1]: "4. MOVC5 with a zero source length operand is the preferred way to fill a block of memory with the fill character." Use that instruction to implement the `setmemhi' instruction then. Use the AP

[Bug tree-optimization/103215] [12 regression] gcc generates unexpected warnings on libx11-1.7.2: error: array subscript -2 is outside array bounds of since r12-3124-g820f0940d7ace130

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103215 --- Comment #5 from Andrew Pinski --- (In reply to Sergei Trofimovich from comment #4) > Created attachment 51792 [details] > gdb-bug.cc That was filed as PR 102216.

Re: [PATCH,FORTRAN] Fix memory leak in finalization wrappers

On Sun, 7 Nov 2021 13:32:34 +0100 Mikael Morin wrote: > > btw.. Just because it's vagely related. > > I think f8add009ce300f24b75e9c2e2cc5dd944a020c28 for > > PR fortran/88009 (ICE in find_intrinsic_vtab, at fortran/class.c:2761) > > is incomplete in that i think all the internal class helpers

[Bug fortran/102043] Wrong array types used for negative stride accesses

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102043 --- Comment #20 from Thomas Koenig --- (In reply to Mikael Morin from comment #19) > (In reply to Thomas Koenig from comment #15) > > One possibility would be to extend the patch Sandra posted at > >

[Bug c++/101853] [12 Regression] g++.dg/modules/xtreme-header-5_b.C ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101853 --- Comment #7 from Jonathan Wakely --- Nobody is maintaining the modules code right now. This was introduced by a libstdc++ change, but as far as I know the library code is correct and this is just a compiler bug that should get fixed in stage

Re: Basic kill analysis for modref

> > > > I think you want get_addr_base_and_unit_offset here. All > > variable indexed addresses are in separate stmts. That also means > > you can eventually work with just byte sizes/offsets? > > Will do. The access range in modref summary is bit based (since we want > to disabiguate

[Bug c++/103239] New: confusing template argument deduction error message

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103239 Bug ID: 103239 Summary: confusing template argument deduction error message Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3

[Bug c++/101853] [12 Regression] g++.dg/modules/xtreme-header-5_b.C ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101853 --- Comment #6 from Hans-Peter Nilsson --- (In reply to seurer from comment #5) > I am still seeing these today with > g:a40970cf043553f0ca09a3b7be1c5a949623d915, r12-4318 [list elided] For cris-elf too. For cris-elf, be5bdccd865b (r12-4056)

[Bug c++/103238] New: c++ Feature: array-copy experimental extensions implementing P1997

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103238 Bug ID: 103238 Summary: c++ Feature: array-copy experimental extensions implementing P1997 Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: patch

[Bug tree-optimization/103237] New: wrong code with -ftree-vectorize at -O1 on x86_64-linux-gnu

ured with:../configure --prefix=/home/haoxin/haoxin-data/compilers/gcc/build/ --enable-bootstrap --enable-checking=release --enable-multilib --enable-languages=c,c++,lto --no-create --no-recursion Thread model: posix Supported LTO compression algorithms: zlib gcc version 12.0.0 2024 (experime

[Bug tree-optimization/103235] [12 Regression] Recent change to atomics triggers ICE

-csky-linux --with-local-prefix=/usr/local --with-system-zlib --disable-libcc1 --disable-libcilkrts --disable-libsanitizer --disable-libmpx --enable-languages=c,c++ Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 12.0.0 2024 (experimental) (GCC) [hjl@gnu-cfl-2

[Bug tree-optimization/103215] [12 regression] gcc generates unexpected warnings on libx11-1.7.2: error: array subscript -2 is outside array bounds of since r12-3124-g820f0940d7ace130

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103215 --- Comment #4 from Sergei Trofimovich --- Created attachment 51792 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51792=edit gdb-bug.cc Found similar bug in gdb/c++ at gdb/language.c. It might have slightly better loop structure. As a

[Bug fortran/102043] Wrong array types used for negative stride accesses

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102043 --- Comment #19 from Mikael Morin --- (In reply to Thomas Koenig from comment #15) > One possibility would be to extend the patch Sandra posted at > https://gcc.gnu.org/pipermail/fortran/2021-January/055563.html > to scalarization. Probably

Re: [PATCH][_GLIBCXX_DEBUG] Code cleanup/simplification

On Sat, 13 Nov 2021 at 13:19, François Dumont via Libstdc++ wrote: > > libstdc++: [_GLIBCXX_DEBUG] Remove _Safe_container<>::_M_safe() > > Container code cleanup to get rid of _Safe_container<>::_M_safe() > and just > _Safe:: calls which use normal inheritance. Also remove several

[Bug tree-optimization/103235] [12 Regression] Recent change to atomics triggers ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103235 --- Comment #2 from Jeffrey A. Law --- Can you please double-check? It just reproduced for me. Perhaps you were missing -I./ which is sometimes needed for cross toolchains to *-linux. [jlaw@dl360p gcc]$ ./cc1 -O2 pthread_cancel.i -I./ -quiet

[Bug fortran/102043] Wrong array types used for negative stride accesses

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102043 Mikael Morin changed: What|Removed |Added Attachment #51787|0 |1 is obsolete|

[Bug c++/103236] ICE: in tsubst_pack_expansion, at cp/pt.c:13162

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103236 --- Comment #1 from 康桓瑋 --- may be dup of PR99590.

[Bug tree-optimization/103235] [12 Regression] Recent change to atomics triggers ICE

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

[Bug fortran/102043] Wrong array types used for negative stride accesses

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102043 --- Comment #17 from Bernhard Reutner-Fischer --- Do we want to address arrays always at position 0 (maybe to help graphite ?) or would it be sufficient to just not dereference the array "before" the first position like Mikael suggests in

[Bug c++/103236] New: ICE: in tsubst_pack_expansion, at cp/pt.c:13162

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103236 Bug ID: 103236 Summary: ICE: in tsubst_pack_expansion, at cp/pt.c:13162 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug fortran/102043] Wrong array types used for negative stride accesses

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102043 --- Comment #16 from Bernhard Reutner-Fischer --- In addition to comment #1 here's an excerpt of an existing test with just one dimension: $ cat f_pr86389.f90 ! PR 19239. Check for various kinds of vector subscript. In this test, ! all

[Bug tree-optimization/103235] New: [12 Regression] Recent change to atomics triggers ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103235 Bug ID: 103235 Summary: [12 Regression] Recent change to atomics triggers ICE Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug tree-optimization/103231] [12 Regression] ICE (nondeterministic) on valid code at -O1 on x86_64-linux-gnu: Segmentation fault since r12-5014-g6b8b959675a3e14c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103231 --- Comment #11 from Martin Liška --- But yes, with ulimit -s 512, one can reduce it to: $ cat pr103231.c long g_1496_BK8K8el_2738; int fn1_l_1522; int fn1_l_2664; long fn1_l_1761; unsigned int fn1_l_1812; int fn1_l_2189; int fn1_by; int

[Bug tree-optimization/103231] [12 Regression] ICE (nondeterministic) on valid code at -O1 on x86_64-linux-gnu: Segmentation fault since r12-5014-g6b8b959675a3e14c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103231 --- Comment #10 from Martin Liška --- (In reply to Zhendong Su from comment #9) > A very simple repro (with ulimit -s 32): Well, using a stack limit of 32B does not make sense, pretty much any executable hits stack overflow with such a small

[Bug tree-optimization/103231] [12 Regression] ICE (nondeterministic) on valid code at -O1 on x86_64-linux-gnu: Segmentation fault since r12-5014-g6b8b959675a3e14c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103231 --- Comment #9 from Zhendong Su --- A very simple repro (with ulimit -s 32): [530] % compile.sh small.c *** Compiling with: gcctk -O1 small.c gcctk: internal compiler error: Segmentation fault signal terminated program cc1 Please submit a full

[Bug analyzer/103233] Warning from system libraries in user code: CWE-476 -Werror=analyzer-null-dereference

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103233 --- Comment #3 from alx.manpages at gmail dot com --- Hi Jonathan, On 11/14/21 15:57, redi at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103233 > > Jonathan Wakely changed: > > What|Removed

Re: [PATCH] rs6000: Fix a handful of 32-bit built-in function problems in the new support

Hi! On Sun, Nov 14, 2021 at 08:17:41AM -0600, Bill Schmidt wrote: > On 11/11/21 10:50 AM, Bill Schmidt wrote: > > On 11/11/21 7:11 AM, Segher Boessenkool wrote: > >> void f(long x) { __builtin_set_texasr(x); } > >> > >> built with -m32 -mpowerpc64 gives (in the expand dump): > >> > >> void f

[Bug ipa/103234] New: ipa-sra is broken (and therefore disabled) on variably sized parameters

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103234 Bug ID: 103234 Summary: ipa-sra is broken (and therefore disabled) on variably sized parameters Product: gcc Version: 12.0 Status: UNCONFIRMED Severity:

Re: [COMMITTED] Do not pass NULL to memset in ssa_global_cache.

Ok, done. Pushed. Aldy On Sun, Nov 14, 2021 at 2:53 PM Martin Liška wrote: > > On 11/14/21 14:15, Aldy Hernandez wrote: > > The code computing ranges in PHIs in the path solver reuses the > > temporary ssa_global_cache by calling its clear method. Calling it on > > an empty cache causes us to

[Bug c++/85282] CWG 727 (full specialization in non-namespace scope)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85282 Patrick Palka changed: What|Removed |Added CC||dl.soluz at gmx dot net --- Comment #16

[Bug c++/103232] scoped template specalization is not supported (not with C+17 nor C++20)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103232 Patrick Palka changed: What|Removed |Added CC||ppalka at gcc dot gnu.org

[Bug c++/103233] Warning from system libraries in user code: CWE-476 -Werror=analyzer-null-dereference

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103233 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[Bug c++/103233] Warning from system libraries in user code: CWE-476 -Werror=analyzer-null-dereference

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103233 --- Comment #1 from Alejandro Colomar --- $ cat /etc/os-release PRETTY_NAME="Debian GNU/Linux bookworm/sid" NAME="Debian GNU/Linux" ID=debian HOME_URL="https://www.debian.org/; SUPPORT_URL="https://www.debian.org/support;

[Bug c++/103233] New: Warning from system libraries in user code: CWE-476 -Werror=analyzer-null-dereference

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103233 Bug ID: 103233 Summary: Warning from system libraries in user code: CWE-476 -Werror=analyzer-null-dereference Product: gcc Version: unknown Status: UNCONFIRMED

[Bug tree-optimization/58483] missing optimization opportunity for const std::vector compared to std::array

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58483 --- Comment #16 from dennis luehring --- the sample still gets reduced by clang to 160 with -O2 or -O3 clang: main: # @main mov eax, 160 ret and gcc 11.2/trunk producing -O2 main:

Re: [PATCH] rs6000: Fix a handful of 32-bit built-in function problems in the new support

On 11/11/21 10:50 AM, Bill Schmidt wrote: > On 11/11/21 7:11 AM, Segher Boessenkool wrote: >> void f(long x) { __builtin_set_texasr(x); } >> >> built with -m32 -mpowerpc64 gives (in the expand dump): >> >> void f (long int x) >> { >> long long unsigned int _1; >> >> ;; basic block 2, loop

[Bug c++/103232] scoped template specalization is not supported (not with C+17 nor C++20)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103232 --- Comment #1 from dennis luehring --- gcc 11.2 https://gcc.godbolt.org/z/jG8f6Phjc clang 7 https://gcc.godbolt.org/z/c4Md5Yh1x

[Bug c++/103232] New: scoped template specalization is not supported (not with C+17 nor C++20)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103232 Bug ID: 103232 Summary: scoped template specalization is not supported (not with C+17 nor C++20) Product: gcc Version: 11.2.0 Status: UNCONFIRMED Severity:

Re: [PATCH 0/6] RFC: adding support to GCC for detecting trust boundaries

On Sat, Nov 13, 2021 at 9:37 PM David Malcolm wrote: > > #define __user __attribute__((untrusted)) > > where my patched GCC treats > T * > vs > T __attribute__((untrusted)) * > as being different types and thus the C frontend can complain (even without > -fanalyzer) about e.g.: This one

Re: [COMMITTED] Do not pass NULL to memset in ssa_global_cache.

On 11/14/21 14:15, Aldy Hernandez wrote: The code computing ranges in PHIs in the path solver reuses the temporary ssa_global_cache by calling its clear method. Calling it on an empty cache causes us to call memset with NULL. [The testcase doesn't fail without the patch. I suppose it needs

[PATCH] Enhance unordered container merge

    libstdc++: Unordered containers merge re-use hash code.     When merging between 2 unordered containers with same hasher we can re-use     the cached hash code if any.     Use previous insert iterator as a hint for the next insert in case of multi container.     *

[Bug other/63426] [meta-bug] Issues found with -fsanitize=undefined

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426 Bug 63426 depends on bug 103229, which changed state. Bug 103229 Summary: gcc/gimple-range-cache.cc:654:10: runtime error: null pointer passed as argument 1, which is declared to never be null https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103229

[Bug tree-optimization/103229] gcc/gimple-range-cache.cc:654:10: runtime error: null pointer passed as argument 1, which is declared to never be null

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103229 Aldy Hernandez changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug tree-optimization/103229] gcc/gimple-range-cache.cc:654:10: runtime error: null pointer passed as argument 1, which is declared to never be null

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103229 --- Comment #3 from CVS Commits --- The master branch has been updated by Aldy Hernandez : https://gcc.gnu.org/g:a7ef5da3a9c348c35abb72d6f64f209f5661cfa4 commit r12-5242-ga7ef5da3a9c348c35abb72d6f64f209f5661cfa4 Author: Aldy Hernandez Date:

  1   2   >