Re: [PATCH v3 1/4] LoongArch: improved target configuration interface

On Sat, 2023-09-09 at 10:46 +0800, Yang Yujie wrote: > The next option I can think of would be MULTILIB_EXTRA_OPTS, where > -fmultiflags > fit in nicely.  However, these options won't reach the toplevel builds, and > tweaking config-ml.in for getting it there would be quite tedious and perhaps >

[Bug c++/111352] Inconsistent constructor behavior associated with auto lambda

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111352 --- Comment #4 from Andrew Pinski --- also see https://en.wikipedia.org/wiki/Most_vexing_parse for more explanation on why this mistake in GCC happened.

[Bug c++/111352] Inconsistent constructor behavior associated with auto lambda

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111352 Andrew Pinski changed: What|Removed |Added Last reconfirmed||2023-09-09 Ever confirmed|0

[Bug target/111354] [7/10/12 regression] The instructions of the DPDK demo program are different and run time increases.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111354 --- Comment #2 from Andrew Pinski --- It might be the case DPDK is tuned towards xeon's rather than the i series also.

[Bug target/111354] [7/10/12 regression] The instructions of the DPDK demo program are different and run time increases.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111354 --- Comment #1 from Andrew Pinski --- First off the performance is difference is die to micro-arch issues with unaligned stores of 256 bits. Also iirc rte_mov128blocks is tuned at copying blocks which are aligned at least to 32 bytes wide.

Re: [RFC] gcc: xtensa: use salt/saltu in xtensa_expand_scc

Hi! On 2023/09/07 23:22, Max Filippov wrote: > gcc/ > * config/xtensa/predicates.md (xtensa_cstoresi_operator): Add > unsigned comparisons. > * config/xtensa/xtensa.cc (xtensa_expand_scc): Add code > generation of salt/saltu instructions. > * config/xtensa/xtensa.h

[Bug libstdc++/111347] Memory leak loading a shared library built with --static-libsdtc++ when version script is used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111347 --- Comment #3 from George Yunaev --- Indeed making a unique symbol local results in a leak.

[PATCH] RISC-V: Add VLS modes VEC_PERM support[PR111311]

This patch add VLS modes VEC_PERM support which fix these following FAILs in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111311: FAIL: gcc.dg/tree-ssa/forwprop-40.c scan-tree-dump-times optimized "BIT_FIELD_REF" 0 FAIL: gcc.dg/tree-ssa/forwprop-40.c scan-tree-dump-times optimized

[Committed] RISC-V: Fix VLS floating-point operations predicate

VLS vfadd should depend on ZVFH instead of ZVFHMIN. Obvious fix and committed. gcc/ChangeLog: * config/riscv/vector-iterators.md: Fix floating-point operations predicate. --- gcc/config/riscv/vector-iterators.md | 24 1 file changed, 12 insertions(+), 12

[Bug target/111354] New: [7/10/12 regression] The instructions of the DPDK demo program are different and run time increases.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111354 Bug ID: 111354 Summary: [7/10/12 regression] The instructions of the DPDK demo program are different and run time increases. Product: gcc Version: 10.3.0 Status:

[Bug go/90685] failure of go in gcc-9.1.0 to build in i686-pc-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90685 Eric Gallager changed: What|Removed |Added Host||i?86-*-* --- Comment #3 from Eric

[Bug go/90685] failure of go in gcc-9.1.0 to build in i686-pc-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90685 Eric Gallager changed: What|Removed |Added Status|UNCONFIRMED |NEW CC|

[Bug libstdc++/111351] constexpr std::string objects permitted to escape constant evaluation when SSO

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111351 --- Comment #1 from Arthur O'Dwyer --- (Author of the blog post here.) In contrast to James' view, I think the libstdc++/MSVC behavior is relatively easy to explain; I think libc++'s `if consteval` approach is baroque and confusing. [That is,

Re: [PATCH v3 1/4] LoongArch: improved target configuration interface

On Thu, Sep 07, 2023 at 07:54:41PM +0800, Yang Yujie wrote: > On Thu, Sep 07, 2023 at 05:47:36PM +0800, Xi Ruoyao wrote: > > On Thu, 2023-09-07 at 17:31 +0800, Yang Yujie wrote: > > > > This is bad.  It makes BOOT_CFLAGS=-mlasx or CFLAGS_FOR_TARGET=-mlasx > > > > silently ignored so we cannot test

