[Bug target/106736] [13 Regression] ICE in gen_movxo, at config/rs6000/mma.md:333

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106736 Arseny Solokha changed: What|Removed |Added Keywords|ice-on-valid-code |ice-on-invalid-code --- Comment #1

Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming

On Thu, Aug 25, 2022 at 01:36:10AM +0200, Alejandro Colomar wrote: > But from your side what do we have? Just direct NAKs without much > explanation. The only one who gave some explanation was Greg, and he > vaguely pointed to Linus's comments about it in the past, with no precise > pointer to

[Bug target/106736] New: [13 Regression] ICE in gen_movxo, at config/rs6000/mma.md:333

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106736 Bug ID: 106736 Summary: [13 Regression] ICE in gen_movxo, at config/rs6000/mma.md:333 Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords:

Re: [PATCH] libstdc++: Optimize operator+(string/char*, string/char*) equally

On Wed, Aug 24, 2022 at 7:03 PM Jonathan Wakely wrote: > > On Wed, 24 Aug 2022 at 23:47, Jonathan Wakely wrote: > > > > On Wed, 24 Aug 2022 at 23:39, Alexandre Oliva wrote: > > > > > > On Aug 24, 2022, Jonathan Wakely via Gcc-patches > > > wrote: > > > > > > >*

[PATCH v4] rs6000: Rework ELFv2 support for -fpatchable-function-entry* [PR99888]

Hi, As PR99888 and its related show, the current support for -fpatchable-function-entry on powerpc ELFv2 doesn't work well with global entry existence. For example, with one command line option -fpatchable-function-entry=3,2, it got below w/o this patch: .LPFE1: nop nop

[Bug middle-end/106725] LTO semantics for __attribute__((leaf))

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106725 --- Comment #3 from rguenther at suse dot de --- On Wed, 24 Aug 2022, dthorn at google dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106725 > > --- Comment #2 from Daniel Thornburgh --- > (In reply to Richard Biener from

Re: [PATCH, rs6000] Change insn condition from TARGET_64BIT to TARGET_POWERPC64 for VSX scalar extract/insert instructions

on 2022/8/25 11:37, HAO CHEN GUI wrote: > Hi, > > On 24/8/2022 下午 1:24, Kewen.Lin wrote: >> Could you try to test with dg-options "-mdejagnu-cpu=power9 -mpowerpc64" all >> the time, but still >> having that has_arch_ppc64 effective target on aix? >> >> I'd expect has_arch_ppc64 check to fail on

[Bug target/106728] Cannot Compile EXE on Shared Network Drive (Windows, MinGW)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106728 --- Comment #6 from Andrew Pinski --- I had a typo, it should have been -S rather than just S.

[Bug target/106728] Cannot Compile EXE on Shared Network Drive (Windows, MinGW)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106728 --- Comment #5 from John Smith --- (In reply to Andrew Pinski from comment #4) > Try the following: > g++ -std=c++11 iterate.cpp S -o "Z:\28sec\out.s" > > If this works, then you should report it to binutils. > Though I suspect it is

Re: [PATCH] Don't gimple fold ymm-version vblendvpd/vblendvps/vpblendvb w/o TARGET_AVX2

On Wed, Aug 24, 2022 at 9:15 AM liuhongt wrote: > > Since 256-bit vector integer comparison is under TARGET_AVX2, > and gimple folding for vblendvpd/vblendvps/vpblendvb relies on that. > Restrict gimple fold condition to TARGET_AVX2. > > Bootstrapped and regtested on x86_64-pc-linux-gnu{-m32,}. >

Re: [PATCH, rs6000] Change insn condition from TARGET_64BIT to TARGET_POWERPC64 for VSX scalar extract/insert instructions

Hi, On 24/8/2022 下午 1:24, Kewen.Lin wrote: > Could you try to test with dg-options "-mdejagnu-cpu=power9 -mpowerpc64" all > the time, but still > having that has_arch_ppc64 effective target on aix? > > I'd expect has_arch_ppc64 check to fail on aix 32bit, the error will not be a > problem

