[Bug c++/104777] New: gcc crashes while compiling a custom coroutine library sample

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104777 Bug ID: 104777 Summary: gcc crashes while compiling a custom coroutine library sample Product: gcc Version: 11.2.0 Status: UNCONFIRMED Severity: normal

[PATCH] [i386] Prevent vectorization for load from parm_decl at O2 to avoid STF issue.

For parameter passing through stack, vectorized load from parm_decl in callee may trigger serious STF issue. This is why GCC12 regresses 50% for cray at -O2 compared to GCC11. The patch add an extremely large number to stmt_cost to prevent vectorization for loads from parm_decl under very-cheap

[PATCH v8 12/12] LoongArch Port: Add doc.

From: chenglulu 2022-03-04 Chenghua Xu Lulu Cheng * contrib/config-list.mk: Add LoongArch triplet. * gcc/doc/install.texi: Add LoongArch options section. * gcc/doc/invoke.texi: Add LoongArch options section. * gcc/doc/md.texi: Add LoongArch

[PATCH v8 11/12] LoongArch Port: gcc/testsuite

From: chenglulu 2022-03-04 Chenghua Xu Lulu Cheng gcc/testsuite/ * g++.dg/cpp0x/constexpr-rom.C: Add build options for LoongArch. * g++.old-deja/g++.abi/ptrmem.C: Add LoongArch support. * g++.old-deja/g++.pt/ptrmem6.C: xfail for LoongArch. *

[PATCH v8 08/12] LoongArch Port: libgcc

From: chenglulu 2022-03-04 Chenghua Xu Lulu Cheng libgcc/ * config/loongarch/crtfastmath.c: New file. * config/loongarch/crti.S: Like wise. * config/loongarch/crtn.S: Like wise. * config/loongarch/linux-unwind.h: Like wise. *

[PATCH v8 10/12] LoongArch Port: libgomp

From: chenglulu 2022-03-04 Chenghua Xu Lulu Cheng libgomp/ * configure.tgt: Add LoongArch triplet. --- libgomp/configure.tgt | 4 1 file changed, 4 insertions(+) diff --git a/libgomp/configure.tgt b/libgomp/configure.tgt index d4f1e741b5a..2cd7272fcd8 100644 ---

[PATCH v8 09/12] LoongArch Port: Regenerate libgcc/configure.

From: chenglulu 2022-03-04 Chenghua Xu Lulu Cheng * libgcc/configure: Regenerated. --- libgcc/configure | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/libgcc/configure b/libgcc/configure index 52bf25d4e94..1f9b2ac578b 100755 --- a/libgcc/configure

[PATCH v8 06/12] LoongArch Port: Builtin functions.

From: chenglulu 2022-03-04 Chenghua Xu Lulu Cheng gcc/ * config/loongarch/larchintrin.h: New file. * config/loongarch/loongarch-builtins.cc: New file. --- gcc/config/loongarch/larchintrin.h | 413 +

[PATCH v8 02/12] LoongArch Port: gcc build

From: chenglulu 2022-03-04 Chenghua Xu Lulu Cheng gcc/ * common/config/loongarch/loongarch-common.cc: New file. * config/loongarch/genopts/genstr.sh: New file. * config/loongarch/genopts/loongarch-strings: New file. *

[PATCH v8 07/12] LoongArch Port: Builtin macros.

From: chenglulu 2022-03-04 Chenghua Xu Lulu Cheng gcc/ *config/loongarch/loongarch-c.cc --- gcc/config/loongarch/loongarch-c.cc | 109 1 file changed, 109 insertions(+) create mode 100644 gcc/config/loongarch/loongarch-c.cc diff --git

[PATCH v8 03/12] LoongArch Port: Regenerate gcc/configure.

From: chenglulu 2022-03-04 Chenghua Xu Lulu Cheng gcc/ * configure: Regenerate. --- gcc/configure | 66 ++- 1 file changed, 60 insertions(+), 6 deletions(-) diff --git a/gcc/configure b/gcc/configure index

[PATCH v8 01/12] LoongArch Port: Regenerate configure

From: chenglulu 2022-03-04 Chenghua Xu Lulu Cheng * config/picflag.m4: Default add build option '-fpic' for LoongArch. * configure: Add LoongArch tuples. * configure.ac: Like wise. --- config/picflag.m4 | 3 +++ configure | 10 +-

[PATCH v8 00/12] Add LoongArch support.