[Bug libstdc++/111353] New: bits/new_allocator.h: No such file or directory in freestanding C++ toolchain

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111353 Bug ID: 111353 Summary: bits/new_allocator.h: No such file or directory in freestanding C++ toolchain Product: gcc Version: 14.0 Status: UNCONFIRMED Severity:

[Bug libstdc++/111347] Memory leak loading a shared library built with --static-libsdtc++ when version script is used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111347 --- Comment #2 from George Yunaev --- Adding -fno-gnu-unique to the makefile for libleak.so doesn't remove the leak.

Re: [PATCH V3] Support folding min(poly,poly) to const

Committed, thanks Richard and Juzhe. On 2023/9/8 16:57, 钟居哲 wrote: Thanks Richard. LGTM again from RISC-V side :). juzhe.zh...@rivai.ai *From:* Richard Sandiford *Date:* 

Re: [PATCH v2 2/5] RISC-V: Add Types for Un-Typed zc Instructions

On 9/8/23 12:16, Edwin Lu wrote: This patch adds types to the untyped zc instructions. Creates a new types "pushpop" and "mvpair" for now gcc/ChangeLog: * config/riscv/riscv.md: Add "csr" type * config/riscv/zc.md: Update types OK. Note that once we finish this exercise,

Re: [PATCH v2 1/5] RISC-V: Update Types for Vector Instructions

On 9/8/23 12:16, Edwin Lu wrote: This patch adds types to vector instructions that were added after or were missed by the original patch https://gcc.gnu.org/pipermail/gcc-patches/2023-August/628594.html gcc/ChangeLog: * config/riscv/autovec-opt.md: Update types *

[Bug c++/111352] Inconsistent constructor behavior associated with auto lambda

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111352 --- Comment #2 from Andrew Pinski --- 99% sure this is because we start parsing as a function declaration and then see it is not but we errored out already.

[Bug c++/111352] Inconsistent constructor behavior associated with auto lambda

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111352 Peter Fletcher changed: What|Removed |Added CC||peter.fletcher@bandicootima

[Bug c++/111352] New: Inconsistent constructor behavior associated with auto lambda

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111352 Bug ID: 111352 Summary: Inconsistent constructor behavior associated with auto lambda Product: gcc Version: 11.4.0 Status: UNCONFIRMED Severity: normal

[Bug libstdc++/111351] New: constexpr std::string objects permitted to escape constant evaluation when SSO

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111351 Bug ID: 111351 Summary: constexpr std::string objects permitted to escape constant evaluation when SSO Product: gcc Version: 14.0 Status: UNCONFIRMED

[Bug tree-optimization/109878] missed simplifications of MAX and MIN

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109878 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Assignee|unassigned at gcc

[Bug target/111350] gcc.target/i386/avx512fp16-vfcmulcph-1b.c and friends fail on x86_64-apple-darwin21

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111350 --- Comment #5 from Iain Sandoe --- (In reply to Iain Sandoe from comment #4) > (In reply to Francois-Xavier Coudert from comment #3) > > Clang: 14.0.0 build 1400 > > CLT: 14.2.0.0.1.1668646533 > > ah, it seems the vfcmulcph insn, at least, is

[Bug target/111350] gcc.target/i386/avx512fp16-vfcmulcph-1b.c and friends fail on x86_64-apple-darwin21

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111350 --- Comment #4 from Iain Sandoe --- (In reply to Francois-Xavier Coudert from comment #3) > Clang: 14.0.0 build 1400 > CLT: 14.2.0.0.1.1668646533 ah, it seems the vfcmulcph insn, at least, is not supported before XC14, and it gives the error

gcc-12-20230908 is now available

Snapshot gcc-12-20230908 is now available on https://gcc.gnu.org/pub/gcc/snapshots/12-20230908/ 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 target/111350] gcc.target/i386/avx512fp16-vfcmulcph-1b.c and friends fail on x86_64-apple-darwin21

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111350 --- Comment #3 from Francois-Xavier Coudert --- Clang: 14.0.0 build 1400 CLT: 14.2.0.0.1.1668646533