[Bug target/106728] Cannot Compile EXE on Shared Network Drive (Windows, MinGW)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106728 --- Comment #4 from Andrew Pinski --- Try the following: g++ -std=c++11 iterate.cpp S -o "Z:\28sec\out.s" If this works, then you should report it to binutils. Though I suspect it is https://sourceware.org/bugzilla/show_bug.cgi?id=25713 which

[Bug target/106728] Cannot Compile EXE on Shared Network Drive (Windows, MinGW)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106728 --- Comment #3 from John Smith --- Please ignore the different machine names in the output I posted above, I forgot to change it in both appearances. I attempted to change it to "machine_name" to avoid confusion but missed it in one spot and I

[Bug target/106728] Cannot Compile EXE on Shared Network Drive (Windows, MinGW)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106728 --- Comment #2 from John Smith --- (In reply to Andrew Pinski from comment #1) > > g++ -std=c++11 iterate.cpp -o "Z:\28sec\out.exe" > > > Does `g++ -c -std=c++11 iterate.cpp -o "\\machine_name\d\performance > testing\t.o" ` work? > > Also if

[Bug target/106459] Compiler crashing for loongarch64-linux-gnu on windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106459 --- Comment #8 from CVS Commits --- The releases/gcc-12 branch has been updated by Chenghua Xu : https://gcc.gnu.org/g:ce753c2792363f1b4cfe2ac56b2da562b34151f3 commit r12-8713-gce753c2792363f1b4cfe2ac56b2da562b34151f3 Author: Chenghua Xu

[Bug target/106459] Compiler crashing for loongarch64-linux-gnu on windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106459 --- Comment #7 from CVS Commits --- The master branch has been updated by Chenghua Xu : https://gcc.gnu.org/g:b169b67d7dafe2b786f87c31d6b2efc603fd880c commit r13-2195-gb169b67d7dafe2b786f87c31d6b2efc603fd880c Author: Chenghua Xu Date: Wed

Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming

On Wed, Aug 24, 2022 at 4:36 PM Alejandro Colomar wrote: > > I'm trying to be nice, and ask for review to make sure I'm not making > some big mistake by accident, and I get disrespect? No thanks. You've been told multiple times that the kernel doesn't use the "standard" names, and *cannot* use

Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming

Alexei, On 8/24/22 20:55, Alejandro Colomar wrote: > Link: > Link: > Signed-off-by: Alejandro Colomar > Nacked-by: Alexei Starovoitov > Nacked-by:

Re: [PATCH] libstdc++: Optimize operator+(string/char*, string/char*) equally

On Wed, 24 Aug 2022 at 23:47, Jonathan Wakely wrote: > > On Wed, 24 Aug 2022 at 23:39, Alexandre Oliva wrote: > > > > On Aug 24, 2022, Jonathan Wakely via Gcc-patches > > wrote: > > > > >* include/bits/basic_string.h (operator+(const string&, > > > const char*)): > > >

[Bug libstdc++/106735] tens of thousands of errors in C++ library

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

Re: [PATCH] libstdc++: Optimize operator+(string/char*, string/char*) equally

On Wed, 24 Aug 2022 at 23:39, Alexandre Oliva wrote: > > On Aug 24, 2022, Jonathan Wakely via Gcc-patches > wrote: > > >* include/bits/basic_string.h (operator+(const string&, > > const char*)): > >Remove naive implementation. > >*

Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming

On Wed, Aug 24, 2022 at 12:04 PM Alejandro Colomar wrote: > > diff --git a/man2/bpf.2 b/man2/bpf.2 > index d05b73ec2..84d1b62e5 100644 > --- a/man2/bpf.2 > +++ b/man2/bpf.2 > @@ -169,34 +169,34 @@ commands: > .EX > union bpf_attr { > struct {/* Used by BPF_MAP_CREATE */ > -

Re: [PATCH] libstdc++: Optimize operator+(string/char*, string/char*) equally

On Aug 24, 2022, Jonathan Wakely via Gcc-patches wrote: >* include/bits/basic_string.h (operator+(const string&, > const char*)): >Remove naive implementation. >* include/bits/basic_string.tcc (operator+(const string&, > const char*)): >Add

[Bug libstdc++/106735] tens of thousands of errors in C++ library

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106735 Jonathan Wakely changed: What|Removed |Added Status|NEW |ASSIGNED Target Milestone|---

[Bug libstdc++/106735] tens of thousands of errors in C++ library

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106735 Marek Polacek changed: What|Removed |Added CC||jwakely.gcc at gmail dot com ---

[Bug libstdc++/106735] tens of thousands of errors in C++ library

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106735 --- Comment #2 from seurer at gcc dot gnu.org --- It it causing so many error messages that emails to the gcc test results list from my autotesters are being rejected as they are 3.9MB in size.

[Bug libstdc++/106735] tens of thousands of errors in C++ library

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106735 Marek Polacek changed: What|Removed |Added Last reconfirmed||2022-08-24 Ever confirmed|0

Re: [PATCH v4] c++: Implement -Wself-move warning [PR81159]

On Tue, Aug 23, 2022 at 05:27:00PM -0400, Jason Merrill wrote: > On 8/23/22 09:39, Marek Polacek wrote: > > + tree arg = CALL_EXPR_ARG (fn, 0); > > + extract_op (arg); > > + if (TREE_CODE (arg) == ADDR_EXPR) > > +arg = TREE_OPERAND (arg, 0); > > + tree type = TREE_TYPE (lhs); > > + lhs =

[Bug libstdc++/106735] New: tens of thousands of errors in C++ library

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106735 Bug ID: 106735 Summary: tens of thousands of errors in C++ library Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug target/100736] ICE: unrecognizable insn

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100736 --- Comment #6 from Segher Boessenkool --- There are so many things here, it's hard to start. Two big things: Firstly, this is not floating point at all, so -ffinite-math-only should not make any difference. We currently abuse CCFP (in a

[Bug fortran/105012] [12/13 Regression] wrf from SPECCPU2017 ICEs during LTO linking since r12-7692-g8db155ddf8cec9

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

Re: [PATCH] c++: Implement C++23 P2071R2 - Named universal character escapes [PR106648]

On 8/21/22 14:18, Jakub Jelinek wrote: Hi! The following patch implements the C++23 P2071R2 - Named universal character escapes paper to support \N{LATIN SMALL LETTER E} etc. I've used Unicode 14.0, there are 144803 character name properties (including the ones generated by Unicode NR1 and NR2

[PATCH] libstdc++: Optimize std::con/disjunction, __and_/__or_, etc

The internal type-level logical operations __and_ and __or_ are currently quite slow to compile for a couple of reasons: 1. They are drop-in replacements for std::con/disjunction, which are rigidly specified to form a type that derives from the first type argument that caused the

[Bug fortran/105012] [12/13 Regression] wrf from SPECCPU2017 ICEs during LTO linking since r12-7692-g8db155ddf8cec9

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105012 --- Comment #17 from anlauf at gcc dot gnu.org --- (In reply to Richard Biener from comment #11) > (In reply to Richard Biener from comment #10) > > likely triggered by the INTENT(out), it looks like gfortran fails to > > properly > >

Re: [PATCH 0/3] picolibc: Add picolibc linking help

Andrew Pinski writes: (removing gcc@ as not appropriate for patch discussions) Thanks for reviewing my patches; I appreciate the time you have taken to think about this. > Why do you need to change the specs to support picolibc? Why not have > the library supply the specs file instead, like

[Bug fortran/106731] ICE on automatic array of derived type with DTIO

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106731 --- Comment #5 from Steve Kargl --- On Wed, Aug 24, 2022 at 07:10:20PM +, federico.perini at gmail dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106731 > > --- Comment #4 from federico --- > The TREE_STATIC assert should

[Bug target/106588] The constraints on most of the patterns in bitmanip.md are broken

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

[Bug target/106632] undefined code causes assembler failure

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

[Bug target/106586] riscv32 still broke with zba_zbb_zbc_zbs, ICE in do_SUBST in C++ code

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106586 Andrew Pinski changed: What|Removed |Added Status|ASSIGNED|RESOLVED Target Milestone|---

[Bug target/106632] undefined code causes assembler failure

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106632 --- Comment #2 from CVS Commits --- The trunk branch has been updated by Andrew Pinski : https://gcc.gnu.org/g:df5204ddd4b8e3a2d02bb3ad5bcdb9d636b02537 commit r13-2190-gdf5204ddd4b8e3a2d02bb3ad5bcdb9d636b02537 Author: Andrew Pinski Date:

[Bug target/106588] The constraints on most of the patterns in bitmanip.md are broken

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106588 --- Comment #3 from CVS Commits --- The trunk branch has been updated by Andrew Pinski : https://gcc.gnu.org/g:df5204ddd4b8e3a2d02bb3ad5bcdb9d636b02537 commit r13-2190-gdf5204ddd4b8e3a2d02bb3ad5bcdb9d636b02537 Author: Andrew Pinski Date:

[Bug target/106586] riscv32 still broke with zba_zbb_zbc_zbs, ICE in do_SUBST in C++ code

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106586 --- Comment #14 from CVS Commits --- The trunk branch has been updated by Andrew Pinski : https://gcc.gnu.org/g:2c721ea9473ad7615bb47b66509097bd254bb839 commit r13-2188-g2c721ea9473ad7615bb47b66509097bd254bb839 Author: Andrew Pinski Date:

[Bug fortran/106731] ICE on automatic array of derived type with DTIO

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106731 --- Comment #4 from federico --- The TREE_STATIC assert should be valid according to what reported in the implementation at report https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48298 But, I can't tell what that means.

[PATCH v3] Many pages: Document fixed-width types with ISO C naming

Kernel __u64 and similar types are ABI-compatible, and mostly API-compatible with ISO C types. User-space programmers don't care about kernel details, and should only use libc types. Document syscalls and structures provided by the Linux kernel as if they used libc types. There's work in the

Re: [Patch] Fortran/OpenMP: Fix strictly structured blocks parsing

Hi Tobias, Am 24.08.22 um 19:47 schrieb Tobias Burnus: This patch is about error diagnostic + an ICE for invalid code. [...] (So far, so good, but then the parsing-code did run into a bug.) For the blocks, the following applies. OpenMP permits either * strictly structured blocks (with

Re: [PATCH] IBM zSystems: Fix function_ok_for_sibcall [PR106355]

On Wed, Aug 17, 2022 at 01:50:45PM +0200, Stefan Schulze Frielinghaus wrote: > For a parameter with BLKmode we cannot use REG_NREGS in order to > determine the number of consecutive registers. Streamlined this with > the implementation of s390_function_arg. > > Fix some indentation whitespace,

[Bug testsuite/106516] New test case gcc.dg/pr104992.c fails on power 10

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106516 --- Comment #8 from Peter Bergner --- (In reply to Kewen Lin from comment #7) > In this patch, I mainly > followed the existing practice vect_int_mult (there are also some similar > effective targets describing target vector support

Re: [PATCH] libstdc++: Fix fallout from P2321R2 pair/tuple enhancements

On Wed, 24 Aug 2022 at 18:00, Patrick Palka via Libstdc++ wrote: > > On Wed, 24 Aug 2022, Patrick Palka wrote: > > > r13-2159-g72886fcc626953 introduced some testsuite regressions in C++23 > > mode: > > > > FAIL: 20_util/pair/requirements/explicit_instantiation/1.cc (test for > > excess

[Bug target/106601] __builtin_bswap16 code gen could be improved with ZBB enabled

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

[Bug target/106600] __builtin_bswap32 is not hooked up for ZBB

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

[Bug testsuite/106690] check_effective_target_bswap should be enabled for riscv if ZBB ISA extension is enabled

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

[Bug testsuite/106690] check_effective_target_bswap should be enabled for riscv if ZBB ISA extension is enabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106690 --- Comment #3 from CVS Commits --- The trunk branch has been updated by Andrew Pinski : https://gcc.gnu.org/g:dec5faa2b2f0d311daa6defd4b4f3c1965748ddf commit r13-2180-gdec5faa2b2f0d311daa6defd4b4f3c1965748ddf Author: Andrew Pinski Date:

[Bug target/106601] __builtin_bswap16 code gen could be improved with ZBB enabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106601 --- Comment #4 from CVS Commits --- The trunk branch has been updated by Andrew Pinski : https://gcc.gnu.org/g:e5e6983c3da53729e58a32af1d531ea74b3dbf5d commit r13-2179-ge5e6983c3da53729e58a32af1d531ea74b3dbf5d Author: Andrew Pinski Date:

[Bug target/106600] __builtin_bswap32 is not hooked up for ZBB

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106600 --- Comment #3 from CVS Commits --- The trunk branch has been updated by Andrew Pinski : https://gcc.gnu.org/g:cb2daf5acce003300ee948a89860c0d13ebcae79 commit r13-2178-gcb2daf5acce003300ee948a89860c0d13ebcae79 Author: Andrew Pinski Date:

Re: [PATCH 0/3] picolibc: Add picolibc linking help

On Wed, Aug 24, 2022 at 11:12 AM Keith Packard via Gcc-patches wrote: > > Picolibc is a C library for embedded systems based on code from newlib > and avr libc. To connect some system-dependent picolibc functions > (like stdio) to an underlying platform, the platform may provide an OS > library.

Re: [PATCH] c: Implement C23 nullptr (N3042)

On Mon, Aug 15, 2022 at 04:03:13PM -0400, Jason Merrill wrote: > On 8/13/22 14:35, Marek Polacek wrote: > > This patch implements the C23 nullptr literal: > > , which is > > intended to replace the problematic definition of NULL which

Re: [PATCH 0/3] picolibc: Add picolibc linking help

On Wed, Aug 24, 2022 at 11:12 AM Keith Packard via Gcc-patches wrote: > > Picolibc is a C library for embedded systems based on code from newlib > and avr libc. To connect some system-dependent picolibc functions > (like stdio) to an underlying platform, the platform may provide an OS > library.

[PATCH v2] c: Implement C23 nullptr (N3042)

On Mon, Aug 15, 2022 at 05:48:34PM +, Joseph Myers wrote: > On Sat, 13 Aug 2022, Marek Polacek via Gcc-patches wrote: > > > This patch also defines nullptr_t in . I'm uncertain about > > the __STDC_VERSION__ version I should be checking. Also, I'm not > > We're using defined

[Bug fortran/103694] [12/13 Regression] ICE in gfc_conv_expr_op, at fortran/trans-expr.c:3882 since r12-3993-gb19bbfb148250536

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103694 --- Comment #8 from CVS Commits --- The master branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:55d8c5409325001c89c35c3d04d425dec9127146 commit r13-2177-g55d8c5409325001c89c35c3d04d425dec9127146 Author: Harald Anlauf Date:

[PATCH 0/3] picolibc: Add picolibc linking help

Picolibc is a C library for embedded systems based on code from newlib and avr libc. To connect some system-dependent picolibc functions (like stdio) to an underlying platform, the platform may provide an OS library. This OS library must follow the C library in the link command line. In current

[PATCH 0/3] picolibc: Add picolibc linking help

Picolibc is a C library for embedded systems based on code from newlib and avr libc. To connect some system-dependent picolibc functions (like stdio) to an underlying platform, the platform may provide an OS library. This OS library must follow the C library in the link command line. In current

[PATCH 3/3] picolibc: Add '--oslib=' option when default C library is picolibc

This option allows targets to insert an OS library after the C library in the LIB_PATH spec file fragment. This library maps a few POSIX APIs used by picolibc to underlying system capabilities. For example, picolibc provides 'libsemihost' on various targets which maps these APIs to semihosting

[PATCH 3/3] picolibc: Add '--oslib=' option when default C library is picolibc

This option allows targets to insert an OS library after the C library in the LIB_PATH spec file fragment. This library maps a few POSIX APIs used by picolibc to underlying system capabilities. For example, picolibc provides 'libsemihost' on various targets which maps these APIs to semihosting

[PATCH 1/3] picolibc: Allow default libc to be specified to configure

The default C library is normally computed based on the target triplet. However, for embedded systems, it can be useful to leave the triplet alone while changing which C library is used by default. Other C libraries may still be available on the system so the compiler and can be used by specifying

[PATCH 2/3] picolibc: Add newlib and picolibc as default C library choices

Signed-off-by: Keith Packard --- gcc/config.gcc | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/gcc/config.gcc b/gcc/config.gcc index f8b6da4f4e7..0aa4bd6c3dd 100644 --- a/gcc/config.gcc +++ b/gcc/config.gcc @@ -639,7 +639,7 @@ case ${target} in esac # Common C

[PATCH 1/3] picolibc: Allow default libc to be specified to configure

The default C library is normally computed based on the target triplet. However, for embedded systems, it can be useful to leave the triplet alone while changing which C library is used by default. Other C libraries may still be available on the system so the compiler and can be used by specifying

[PATCH 2/3] picolibc: Add newlib and picolibc as default C library choices

Signed-off-by: Keith Packard --- gcc/config.gcc | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/gcc/config.gcc b/gcc/config.gcc index f8b6da4f4e7..0aa4bd6c3dd 100644 --- a/gcc/config.gcc +++ b/gcc/config.gcc @@ -639,7 +639,7 @@ case ${target} in esac # Common C

Re: [PATCH] Fortran: improve error recovery while simplifying size of bad array [PR103694]

Dear Harald, On 23.08.22 22:29, Harald Anlauf via Fortran wrote: the simplification of the size of an array with a bad decl should not be successful. Improve the error recovery for such a situation. [...] Regtested on x86_64-pc-linux-gnu. The PR is marked as a 12/13 regression. Will

[Patch] Fortran/OpenMP: Fix strictly structured blocks parsing

This patch is about error diagnostic + an ICE for invalid code. Before the patch, gfortran/f951 showed: ... Error: 'ancestor' device modifier not preceded by 'requires' directive with 'reverse_offload' clause 18 | end block | 1 Error: Expecting END PROGRAM statement at (1) gfortran:

[Bug debug/106718] GCC does not follow DWARF5 standard for DW_AT_ranges and DW_FORM_rnglistx

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106718 Navid Rahimi changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED

[Bug debug/106718] GCC does not follow DWARF5 standard for DW_AT_ranges and DW_FORM_rnglistx

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106718 --- Comment #2 from Navid Rahimi --- Thanks for clarifying it. I was able to fix a bug somewhere else with your explanation.

[Bug fortran/106731] ICE on automatic array of derived type with DTIO

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

[Bug c++/106652] [C++23] P1467 - Extended floating-point types and standard names

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106652 --- Comment #4 from joseph at codesourcery dot com --- Regarding mangling: I expect this change should fix bug 85518. General: I expect some glibc header changes might be appropriate, where they currently assume __FloatN keywords aren't

Re: [PATCH] libstdc++: Fix fallout from P2321R2 pair/tuple enhancements

On Wed, 24 Aug 2022, Patrick Palka wrote: > r13-2159-g72886fcc626953 introduced some testsuite regressions in C++23 > mode: > > FAIL: 20_util/pair/requirements/explicit_instantiation/1.cc (test for > excess errors) > FAIL: 20_util/tuple/53648.cc (test for excess errors) > FAIL:

[Bug target/102146] [11 regression] several test cases fails after r11-8940

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102146 Segher Boessenkool changed: What|Removed |Added Resolution|--- |FIXED

[Bug c++/106652] [C++23] P1467 - Extended floating-point types and standard names

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106652 --- Comment #3 from Jakub Jelinek --- Testcase for the already implemented features: // P1467R9 - Extended floating-point types and standard names. // { dg-do compile { target c++23 } } // { dg-options "" } namespace std { #ifdef

[Bug middle-end/106725] LTO semantics for __attribute__((leaf))

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106725 --- Comment #2 from Daniel Thornburgh --- (In reply to Richard Biener from comment #1) > If GCC, with LTO, would partition the program into two LTRANS partitions, > one containing main and bar and one containing foo then applying this >

[PATCH] libstdc++: Fix fallout from P2321R2 pair/tuple enhancements

r13-2159-g72886fcc626953 introduced some testsuite regressions in C++23 mode: FAIL: 20_util/pair/requirements/explicit_instantiation/1.cc (test for excess errors) FAIL: 20_util/tuple/53648.cc (test for excess errors) FAIL: 20_util/tuple/cons/noexcept_specs.cc (test for excess errors)

[Bug target/106728] Cannot Compile EXE on Shared Network Drive (Windows, MinGW)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106728 --- Comment #1 from Andrew Pinski --- > g++ -std=c++11 iterate.cpp -o "Z:\28sec\out.exe" Does `g++ -c -std=c++11 iterate.cpp -o "\\machine_name\d\performance testing\t.o" ` work? Also if it is failing like this, it is not a problem with GCC

[Bug target/106724] logical-op-non-short-circuit maybe should be 1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106724 --- Comment #4 from Andrew Pinski --- (In reply to Richard Biener from comment #3) > we usually define logical-op-non-short-circuit based on branch cost Right, I think this definition was copied from the MIPS backend even which is wrong there

[Bug target/106723] Unreplaced mode/code attributes in aarch64/arm backends

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106723 --- Comment #3 from Richard Earnshaw --- I think we should error if the name matches some iteration values, but not others. If is valid in the assembler output 'as-is' then it's bad form to have an attribute that overloads this - and the fix

Re: Counting static __cxa_atexit calls

Hello, On Wed, 24 Aug 2022, Florian Weimer wrote: > > On Wed, 24 Aug 2022, Florian Weimer wrote: > > > >> > Isn't this merely moving the failure point from exception-at-ctor to > >> > dlopen-fails? > >> > >> Yes, and that is a soft error that can be handled (likewise for > >> pthread_create).

[Bug middle-end/91213] Missed optimization: (sub X Y) -> (xor X Y) when Y <= X and isPowerOf2(X + 1)

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

[Bug target/106701] Compiler does not take into account number range limitation to avoid subtract from immediate

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106701 Andrew Pinski changed: What|Removed |Added Resolution|--- |DUPLICATE

[Bug middle-end/91213] Missed optimization: (sub X Y) -> (xor X Y) when Y <= X and isPowerOf2(X + 1)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91213 Andrew Pinski changed: What|Removed |Added CC||jens.seifert at de dot ibm.com ---

[PATCH][RFC] Uninit diagnostic consistency

I've figured that while the uninit diagnostic is intended to diagnose all cases where we cannot prove the must-uninit paths are not reaching any use the actual implementation errors on the wrong side in two places. First the recently added use_cannot_happen computes the must-uninit predicate

[Bug c++/106652] [C++23] P1467 - Extended floating-point types and standard names

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106652 Jakub Jelinek changed: What|Removed |Added CC||jason at gcc dot gnu.org,

[committed] libstdc++: Fix regression in std::stable_sort

Tested powerpc64le-linux, pushed to trunk. No backport needed as the regression is only on trunk. -- >8 -- The recent change to split out the cold path of std::stable_sort caused a regression for some Qt code. The problem is that the library now adds a value of type ptrdiff_t to the iterator,

Re: Counting static __cxa_atexit calls

* Michael Matz: > Hello, > > On Wed, 24 Aug 2022, Florian Weimer wrote: > >> > Isn't this merely moving the failure point from exception-at-ctor to >> > dlopen-fails? >> >> Yes, and that is a soft error that can be handled (likewise for >> pthread_create). > > Makes sense. Though that actually

[Bug libstdc++/106669] incorrect definition of viewable_range ("more madness with move-only views")

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106669 Hannes Hauswedell changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

Re: [PATCH Rust front-end v2 01/37] Use DW_ATE_UTF for the Rust 'char' type

On 8/24/22 04:59, herron.phi...@googlemail.com wrote: From: Tom Tromey The Rust 'char' type should use the DWARF DW_ATE_UTF encoding. The DWARF changes are OK. --- gcc/dwarf2out.cc | 23 ++- 1 file changed, 22 insertions(+), 1 deletion(-) diff --git

Re: [PATCH Rust front-end v2 01/37] Use DW_ATE_UTF for the Rust 'char' type

On 8/24/22 04:59, herron.phi...@googlemail.com wrote: From: Tom Tromey The Rust 'char' type should use the DWARF DW_ATE_UTF encoding. The DWARF changes are OK. --- gcc/dwarf2out.cc | 23 ++- 1 file changed, 22 insertions(+), 1 deletion(-) diff --git

[Bug c++/106734] [requires] std::same_as in compound requirements doesn't produce expected result

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106734 --- Comment #7 from Jonathan Wakely --- decltype(bar) and decltype((bar)) are not the same type.

[Bug c++/106652] [C++23] P1467 - Extended floating-point types and standard names

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106652 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment

[Bug c++/106734] [requires] std::same_as in compound requirements doesn't produce expected result

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106734 jakob at schmutz dot co.uk changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

Re: [PATCH] libstdc++: Optimize operator+(string/char*, string/char*) equally

On Wed, 24 Aug 2022 at 07:17, Will Hawkins wrote: > > Until now operator+(char*, string) and operator+(string, char*) had > different performance characteristics. The former required a single > memory allocation and the latter required two. This patch makes the > performance equal. > >

[Bug c++/106734] [requires] std::same_as in compound requirements doesn't produce expected result

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106734 --- Comment #5 from jakob at schmutz dot co.uk --- oh I see `std::same_as` is false

[Bug c++/106734] [requires] std::same_as in compound requirements doesn't produce expected result

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106734 --- Comment #4 from jakob at schmutz dot co.uk --- (In reply to Jonathan Wakely from comment #3) > (In reply to jakob from comment #0) > > Bar bar; > > constexpr bool same = requires > > { > > { bar } -> std::same_as; > >

[PATCH v2 2/2 resend] LoongArch: add model attribute

On Wed, 2022-08-24 at 22:08 +0800, Xi Ruoyao wrote: > v1 -> v2: > >  * Avoid introduce of SYMBOL_PCREL32, use SYMBOL_PCREL for 32-bit PC >    relative. >  * Rebase onto a bug fix ([1/2] in the series) to avoid merge conflict. >  * Fix missed ChangeLog entries. Resend because my mail client has

[PATCH] LoongArch: testsuite: refine __tls_get_addr tests with tls_native

If GCC is not built with a working linker for the target (developers occansionally build such a "minimal" GCC for testing and debugging), TLS will be emulated and __tls_get_addr won't be used. Refine those tests depending on __tls_get_addr with tls_native to avoid test failures.

  1   2   3   >