From: chenglulu Hi, all: This is the v8 version of LoongArch Port. Please review. We know it is stage4, I think it is ok for a new prot. The kernel side upstream waiting for a approval by gcc side, if it is blocked by stage4, a approval for GCC13 will be appreciation. The LoongArch

[Bug fortran/104776] New: incorrect compiler error with Parameterized derived type component initialization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104776 Bug ID: 104776 Summary: incorrect compiler error with Parameterized derived type component initialization Product: gcc Version: 11.0 Status: UNCONFIRMED

[Bug target/104208] -mlong-double-64 should override a previous -mabi=ibmlongdouble

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104208 --- Comment #9 from Peter Bergner --- Created attachment 52559 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52559=edit Proposed patch Attaching a patch using Jakub's suggestion. I'm having problems posting it to the mailing list at

[r12-7468 Regression] FAIL: g++.dg/warn/Wstringop-overflow-6.C -std=gnu++20 (test for excess errors) on Linux/x86_64

On Linux/x86_64, 9805965e3551b66b5bd751d6076791d00cdeb137 is the first bad commit commit 9805965e3551b66b5bd751d6076791d00cdeb137 Author: Jonathan Wakely Date: Thu Mar 3 12:34:27 2022 + libstdc++: Implement std::strong_order for floating-point types [PR96526] caused FAIL:

[Bug libstdc++/95989] Segmentation fault compiling with static libraries and using jthread::request_stop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95989 Jackson Huff changed: What|Removed |Added CC||lightningdzeyenr at gmail dot com ---

[Bug target/104610] memcmp () == 0 can be optimized better for avx512f

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104610 Bug 104610 depends on bug 104704, which changed state. Bug 104704 Summary: [12 Regression] ix86_gen_scratch_sse_rtx doesn't work with explicit XMM7/XMM15/XMM31 usage https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104704 What

[Bug target/104704] [12 Regression] ix86_gen_scratch_sse_rtx doesn't work with explicit XMM7/XMM15/XMM31 usage

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104704 H.J. Lu changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug target/104704] [12 Regression] ix86_gen_scratch_sse_rtx doesn't work with explicit XMM7/XMM15/XMM31 usage

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104704 --- Comment #14 from CVS Commits --- The master branch has been updated by H.J. Lu : https://gcc.gnu.org/g:609e8c492d62d92465460eae3d43dfc4b2c68288 commit r12-7472-g609e8c492d62d92465460eae3d43dfc4b2c68288 Author: H.J. Lu Date: Sat Feb 26

[PATCH 3/3] RISC-V:Cache Management Operation instructions testcases

From: yulong-plct This commit adds testcases about CMO instructions. 7 8 gcc/testsuite/ChangeLog: 9 10 * gcc.target/riscv/cmo-zicbom-1.c: New test. 11 * gcc.target/riscv/cmo-zicbom-2.c: New test. 12 * gcc.target/riscv/cmo-zicbop-1.c: New test. 13 *

[PATCH 2/3] RISC-V:Cache Management Operation instructions

From: yulong-plct This commit adds cbo.clea,cbo.flush,cbo.inval,cbo.zero,prefetch.i,prefetch.r and prefetch.w instructions. 7 8 gcc/ChangeLog: 9 10 * config/riscv/predicates.md (imm5_operand): Add a new operand type for prefetch instructions. 11 *

[PATCH 1/3] RISC-V: Add mininal support for Zicbo[mzp]

From: yulong-plct This commit adds minimal support for 'Zicbom','Zicboz' and 'Zicbop' extensions. 7 8 gcc/ChangeLog: 9 10 * common/config/riscv/riscv-common.cc: Add zicbom, zicboz, zicbop extensions. 11 * config/riscv/riscv-opts.h (MASK_ZICBOZ): New. 12

[PATCH 0/3] RISC-V: Add Ratified Cache Management Operation ISA Extensions

From: yulong-plct This patchset adds support for three recently ratified RISC-V extensions: - Zicbom (Cache-Block Management Instructions) - Zicbop (Cache-Block Prefetch hint instructions) - Zicboz (Cache-Block Zero Instructions) Patch 1: Add Zicbom/z/p mininal support

Re: [PATCH] [i386] Optimize v4si broadcast for noavx512vl.