[Bug target/111350] gcc.target/i386/avx512fp16-vfcmulcph-1b.c and friends fail on x86_64-apple-darwin21

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111350 --- Comment #2 from Iain Sandoe --- (In reply to Andrew Pinski from comment #1) > This seems like a bug in darwin's assembler as all of those registers are > distinct ... indeed, it does look that way - what version of Xcode?

[Bug target/111350] gcc.target/i386/avx512fp16-vfcmulcph-1b.c and friends fail on x86_64-apple-darwin21

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111350 --- Comment #1 from Andrew Pinski --- This seems like a bug in darwin's assembler as all of those registers are distinct ...

[Bug target/111350] New: gcc.target/i386/avx512fp16-vfcmulcph-1b.c and friends fail on x86_64-apple-darwin21

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111350 Bug ID: 111350 Summary: gcc.target/i386/avx512fp16-vfcmulcph-1b.c and friends fail on x86_64-apple-darwin21 Product: gcc Version: 14.0 Status: UNCONFIRMED

[Bug tree-optimization/111349] `Optimize (a CMP CST1) ? max : a` pattern's cmp is missing :c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111349 Andrew Pinski changed: What|Removed |Added Last reconfirmed||2023-09-08

[Bug tree-optimization/111349] New: `Optimize (a CMP CST1) ? max : a` pattern's cmp is missing :c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111349 Bug ID: 111349 Summary: `Optimize (a CMP CST1) ? max : a` pattern's cmp is missing :c Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords:

[Bug tree-optimization/111348] `(a CMP b) ? minmax : minmax` pattern missing :c on CMP

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111348 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug libstdc++/111347] Memory leak loading a shared library built with --static-libsdtc++ when version script is used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111347 --- Comment #1 from Andrew Pinski --- I am pretty sure _ZNSt8messagesIwE2idE is marked as GNU unique

[Bug tree-optimization/111348] `(a CMP b) ? minmax : minmax` pattern missing :c on CMP

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111348 --- Comment #1 from Andrew Pinski --- Need a testcase for this though.

[Bug tree-optimization/111348] New: `(a CMP b) ? minmax : minmax` pattern missing :c on CMP

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111348 Bug ID: 111348 Summary: `(a CMP b) ? minmax : minmax` pattern missing :c on CMP Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: internal-improvement,

[Bug libstdc++/111347] New: Memory leak loading a shared library built with --static-libsdtc++ when version script is used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111347 Bug ID: 111347 Summary: Memory leak loading a shared library built with --static-libsdtc++ when version script is used Product: gcc Version: 13.2.0 Status: UNCONFIRMED

[Bug tree-optimization/111346] `X <= MINMAX` pattern is missing :c on the cmp

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111346 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug tree-optimization/111346] New: `X <= MINMAX` pattern is missing :c on the cmp

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111346 Bug ID: 111346 Summary: `X <= MINMAX` pattern is missing :c on the cmp Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: internal-improvement, missed-optimization

[Bug tree-optimization/111345] `X % Y is smaller than Y.` pattern could be simpified

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111345 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug tree-optimization/111345] New: `X % Y is smaller than Y.` pattern could be simpified

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111345 Bug ID: 111345 Summary: `X % Y is smaller than Y.` pattern could be simpified Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: internal-improvement Severity:

[Bug c/29280] misleading warning for assignment used as truth construct

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29280 Andrew Pinski changed: What|Removed |Added CC||markgaleck at gmail dot com --- Comment

[Bug c/111344] bogus "warning: suggest parentheses around assignment used as truth value [-Wparentheses]"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111344 Andrew Pinski changed: What|Removed |Added Resolution|INVALID |DUPLICATE --- Comment #7 from Andrew

[Bug c/111344] bogus "warning: suggest parentheses around assignment used as truth value [-Wparentheses]"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111344 --- Comment #6 from Mark Galeck --- (In reply to Andrew Pinski from comment #5) > Reduced: > ``` > int *f(const char*); > int *g(int*); > int main() > { > int* pdir; > int* pentry; > > pdir = f("d"); > > while (pentry = g(pdir)) ; > } >

Re: [PATCH] fortran: Remove redundant tree walk to delete element