On Fri, Mar 4, 2022 at 10:29 AM liuhongt via Gcc-patches wrote: > > This is incremental patch based on [1], it enables optimization as below > > - vbroadcastss.LC1(%rip), %xmm0 > + movl$-45, %edx > + vmovd %edx, %xmm0 > + vpshufd $0, %xmm0, %xmm0 > > According to

[PATCH] [i386] Optimize v4si broadcast for noavx512vl.

This is incremental patch based on [1], it enables optimization as below - vbroadcastss.LC1(%rip), %xmm0 + movl$-45, %edx + vmovd %edx, %xmm0 + vpshufd $0, %xmm0, %xmm0 According to microbenchmark, it's faster than broadcast from memory. [1]

[Bug ada/104767] GNAT.Serial_Communications windows package allows/causes multiple closing of the same windows handle.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104767 --- Comment #2 from tornenvi at gmail dot com --- Created attachment 52558 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52558=edit Test program to demonstrate problem Adding test program code gnatserialerrortest2.adb to highlight the

[Bug tree-optimization/104716] ICE in copy_loop_before, at tree-loop-distribution.cc:952

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

[Bug target/104773] compare with 1 not merged with subtract 1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104773 --- Comment #1 from Hongtao.liu --- It looks like the same issue as PR98977.

Re: [PATCH] x86: Always return pseudo register in ix86_gen_scratch_sse_rtx

On Thu, Mar 3, 2022 at 10:22 PM H.J. Lu via Gcc-patches wrote: > > ix86_gen_scratch_sse_rtx returns XMM7/XMM15/XMM31 as a scratch vector > register to prevent RTL optimizers from removing vector register. It > introduces a conflict with explicit XMM7/XMM15/XMM31 usage and when it > is called by

[Bug testsuite/104724] gcc.target/i386/avx512fp16-vcvtsi2sh-1b.c etc. FAIL

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104724 Andrew Pinski changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED

[Bug ada/104767] GNAT.Serial_Communications windows package allows/causes multiple closing of the same windows handle.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104767 --- Comment #1 from tornenvi at gmail dot com --- Bug report should be referring to calls to 'Open' instead of 'Connect'.

[Bug tree-optimization/104746] False positive for -Wformat-overflow=2 since r12-7033-g3c9f762ad02f398c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104746 --- Comment #8 from Martin Sebor --- Andrew, quoting from the documentation for the warning: Unknown string arguments whose length cannot be assumed to be bounded either by the directive’s precision, or by a finite set of string literals

Re: [PATCH] call mark_dfs_back_edges() before testing EDGE_DFS_BACK [PR104761]

On 3/3/22 01:01, Jakub Jelinek wrote: On Wed, Mar 02, 2022 at 04:15:09PM -0700, Martin Sebor via Gcc-patches wrote: The -Wdangling-pointer code tests the EDGE_DFS_BACK but the pass never calls the mark_dfs_back_edges() function that initializes the bit (I didn't know about it). As a result the

Re: [PATCH] libgcc: allow building float128 libraries on FreeBSD

Hi! On Mon, Feb 21, 2022 at 12:37:56AM +0100, pku...@freebsd.org wrote: > From: Piotr Kubaj > > While FreeBSD currently uses 64-bit long double, there should be no > problem with adding support for float128. > > Signed-off-by: Piotr Kubaj This needs a changelog. The entry for configure

[Bug c++/104734] -isystem hides -Woverloaded-virtual warning

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104734 Andrew Pinski changed: What|Removed |Added Keywords||diagnostic Last reconfirmed|

New German PO file for 'gcc' (version 12.1-b20220213)

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 German team of translators. The file is available at: https://translationproject.org/latest/gcc/de.po (This file,

[Bug c/99291] maybe_warn_pass_by_reference uses outdated format string

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99291 --- Comment #6 from Roland Illig --- Still reproducible in GCC 12.

[Bug translation/104552] Mistakes in strings to be translated in GCC 12

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552 --- Comment #8 from Roland Illig --- >From tree-ssa-uninit.c: > accessing argument %u of a function declared with attribute %<%s%> The %<%s%> should be the conventional %qs.

[Bug target/99708] __SIZEOF_FLOAT128__ not defined on powerpc64le-linux

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99708 --- Comment #18 from Segher Boessenkool --- Ah, I didn't see the else ieee128_float_type_node = ibm128_float_type_node = long_double_type_node; which looks completely garbage. It long double is just DP float, we certainly do not want

[Bug target/99708] __SIZEOF_FLOAT128__ not defined on powerpc64le-linux

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99708 --- Comment #17 from Segher Boessenkool --- (In reply to Jakub Jelinek from comment #13) > I see > Doesn't this mean that ieee128_float_type_node and ibm128_float_type_node is > always non-NULL? No. All of that code is inside if

[Bug libstdc++/96526] implement std::strong_order total order on floating point types

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96526 Jonathan Wakely changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug libstdc++/104748] debug mode: FAIL: std/ranges/adaptors/all.cc (test for excess errors)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104748 Jonathan Wakely changed: What|Removed |Added Last reconfirmed||2022-03-03

[committed] libstdc++: Use non-debug vector in constexpr test [PR104748]

Tested x86_64-linux, pushed to trunk. -- >8 -- The std::__debug::vector isn't usable in constant expressions, so this test fails in debug mode. Until the debug vector is fixed we can just make the test use the non-debug one. libstdc++-v3/ChangeLog: PR libstdc++/104748 *

[committed] libstdc++: Fix test failure on AIX

Tested x86_64-linux, pushed to trunk. -- >8 -- This fixes a test failure due to a non-reserved name in an AIX system header (included via ). That name clashes with one of the names we check our own headers for, so skip checking that name on AIX. libstdc++-v3/ChangeLog: *

[committed] libstdc++: Implement std::strong_order for floating-point types [PR96526]

Tested x86_64-linux (-m32/-m64), powerpc64-linux (-m32/-m64), powerpc64le-linux, powerpc-aix (maix32/-maix64/-mlong-double-128). Pushed to trunk. I'm inclined to backport this to gcc-11 after some soak time on trunk (but not gcc-10, because it needs __builtin_bit_cast). -- >8 -- This removes a

gcc-9-20220303 is now available

Snapshot gcc-9-20220303 is now available on https://gcc.gnu.org/pub/gcc/snapshots/9-20220303/ 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

[Bug libstdc++/104748] debug mode: FAIL: std/ranges/adaptors/all.cc (test for excess errors)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104748 --- Comment #1 from CVS Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:5706a5db88a0eeaf82071debe1364f4533896a65 commit r12-7470-g5706a5db88a0eeaf82071debe1364f4533896a65 Author: Jonathan Wakely

[Bug libstdc++/96526] implement std::strong_order total order on floating point types

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96526 --- Comment #3 from CVS Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:9805965e3551b66b5bd751d6076791d00cdeb137 commit r12-7468-g9805965e3551b66b5bd751d6076791d00cdeb137 Author: Jonathan Wakely Date:

[Bug target/104775] [9/10/11/12 Regression] Failure to assemble on s390x with -fsanitize=undefined

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104775 --- Comment #1 from Jakub Jelinek --- Even simpler testcase, this time C, just -O2 -march=zEC12 is needed: long a[64]; void bar (void); void foo (int x, int y) { if (x != a[y]) bar (); __builtin_trap (); }

[Bug target/104775] [9/10/11/12 Regression] Failure to assemble on s390x with -fsanitize=undefined

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104775 Jakub Jelinek changed: What|Removed |Added Target Milestone|--- |9.5 CC|

[Bug target/104775] New: [9/10/11/12 Regression] Failure to assemble on s390x with -fsanitize=undefined

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104775 Bug ID: 104775 Summary: [9/10/11/12 Regression] Failure to assemble on s390x with -fsanitize=undefined Product: gcc Version: 12.0 Status: UNCONFIRMED

[Bug tree-optimization/104746] False positive for -Wformat-overflow=2 since r12-7033-g3c9f762ad02f398c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104746 Andrew Macleod changed: What|Removed |Added CC||amacleod at redhat dot com ---

Re: [PATCH] tree: Fix up warn_deprecated_use [PR104627]

On 3/1/22 14:33, Jakub Jelinek wrote: Hi! The r12-7287-g1b71bc7c8b18bd1b change improved the -Wdeprecated warning for C++, but regressed it for C, in particular in gcc.dg/deprecated.c testcase we now report a type that actually isn't deprecated as deprecated instead of the one that is

[Bug middle-end/104077] bogus/missing -Wdangling-pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104077 Bug 104077 depends on bug 104761, which changed state. Bug 104761 Summary: [12 Regression] bogus -Wdangling-pointer with cleanup and infinite loop https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104761 What|Removed