Am 08.09.23 um 12:04 schrieb Mikael Morin via Gcc-patches: Hello, this avoids some redundant work in the symbol deletion code, which is used a lot by the parser to cancel statements that fail to match in the end. I haven't tried to measure the performance effect, if any, on a pathological

[Bug c/111344] bogus "warning: suggest parentheses around assignment used as truth value [-Wparentheses]"

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

[Bug c/111344] bogus "warning: suggest parentheses around assignment used as truth value [-Wparentheses]"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111344 --- Comment #4 from Mark Galeck --- I am getting seemingly bogus "warning: suggest parentheses around assignment used as truth value [-Wparentheses]". I see long time ago there were such reports, fixed at the time, but this is happening now

[Bug c/111344] bogus "warning: suggest parentheses around assignment used as truth value [-Wparentheses]"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111344 --- Comment #3 from Mark Galeck --- Created attachment 55859 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55859=edit preprocessed SSCCE foobar.i

[Bug c/111344] bogus "warning: suggest parentheses around assignment used as truth value [-Wparentheses]"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111344 --- Comment #2 from Mark Galeck --- Created attachment 55858 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55858=edit preprocessed SSCCE foobar.i

[Bug target/111343] [SH] Including in C++23 causes an ICE with -m4-single-only

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111343 --- Comment #1 from Andrew Pinski --- Most likely introduced by r13-2887-gb04208895fed34171eac6 which implements C++23 extended floating point types ... And the use of _Float32 but now sizeof(double) == sizeof(float) == sizeof(_Float32)

[Bug c/111344] bogus "warning: suggest parentheses around assignment used as truth value [-Wparentheses]"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111344 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |WAITING Ever confirmed|0

[COMMITTED] [frange] Revert relation handling in LTGT_EXPR.

In trying to come up with a missing testcase for commit 979e0fbf53cd, I've realized the patch doesn't catch anything. A relation of VREL_EQ in foperator_ltgt::fold_range() is either both arguments the same (x LTGT_EXPR x), which we should never emit, or two arguments that are actually the same,

[Bug c/111344] New: bogus "warning: suggest parentheses around assignment used as truth value [-Wparentheses]"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111344 Bug ID: 111344 Summary: bogus "warning: suggest parentheses around assignment used as truth value [-Wparentheses]" Product: gcc Version: unknown Status: UNCONFIRMED

[Bug c++/111343] New: [SH] Including in C++23 causes an ICE with -m4-single-only

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111343 Bug ID: 111343 Summary: [SH] Including in C++23 causes an ICE with -m4-single-only Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal

[Bug c++/111075] ICE on g++.dg/torture/tail-padding1.C on darwin

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111075 --- Comment #1 from Francois-Xavier Coudert --- Preprocessed source: % cat a-tail-padding1.ii # 0 "/Users/fx/gcc-upstream/gcc/testsuite/g++.dg/torture/tail-padding1.C" # 0 "" # 0 "" # 1

[Bug modula2/111330] [13 Regression] Bootstrap failure building SeqFile.lo

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111330 --- Comment #4 from Jakub Jelinek --- Seems sed -i -e 's/ -fcase / -fcase -Wno-all /' libgm2/*/Makefile.am sed -i -e 's/ -fcase / -fcase -Wno-all /' libgm2/*/Makefile.in can work as a work-around for this bug, but it would still be nice to

[Bug c++/106310] [12/13 Regression] lookup after this-> seems wrong for dependent lookup since r12-6754-g30f2c22def739211

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

[Bug target/111342] New: ICE for g++.target/i386/pr105980.C on x86_64-apple-darwin21

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111342 Bug ID: 111342 Summary: ICE for g++.target/i386/pr105980.C on x86_64-apple-darwin21 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

Ping: [PATCH] testsuite: Add test for already-fixed issue with _Pragma expansion [PR90400]

Hello- May I please ping this one? It's adding a testcase prior to closing the PR. Thanks! https://gcc.gnu.org/pipermail/gcc-patches/2023-August/628488.html -Lewis On Fri, Aug 25, 2023 at 4:46 PM Lewis Hyatt wrote: > > Hello- > > This is adding a testcase for a PR that was already incidentally