[Bug middle-end/104761] [12 Regression] bogus -Wdangling-pointer with cleanup and infinite loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104761 Martin Sebor changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug middle-end/104761] [12 Regression] bogus -Wdangling-pointer with cleanup and infinite loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104761 --- Comment #5 from CVS Commits --- The master branch has been updated by Martin Sebor : https://gcc.gnu.org/g:51149a05b8cc8e4fc5a77a65857894daa371de89 commit r12-7467-g51149a05b8cc8e4fc5a77a65857894daa371de89 Author: Martin Sebor Date:

[Bug c++/104702] [12 Regression] False positive -Wunused-value warning with -fno-exceptions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104702 --- Comment #3 from Martin Sebor --- The warning mapping needs to be updated whenever a location of a tree or gimple* changes (gimple_set_block() calls gimple_set_location() which calls copy_warning() so that part at least should work). I saw

[Bug c++/65396] Function template default template arguments not merged

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

[PATCH] c++: merge default targs for function templates [PR65396]

We currently merge default template arguments for class templates, but not for function templates. This patch fixes this by splitting out the argument merging logic in redeclare_class_template into a separate function and using it in duplicate_decls as well. Bootstrapped and regtested on

[Bug tree-optimization/104746] False positive for -Wformat-overflow=2 since r12-7033-g3c9f762ad02f398c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104746 Martin Sebor changed: What|Removed |Added Summary|[12 Regression] False |False positive for

[Bug tree-optimization/104746] [12 Regression] False positive for -Wformat-overflow=2 since r12-7033-g3c9f762ad02f398c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104746 --- Comment #5 from Martin Sebor --- (In reply to Martin Liška from comment #3) This is an example of the "symbolic constraints involving multiple arguments" that I mentioned in comment #1. There is no logic to determine from the complex

[Bug tree-optimization/104754] gcc.dg/pr102892-1.c FAILs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104754 --- Comment #2 from Aldy Hernandez --- BTW, on GCC11, ivopts doesn't even get a whack at it. The whole thing is optimized away by .fre4: int main () { long int a; long int c; [local count: 44232128]: if (a_9(D) <= 0) goto ;

[Bug target/99708] __SIZEOF_FLOAT128__ not defined on powerpc64le-linux

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99708 --- Comment #16 from Jakub Jelinek --- So what about: --- gcc/config/rs6000/rs6000-c.cc.jj2022-02-17 10:24:16.756113275 +0100 +++ gcc/config/rs6000/rs6000-c.cc 2022-03-03 19:06:25.771981905 +0100 @@ -584,6 +584,10 @@

[Bug tree-optimization/104754] gcc.dg/pr102892-1.c FAILs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104754 Aldy Hernandez changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0

[Bug target/99708] __SIZEOF_FLOAT128__ not defined on powerpc64le-linux

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99708 --- Comment #15 from Jakub Jelinek --- Perhaps another possible test could be ieee128_float_type_node != ibm128_float_type_node because whenever those two are different, we know __ieee128 and __ibm128 are supported (but still need to verify

Re: [PATCH] call mark_dfs_back_edges() before testing EDGE_DFS_BACK [PR104761]

On 3/3/2022 1:01 AM, Jakub Jelinek wrote: On Wed, Mar 02, 2022 at 04:15:09PM -0700, Martin Sebor via Gcc-patches wrote: The -Wdangling-pointer code tests the EDGE_DFS_BACK but the pass never calls the mark_dfs_back_edges() function that initializes the bit (I didn't know about it). As a

[Bug tree-optimization/104475] [12 Regression] Wstringop-overflow + atomics incorrect warning on dynamic object

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104475 --- Comment #5 from Andrew Macleod --- We do have the option of not trying to determine anything about _1 in situations like this.. I tried removing the op1_range() routine for addr_expr, and we pass all tests just fine. we would pick up

[Bug target/104758] [nvptx] sm_30 board support broken

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104758 --- Comment #6 from Tom de Vries --- I'm now looking at: ... diff --git a/gcc/config/nvptx/nvptx.opt b/gcc/config/nvptx/nvptx.opt index c83ceb3568b1..fea99c5d4069 100644 --- a/gcc/config/nvptx/nvptx.opt +++ b/gcc/config/nvptx/nvptx.opt @@ -53,7

[Bug target/99708] __SIZEOF_FLOAT128__ not defined on powerpc64le-linux

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99708 --- Comment #14 from Jakub Jelinek --- Unfortunately, checking TYPE_NAME won't work either. Because for the ibm128_float_type_node = long_double_type_node; and ieee128_float_type_node = long_double_type_node; cases,

[Bug fortran/104696] [OpenMP] Implicit mapping breaks struct mapping

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104696 Tobias Burnus changed: What|Removed |Added Summary|[12 Regression][OpenMP] |[OpenMP] Implicit mapping

[Bug c/104680] identical inner condition not detected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104680 Eric Gallager changed: What|Removed |Added Blocks||89863 See Also|

[Bug c++/104642] Add __builtin_trap() for missing return at -O0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104642 --- Comment #3 from Jonathan Wakely --- (In reply to Richard Biener from comment #1) > Not sure, people will still see the surprising behavior at -O1+ then Sure, but we can justify that as optimizing away the checks. But giving a predictable

[Bug target/99708] __SIZEOF_FLOAT128__ not defined on powerpc64le-linux

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99708 --- Comment #13 from Jakub Jelinek --- I see if (TARGET_FLOAT128_TYPE) { if (!TARGET_IEEEQUAD && TARGET_LONG_DOUBLE_128) ibm128_float_type_node = long_double_type_node; else { ibm128_float_type_node =

[Bug target/104643] gcc/config/rs6000/driver-rs6000.cc: 2 * pointless call ?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104643 --- Comment #3 from Segher Boessenkool --- Note that the called function is not pure (it writes to some global vars), so perhaps this was on purpose even? Andreas?

[Bug c++/104642] Add __builtin_trap() for missing return at -O0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104642 Marek Polacek changed: What|Removed |Added CC||mpolacek at gcc dot gnu.org Ever

[Bug target/99708] __SIZEOF_FLOAT128__ not defined on powerpc64le-linux

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99708 --- Comment #12 from Segher Boessenkool --- (In reply to Jonathan Wakely from comment #10) > Maybe we could do this instead: > > --- a/gcc/config/rs6000/rs6000-c.cc > +++ b/gcc/config/rs6000/rs6000-c.cc > @@ -623,11 +623,13 @@

[Bug target/99708] __SIZEOF_FLOAT128__ not defined on powerpc64le-linux

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99708 Segher Boessenkool changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

[Bug middle-end/104774] New: OpenACC 'kernels' decomposition: internal compiler error: 'verify_gimple' failed, with 'loop' with explicit 'seq' or 'independent'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104774 Bug ID: 104774 Summary: OpenACC 'kernels' decomposition: internal compiler error: 'verify_gimple' failed, with 'loop' with explicit 'seq' or 'independent' Product: gcc

[Bug libstdc++/104772] std::numeric_limits<__float128> should be specialized

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104772 Jonathan Wakely changed: What|Removed |Added Last reconfirmed||2022-03-03 Ever confirmed|0

[Bug libstdc++/104772] std::numeric_limits<__float128> should be specialized

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104772 --- Comment #1 from Jonathan Wakely --- Strictly speaking, the __FLT128_* macros relate to _Float128 which is not defined for C++ even when __float128 is (and in theory a target could have a non-IEEE __float128 which would have different

[Bug tree-optimization/104475] [12 Regression] Wstringop-overflow + atomics incorrect warning on dynamic object

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104475 --- Comment #4 from Andrew Macleod --- (In reply to Aldy Hernandez from comment #3) > This isn't the threader but VRP/ranger. > > What happens is that the threader isolates the path, making it easier for > VRP to see the equivalence, and then

[Bug target/104773] New: compare with 1 not merged with subtract 1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104773 Bug ID: 104773 Summary: compare with 1 not merged with subtract 1 Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal

[Bug libstdc++/104772] New: std::numeric_limits<__float128> should be specialized

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104772 Bug ID: 104772 Summary: std::numeric_limits<__float128> should be specialized Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: enhancement Priority: P3

[Bug target/99708] __SIZEOF_FLOAT128__ not defined on powerpc64le-linux

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99708 --- Comment #10 from Jonathan Wakely --- Maybe we could do this instead: --- a/gcc/config/rs6000/rs6000-c.cc +++ b/gcc/config/rs6000/rs6000-c.cc @@ -623,11 +623,13 @@ rs6000_cpu_cpp_builtins (cpp_reader *pfile) if (TARGET_FRSQRTES)

[Bug target/99708] __SIZEOF_FLOAT128__ not defined on powerpc64le-linux

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99708 --- Comment #9 from Jonathan Wakely --- It looks like r12-7271-g687e57d7ac741d added it: --- a/gcc/config/rs6000/rs6000-c.cc +++ b/gcc/config/rs6000/rs6000-c.cc @@ -623,7 +623,11 @@ rs6000_cpu_cpp_builtins (cpp_reader *pfile) if

[Bug target/99708] __SIZEOF_FLOAT128__ not defined on powerpc64le-linux

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99708 --- Comment #8 from Jonathan Wakely --- It looks like trunk now defines __SIZEOF_FLOAT128__ on powerpc-ibm-aix* and powerpc64*-*-linux-gnu, but it seems to be defined unconditionally, even if the __float128 type *isn't* available! On

[Bug target/104643] gcc/config/rs6000/driver-rs6000.cc: 2 * pointless call ?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104643 Will Schmidt changed: What|Removed |Added CC||bergner at gcc dot gnu.org,

[Bug tree-optimization/104639] [12 Regression] Useless loop not fully optimized anymore

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104639 --- Comment #11 from Aldy Hernandez --- (In reply to Andrew Macleod from comment #10) > I was thinking less about phis and more that its a "return" instead of an > "if" ending the block preventing the threader from doing anything. > > _3 =

Re: [PATCH] libgcc: allow building float128 libraries on FreeBSD

I don't have any objection, but the patch is FreeBSD-specific. You are sending the patch from the FreeBSD organization, but I don't know the authority structure within the organization. Andreas Tobler is the FreeBSD maintainer for GCC, but I don't know his current status. Thanks, David On

[PATCH][pushed] configure: enable plugin support for ld.mold

Hi. There's another part of mold enablement. Going to push it. Martin gcc/ChangeLog: * configure.ac: Now ld.mold support LTO plugin API, use it. * configure: Regenerate. --- gcc/configure| 2 ++ gcc/configure.ac | 2 ++ 2 files changed, 4 insertions(+) diff --git

[Bug c++/104765] Expression statement with a return in a lambda-parameter-default causes segfault when called in a different function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104765 --- Comment #4 from Marek Polacek --- The attached patch disables ({}) in lambda param list, which fixes the bug, but also makes things less consistent: void G() { void fn (int i, int = ({ 1; })); // currently OK } void g() { auto a =

[Bug middle-end/104757] [12 Regression][OpenMP] ICE in GIMPLE pass: walloca - in gimple_range_global / segfault as SSA_NAME_DEF_STMT is NULL for 'if' clause arg

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104757 Thomas Schwinge changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c/104680] identical inner condition not detected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104680 --- Comment #9 from Jakub Jelinek --- At least right now the analyzer might be too late for this though, no? There could be various optimizations before it that make it hard to figure out what was actually user code and what is something else.