[Bug c++/105512] compilation with -fmodules-ts and std=c++20 leads to segfault

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105512 Gerrit Albrecht changed: What|Removed |Added CC||m...@gerrit-albrecht.de --- Comment

[Bug modula2/111330] [13 Regression] Bootstrap failure building SeqFile.lo

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111330 --- Comment #3 from Jakub Jelinek --- So, narrowed it down to Fedora build doing essentially (stripped down from all languages etc.): CC=gcc \ CXX=g++ \ CFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -Wall -Wformat-security

[PATCH, pushed] testsuite: adjust for darwin linker warning

Pushed as obvious to fix two testsuite FAILs on darwin with recent macOS linkers when -no_pie is passed. FX 0001-testsuite-adjust-for-darwin-linker-warning.patch Description: Binary data

[Bug modula2/111330] [13 Regression] Bootstrap failure building SeqFile.lo

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111330 --- Comment #2 from Jakub Jelinek --- Though, bisection points to r13-7651-g824a37d0bfa9f5c232 as first commit which fails to build.

[Bug fortran/111339] bounds-check does not detect nonconforming functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111339 anlauf at gcc dot gnu.org changed: What|Removed |Added Ever confirmed|0 |1

[Bug fortran/111341] New: Elemental operator on zero-sized array seg-faults

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111341 Bug ID: 111341 Summary: Elemental operator on zero-sized array seg-faults Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal Priority: P3

[PATCH v3] c++: Move consteval folding to cp_fold_r

On Thu, Sep 07, 2023 at 02:32:51PM -0400, Jason Merrill wrote: > On 9/7/23 11:23, Marek Polacek wrote: > > On Tue, Sep 05, 2023 at 04:36:34PM -0400, Jason Merrill wrote: > > > On 9/5/23 15:59, Marek Polacek wrote: > > > > On Tue, Sep 05, 2023 at 10:52:04AM -0400, Jason Merrill wrote: > > > > > On

[Bug modula2/111330] [13 Regression] Bootstrap failure building SeqFile.lo

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

[Bug modula2/111330] [13 Regression] Bootstrap failure building SeqFile.lo

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111330 --- Comment #1 from Jakub Jelinek --- So far bisected to between r13-7647 (builds fine) and r13-7660 (fails to build), and can reproduce even without bootstrap. I suspect r13-7650 but will confirm it or not soon.

Cauldron schedule: diagnostics and security features talks

Hello, I want to begin by apologizing because I know from first hand experience that scheduling can be an immensely painful job. The Cauldron 2023 schedule[1] looks packed and I noticed that Qing and David's talks on security features and diagnostics respectively are in the same time slot.

Re: [committed] libstdc++: Add Filesystem TS and std::stacktrace symbols to libstdc++exp.a

I forgot to say: Tested x86_64-linux and aarch64-linux, built for avr, arm-eabi and cris-elf. Pushed to trunk. On Fri, 8 Sept 2023 at 18:09, Jonathan Wakely via Libstdc++ wrote: > > This consolidates the three static archives for extensions into one, so > that -lstdc++exp can be used to

[PATCH v2 2/5] RISC-V: Add Types for Un-Typed zc Instructions

This patch adds types to the untyped zc instructions. Creates a new types "pushpop" and "mvpair" for now gcc/ChangeLog: * config/riscv/riscv.md: Add "csr" type * config/riscv/zc.md: Update types Signed-off-by: Edwin Lu --- Changes in V2: - Change "csr" type to "pushpop" and

[PATCH v2 1/5] RISC-V: Update Types for Vector Instructions

This patch adds types to vector instructions that were added after or were missed by the original patch https://gcc.gnu.org/pipermail/gcc-patches/2023-August/628594.html gcc/ChangeLog: * config/riscv/autovec-opt.md: Update types * config/riscv/autovec.md: likewise

[PATCH v2 0/5] RISC-V: Add Types to Untyped Instructions

This series adds types to the remaining untyped instructions. Related Discussion: https://inbox.sourceware.org/gcc-patches/12fb5088-3f28-0a69-de1e-f387371a5...@gmail.com/ Also enables assert which checks to make sure every instruction has a type All patches were tested with rv32/rv64

[committed] libstdc++: Update outdated default -std in testing docs