[Bug target/104758] [nvptx] sm_30 board support broken

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104758 Tom de Vries changed: What|Removed |Added Resolution|FIXED |--- Last reconfirmed|

[Bug tree-optimization/104639] [12 Regression] Useless loop not fully optimized anymore

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104639 --- Comment #10 from Andrew Macleod --- I was thinking less about phis and more that its a "return" instead of an "if" ending the block preventing the threader from doing anything. _3 = i_6 != 0; return _3; Ie, so if a return uses a

[Bug c/104680] identical inner condition not detected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104680 David Malcolm changed: What|Removed |Added Component|analyzer|c Assignee|dmalcolm at gcc

[Bug middle-end/104529] [12 Regression] inefficient codegen around new/delete

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104529 Jakub Jelinek changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org

[PATCH] x86: Always return pseudo register in ix86_gen_scratch_sse_rtx

ix86_gen_scratch_sse_rtx returns XMM7/XMM15/XMM31 as a scratch vector register to prevent RTL optimizers from removing vector register. It introduces a conflict with explicit XMM7/XMM15/XMM31 usage and when it is called by RTL optimizers, it may introduce conflicting usages of XMM7/XMM15/XMM31.

[Bug analyzer/104680] identical inner condition not detected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104680 --- Comment #7 from David Malcolm --- > trunk.git/zlib/contrib/minizip/zip.c:1212:26: warning: Identical inner 'if' > condition is always true. [identicalInnerCondition] In zipOpenNewFileInZip4_64: 1206 │ #ifdef HAVE_BZIP2 1207 │ if

  1   2   >