Pushed to gcc-13 (I've removed/rewritten this text on trunk). I'll push to the older branches too. -- >8 -- libstdc++-v3/ChangeLog: * doc/xml/manual/test.xml: Update reference to -std=gnu++14 as the default. * doc/html/manual/test.html: Regenerate. ---

[PATCH] match: Don't sink comparisons into vec_cond operands.

Hi, on riscv gcc.dg/pr70252.c ICEs at gimple-isel.cc:283. This is because we created the gimple statement mask__7.36_170 = VEC_COND_EXPR ; during vrp2. What happens is that, starting with maskdest = (vec_cond mask1 1 0) >= (vec_cond mask2 1 0) we fold to maskdest = mask1 >= (vec_cond

[Bug tree-optimization/111336] [14 Regression] Wrong code at -O2/3 since r14-2472-g14b10ff30ad

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111336 --- Comment #5 from Andrew Pinski --- (In reply to Xi Ruoyao from comment #4) > (In reply to Andrew Pinski from comment #3) > > Note -fwrapv or -fno-ivopts causes the issue to disappear. > > Does your patch for PR111331 work for this one too?

[Bug tree-optimization/111336] [14 Regression] Wrong code at -O2/3 since r14-2472-g14b10ff30ad

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

[Bug libstdc++/104167] Implement C++20 std::chrono::utc_clock, std::chrono::tzdb etc.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104167 --- Comment #14 from CVS Commits --- The releases/gcc-13 branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:294d11837367455499786578377c530a0238b6ca commit r13-7782-g294d11837367455499786578377c530a0238b6ca Author: Jonathan

Re: [PATCH v2] libstdc++: Fix -Wunused-parameter warnings

On Thu, 7 Sept 2023 at 20:30, Pekka Seppänen wrote: > > On 7.9.2023 19:40, Jonathan Wakely wrote: > > On 29/08/23 15:04 +0300, Pekka Seppänen wrote: > >> libstdc++: Fix -Wunused-parameter warnings when _GLIBCXX_USE_WCHAR_T is > >> not defined. > >> > >> libstdc++-v3/ChangeLog: > >> > >> *

[Bug tree-optimization/111336] [14 Regression] Wrong code at -O2/3 since r14-2472-g14b10ff30ad

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111336 Xi Ruoyao changed: What|Removed |Added CC||xry111 at gcc dot gnu.org --- Comment #4

[committed] libstdc++: Add Filesystem TS and std::stacktrace symbols to libstdc++exp.a

This consolidates the three static archives for extensions into one, so that -lstdc++exp can be used to provide the definitions of all unstable library features. The libstdc++_libbacktrace.a archive is now just a "noinst" convenience library that is only used during the build, not installed. Its

Re: [PATCH] libstdc++: Reduce output of 'make check'

On Thu, 7 Sept 2023 at 14:32, Jonathan Wakely via Libstdc++ wrote: > > Any objections to this change? Pushed to trunk now. > > -- >8 -- > > This removes the 39 lines of shell commands that get echoed when > starting the testsuite. The fact that near the end of that output it > prints `echo

Re: [PATCH] libbacktrace: Fix unconditional -Werror

On Fri, 8 Sept 2023 at 11:10, Jonathan Wakely wrote: > > The patch looks good, thanks. I noticed the unconditional -Werror the other > day when testing a build on avr. > > N.B. All patches should go to gcc-patches (as well as a more specific list > like libstdc++ when appropriate). > > OK for

[Bug tree-optimization/111336] [14 Regression] Wrong code at -O2/3 since r14-2472-g14b10ff30ad

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111336 --- Comment #3 from Andrew Pinski --- Note -fwrapv or -fno-ivopts causes the issue to disappear.

[Bug libstdc++/111050] [11/12/13/14 Regression] ABI break in _Hash_node_value_base since GCC 11

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111050 --- Comment #7 from TC --- Confirmed with my reporter that this fixes their actual code too.

Re: [PATCH 01/13] [APX EGPR] middle-end: Add insn argument to base_reg_class

On 8/31/23 04:20, Hongyu Wang wrote: @@ -2542,6 +2542,8 @@ the code of the immediately enclosing expression (@code{MEM} for the top level of an address, @code{ADDRESS} for something that occurs in an @code{address_operand}). @var{index_code} is the code of the corresponding index

[PATCH] Allow target attributes in non-gnu namespaces

Currently there are four static sources of attributes: - LANG_HOOKS_ATTRIBUTE_TABLE - LANG_HOOKS_COMMON_ATTRIBUTE_TABLE - LANG_HOOKS_FORMAT_ATTRIBUTE_TABLE - TARGET_ATTRIBUTE_TABLE All of the attributes in these tables go in the "gnu" namespace. This means that they can use the traditional GNU

[Bug c++/99599] [11/12/13/14 Regression] Concepts requirement falsely reporting cyclic dependency, breaks tag_invoke pattern

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99599 --- Comment #18 from CVS Commits --- The master branch has been updated by Patrick Palka : https://gcc.gnu.org/g:2154bcd6d43cfd821ca70e1583880c4ed955355d commit r14-3809-g2154bcd6d43cfd821ca70e1583880c4ed955355d Author: Patrick Palka Date:

[Bug target/111340] gcc.dg/bitint-12.c fails on x86_64-apple-darwin or fails on x86_64-linux-gnu with -fPIE

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

[Bug target/110960] TestSatWidenMulPairwiseAdd in the Google Highway test suite fails when compiled with GCC 12 or later with the -mcpu=power9 option

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110960 --- Comment #8 from Andrew Pinski --- (In reply to Mathieu Malaterre from comment #7) > @rguenth You added `needs-bisection` keyword, but the example is quite > small: 154 lines of code. needs-bisection means to figure out which commit caused

[Bug target/111340] gcc.dg/bitint-12.c fails on x86_64-apple-darwin or fails on x86_64-linux-gnu with -fPIE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111340 --- Comment #3 from Jakub Jelinek --- Seems to be a pre-existing problem. void bar (void) { __asm ("# %0" : : "g" unsigned __int128) 0x123456789abcdef0ULL) << 64) | 0x0fedcba987654321ULL)); } fails the same way. void baz (void) {

PING^4: [PATCH V4, rs6000] Disable generation of scalar modulo instructions

Ping. On 6/30/23 2:26 PM, Pat Haugen via Gcc-patches wrote: Updated from prior version to address latest review comment (simplify umod3). Disable generation of scalar modulo instructions. It was recently discovered that the scalar modulo instructions can suffer noticeable performance issues

Re: [PATCH 3/3] [V2] [RISC-V] support cm.mva01s cm.mvsa01 in zcmp

On 9/7/23 20:06, Fei Gao wrote: On 2023-09-08 04:33  Palmer Dabbelt wrote: On Thu, 07 Sep 2023 13:16:36 PDT (-0700), dimi...@dinux.eu wrote: Hi, This patch appears to have caused PR 111259. Hi Patrick We're reproducing the issue also. One thing that puzzles me is why a zcmp predicate

[Bug target/111340] gcc.dg/bitint-12.c fails on x86_64-apple-darwin

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111340 --- Comment #2 from Francois-Xavier Coudert --- Created attachment 55857 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55857=edit Output of -fdump-rtl-final

[Bug target/111340] gcc.dg/bitint-12.c fails on x86_64-apple-darwin

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

[Bug c/111340] New: gcc.dg/bitint-12.c fails on x86_64-apple-darwin

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111340 Bug ID: 111340 Summary: gcc.dg/bitint-12.c fails on x86_64-apple-darwin Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[PATCH v3] libcpp: add function to check XID properties

From: Raiki Tamura Fixed to include the enum's name which I had forgotten to commit. Thanks This commit adds a new function intended for checking the XID properties of a possibly unicode character, as well as the accompanying enum describing the possible properties. libcpp/ChangeLog:

[PATCH v3] libcpp: add function to check XID properties

From: Raiki Tamura Fixed to include the enum's name which I had forgotten to commit. Thanks This commit adds a new function intended for checking the XID properties of a possibly unicode character, as well as the accompanying enum describing the possible properties. libcpp/ChangeLog:

[Bug c/111337] ICE in gimple-isel.cc for RISC-V port

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111337 Robin Dapp changed: What|Removed |Added CC||rdapp at gcc dot gnu.org --- Comment #1

  1   2   >