[r14-2834 Regression] FAIL: gcc.target/i386/pr87007-5.c scan-assembler-times vxorps[^\n\r]*xmm[0-9] 1 on Linux/x86_64

On Linux/x86_64, b9d7140c80bd3c7355b8291bb46f0895dcd8c3cb is the first bad commit commit b9d7140c80bd3c7355b8291bb46f0895dcd8c3cb Author: Jan Hubicka Date: Fri Jul 28 09:16:09 2023 +0200 loop-split improvements, part 1 caused FAIL: gcc.target/i386/pr87007-4.c scan-assembler-times

[Bug modula2/109952] Inconsistent HIGH values with 'ARRAY OF CHAR'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109952 --- Comment #5 from CVS Commits --- The releases/gcc-13 branch has been updated by Gaius Mulley : https://gcc.gnu.org/g:6ae50730003862aee81ad6c53e4c1a96ed1ee36e commit r13-7640-g6ae50730003862aee81ad6c53e4c1a96ed1ee36e Author: Gaius Mulley

[no subject]

See Sent from my iPhone

[Bug middle-end/110818] Segmentation fault with '-O3 -fno-dce -fno-ipa-cp -fno-tree-dce -fno-tree-sink'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110818 --- Comment #7 from CTC <19373742 at buaa dot edu.cn> --- Reduced testcase: # cat testcase.i struct a { short b; } d, g; int c; static struct a e(short); static struct a f(int *i) { long h[] = {1, 1, 1, 1, 1, 1, 1}; for (; c <= 8; ++c)

[Bug tree-optimization/110819] Missed optimization: when vector's size is 0 but vector::reserve has been called.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110819 --- Comment #2 from AK --- > When compiled with clang, libstdc++'s std::vector uses __builtin_operator_new > which always has the -fassume-sane-operator-new semantics, and so can be > optimized. yes clang optimizes with libstdc++ as well.

[Bug modula2/109908] Delete from m2iso Strings is broken

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109908 --- Comment #5 from CVS Commits --- The releases/gcc-13 branch has been updated by Gaius Mulley : https://gcc.gnu.org/g:9306ef0d5786496a9bbe1850c2e826d5cdf5582e commit r13-7639-g9306ef0d5786496a9bbe1850c2e826d5cdf5582e Author: Gaius Mulley

[Bug tree-optimization/110849] [14 Regression] XPASS in gcc.dg/unroll-7.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110849 Patrick O'Neill changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED

[Bug bootstrap/110684] unknown spec function ‘dumps’ error, C compiler cannot create executables

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110684 --- Comment #17 from AlexK --- to continue I should add line cp -v prev-libcody/libcody.so libccody/ but why there are so many static libs in prev- directories ? my patches didn't cancel all them ...

[Bug modula2/109879] ReadCard and ReadInt from WholeIO have problems with leading space

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109879 --- Comment #5 from CVS Commits --- The releases/gcc-13 branch has been updated by Gaius Mulley : https://gcc.gnu.org/g:461359a8f8361d00f926985050e06bd13445ea69 commit r13-7637-g461359a8f8361d00f926985050e06bd13445ea69 Author: Gaius Mulley

[Bug target/110748] RISC-V: optimize store of DF 0.0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110748 --- Comment #15 from Vineet Gupta --- (In reply to Vineet Gupta from comment #12) > > void znd(double *d) { *d = -0.0; } > > void znf(float *f) { *f = -0.0; } We need 3 set of changes to get const -0.0 working: 1. Allow expand to generate

Re: [PATCH v2] RISC-V: convert the mulh with 0 to mov 0 to the reg.

On 7/28/23 06:31, Robin Dapp via Gcc-patches wrote: This is a draft patch. I would like to explain it's hard to make the simplify generic and ask for some help. There're 2 categories we need to optimize. - The op in optab such as div / 1. - The unspec operation such as mulh * 0,

Re: [PATCH v3 1/4] diagnostics: libcpp: Add LC_GEN linemaps to support in-memory buffers

On Fri, 2023-07-21 at 19:08 -0400, Lewis Hyatt wrote: > Add a new linemap reason LC_GEN which enables encoding the location > of data > that was generated during compilation and does not appear in any > source file. > There could be many use cases, such as, for instance, referring to > the content

gcc-12-20230728 is now available

Snapshot gcc-12-20230728 is now available on https://gcc.gnu.org/pub/gcc/snapshots/12-20230728/ 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 tree-optimization/110849] [14 Regression] XPASS in gcc.dg/unroll-7.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110849 Patrick O'Neill changed: What|Removed |Added CC||jh at suse dot cz --- Comment #1

[Bug c++/110848] Consider enabling -Wvla by default in C++ modes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110848 Martin Uecker changed: What|Removed |Added CC||muecker at gwdg dot de --- Comment #5

Re: [PATCH v3 0/4] diagnostics: libcpp: Overhaul locations for _Pragma tokens

On Fri, 2023-07-21 at 19:08 -0400, Lewis Hyatt wrote: > Hello- > > This is an update to the v2 patch series last sent in January: > https://gcc.gnu.org/pipermail/gcc-patches/2023-January/609473.html > > While I did not receive any feedback on the v2 patches yet, they did > need some > rebasing

[Bug lto/110844] LTO sometimes fail with -save-temp -dumpdir options

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

[Bug tree-optimization/110849] New: [14 Regression] XPASS in gcc.dg/unroll-7.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110849 Bug ID: 110849 Summary: [14 Regression] XPASS in gcc.dg/unroll-7.c Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

Re: [PATCH] RISC-V: Fix uninitialized and redundant use of which_alternative

On 7/28/23 10:42, Patrick O'Neill wrote: No worries! I'm glad it was an easy fix ;) Note there's an effort underway via RISE to have some official RISC-V continuous testing for the compiler tools in place in the very near future (before Sept 1). We're starting with a limited POC, so my

[Bug lto/110844] LTO sometimes fail with -save-temp -dumpdir options

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110844 --- Comment #1 from Andrew Pinski --- Created attachment 55655 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55655=edit strace output Attached is the `strace -f` output of invoking `g++ -flto -save-temps -dumpdir /tmp/ a.o` for the

[Bug modula2/108344] Many tests time out: isatty called in a tight loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108344 --- Comment #7 from CVS Commits --- The releases/gcc-13 branch has been updated by Gaius Mulley : https://gcc.gnu.org/g:35a04220554d62d9bbe068dfa2f52d4d2d572805 commit r13-7636-g35a04220554d62d9bbe068dfa2f52d4d2d572805 Author: Gaius Mulley

[Bug middle-end/110847] [13/14 Regression] Inaccurate GCC documentation about -Wtsan and -Wxor-used-as-pow warnings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110847 Andrew Pinski changed: What|Removed |Added Summary|Inaccurate GCC |[13/14 Regression]

[Bug fortran/110360] ABI issue with character,value dummy argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110360 --- Comment #31 from David Edelsohn --- Yes, &"B"[1], is not shifted because it is a reference. The important different is "B" is passed left-shifted, but 65 is passed right-shifted. call val ("B","B") OK call val

Re: [PATCH] gcc-ar: Handle response files properly [PR77576]

This patch is OK. -- Joseph S. Myers jos...@codesourcery.com

Re: [PATCH 3/5] [RISC-V] Generate Zicond instruction for select pattern with condition eq or neq to 0

On 7/19/23 04:11, Xiao Zeng wrote: + else if (TARGET_ZICOND + && (code == EQ || code == NE) + && GET_MODE_CLASS (mode) == MODE_INT) +{ + need_eq_ne_p = true; + /* 0 + imm */ + if (GET_CODE (cons) == CONST_INT && cons == const0_rtx + &&

[COMMITTED] Remove value_query, push into sub class.

When we first introduced range_query, we provided a base class for constants rather than range queries.  Then inherioted from that and modified the value queries for a range-specific engine. .   At the time, we figured there would be other consumers of the value_query class. When all the dust

[COMMITTED] Add a merge_range to ssa_cache and use it.

This adds some tweaks to the ssa-range cache. 1)   Adds a new merge_range which works like set_range, except if there is already a value, the two values are merged via intersection and stored.   THis avpoids having to check if there is a value, load it, intersect it then store that in the

[COMMITTED] PR tree-optimization/110205 -Fix some warnings

This patch simply fixes the code up a little to remove potential warnings. Bootstrapped on x86_64-pc-linux-gnu with no regressions. Pushed. Andrew From 7905c071c35070fff3397b1e24f140c128c08e64 Mon Sep 17 00:00:00 2001 From: Andrew MacLeod Date: Mon, 10 Jul 2023 13:58:22 -0400 Subject: [PATCH

[Bug other/110205] Some new warnings from clang for the range code

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110205 --- Comment #5 from CVS Commits --- The master branch has been updated by Andrew Macleod : https://gcc.gnu.org/g:7905c071c35070fff3397b1e24f140c128c08e64 commit r14-2859-g7905c071c35070fff3397b1e24f140c128c08e64 Author: Andrew MacLeod Date:

[Bug analyzer/109361] RFE: SARIF output could contain timing/profile information

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109361 --- Comment #4 from David Malcolm --- 1st patch posted for this (adding -fsarif-time-report): https://gcc.gnu.org/pipermail/gcc-patches/2023-April/615109.html 2nd patch: https://gcc.gnu.org/pipermail/gcc-patches/2023-July/625767.html

[Bug c++/110848] Consider enabling -Wvla by default in C++ modes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110848 --- Comment #4 from Andrew Pinski --- Maybe my issue is this has been a documented extension for 20 years now. -pedantic or -std=c++NN has always rejected it like it should. GCC has other extensions which folks could use by accident too (like

Re: [PATCH RESEND] c: add -Wmissing-variable-declarations [PR65213]

On Tue, 18 Jul 2023, Hamza Mahfooz wrote: > Resolves: > PR c/65213 - Extend -Wmissing-declarations to variables [i.e. add > -Wmissing-variable-declarations] > > gcc/c-family/ChangeLog: > > PR c/65213 > * c.opt (-Wmissing-variable-declarations): New option. > > gcc/c/ChangeLog: > >

[Bug c++/110848] Consider enabling -Wvla by default in C++ modes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110848 --- Comment #3 from Aaron Ballman --- (In reply to Andrew Pinski from comment #1) > Since VLA support has been a GNU C++ extension way before it was proposed to > WG21, I doubt we want to enable this by default. I think it boils down to

[PATCH v2] SARIF and -ftime-report's output [PR109361]

On Fri, 2023-07-28 at 08:00 +0200, Richard Biener wrote: > On Fri, Jul 28, 2023 at 12:23 AM David Malcolm via Gcc-patches > wrote: > > > > On Tue, 2023-04-11 at 08:43 +, Richard Biener wrote: > > > On Tue, 4 Apr 2023, David Malcolm wrote: > > > > > > > Richi, Jakub: I can probably

[Bug c++/110848] Consider enabling -Wvla by default in C++ modes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110848 --- Comment #2 from Andrew Pinski --- GCC has documented VLA extensions for C++ support since r0-35216-g4b404517536c85 (PR 930 which was done in 2001). So

[Bug c++/110848] Consider enabling -Wvla by default in C++ modes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110848 Andrew Pinski changed: What|Removed |Added Severity|normal |enhancement Keywords|

[Bug modula2/109830] m2iso library SeqFile.mod - appending to a file overwrites the contents

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109830 --- Comment #5 from CVS Commits --- The releases/gcc-13 branch has been updated by Gaius Mulley : https://gcc.gnu.org/g:55156f50e7c14d63f6c31a65cfdf61c1de33359d commit r13-7634-g55156f50e7c14d63f6c31a65cfdf61c1de33359d Author: Gaius Mulley

[Bug c++/110848] New: Consider enabling -Wvla by default in C++ modes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110848 Bug ID: 110848 Summary: Consider enabling -Wvla by default in C++ modes Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug fortran/110360] ABI issue with character,value dummy argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110360 --- Comment #30 from anlauf at gcc dot gnu.org --- (In reply to David Edelsohn from comment #29) > Maybe something about the way that GFORTRAN is passing the string by value. > 257.optimized shows > > val (&"B"[1]{lb: 1 sz: 1}, "B", 1, 1); >

[COMMITTED] bpf: disable tail call optimization in BPF targets

clang disables tail call optimizations in BPF targets. Do the same in GCC. gcc/ChangeLog: * config/bpf/bpf.cc (bpf_option_override): Disable tail-call optimizations in BPF target. --- gcc/config/bpf/bpf.cc | 3 +++ 1 file changed, 3 insertions(+) diff --git

[Bug fortran/110360] ABI issue with character,value dummy argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110360 --- Comment #29 from David Edelsohn --- I don't know if this is a BE issue or a struct issue. AIX doesn't pass characters in structs normally. Is there any other debugging output from the GFORTRAN other than parse? -fdump-lang-all doesn't

[Bug libstdc++/110807] [13 Regression] Copy list initialisation of a vector raises a warning with -O2

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

[Bug tree-optimization/88443] [meta-bug] bogus/missing -Wstringop-overflow warnings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88443 Bug 88443 depends on bug 110807, which changed state. Bug 110807 Summary: [13 Regression] Copy list initialisation of a vector raises a warning with -O2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110807 What|Removed

[Bug libstdc++/110708] std::format("{:%EEC %OOd}", std::chrono::system_clock::now()) should be rejected

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

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104167 Bug 104167 depends on bug 110719, which changed state. Bug 110719 Summary: Should chrono formatters always use std::time_put for locale's representation? https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110719 What|Removed

[Bug libstdc++/110719] Should chrono formatters always use std::time_put for locale's representation?

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

[Bug fortran/110825] TYPE(*) dummy argument to generate an unused hidden argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110825 --- Comment #5 from CVS Commits --- The master branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:02f4ca0df2d69b922a622e7cc9b396cf686d5a0f commit r14-2856-g02f4ca0df2d69b922a622e7cc9b396cf686d5a0f Author: Harald Anlauf Date:

[Bug fortran/110360] ABI issue with character,value dummy argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110360 --- Comment #28 from anlauf at gcc dot gnu.org --- (In reply to David Edelsohn from comment #27) > If GFORTRAN assumes that a scalar value and a value in a struct are passed > in registers with the same padding, that is not a valid, general

Re: [RFC WIP PATCH] _BitInt bit-field support [PR102989]

On Fri, 28 Jul 2023, Jakub Jelinek via Gcc-patches wrote: > But I ran into a compiler divergence on _Generic with bit-field expressions. > My understanding is that _Generic controlling expression undergoes array > to pointer and function to pointer conversions, but not integral promotions >

Re: _BitInt vs. _Atomic

On Fri, 28 Jul 2023, Jakub Jelinek via Gcc-patches wrote: > The C++ way of dealing with this is using __builtin_clear_padding, > done on atomic stores/updates of the atomic memory (padding is cleared > if any on the value to be stored, or on the expected and desired values). > > I don't know

[Bug modula2/109810] String literal exceeding array causes ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109810 --- Comment #7 from CVS Commits --- The releases/gcc-13 branch has been updated by Gaius Mulley : https://gcc.gnu.org/g:52405b14b7e6a8d13ac53525a341ebfd27ef67cc commit r13-7633-g52405b14b7e6a8d13ac53525a341ebfd27ef67cc Author: Gaius Mulley

Re: [PATCH] Fortran: do not pass hidden character length for TYPE(*) dummy [PR110825]

On Thu, Jul 27, 2023 at 09:39:53PM +0200, Harald Anlauf via Fortran wrote: > Dear all, > > when passing a character actual argument to an assumed-type dummy > (TYPE(*)), we should not pass the character length for that argument, > as otherwise other hidden arguments that are passed as part of the

Re: [PATCH 0/5] GCC _BitInt support [PR102989]

On Fri, 28 Jul 2023, Jakub Jelinek via Gcc-patches wrote: > I had a brief look at libbid and am totally unimpressed. > Seems we don't implement {,unsigned} __int128 <-> _Decimal{32,64,128} > conversions at all (we emit calls to __bid_* functions which don't exist), That's bug 65833. > the

New German PO file for 'gcc' (version 13.2.0)

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, 'gcc-13.2.0.de.po', has

Re: [PATCH] AArch64: Do not increase the vect reduction latency by multiplying count [PR110625]

Sorry for the slow response. Hao Liu OS writes: >> Ah, thanks. In that case, Hao, I think we can avoid the ICE by changing: >> >> if ((kind == scalar_stmt || kind == vector_stmt || kind == vec_to_scalar) >> && vect_is_reduction (stmt_info)) >> >> to: >> >> if ((kind == scalar_stmt ||

[Bug libstdc++/110719] Should chrono formatters always use std::time_put for locale's representation?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110719 --- Comment #6 from CVS Commits --- The releases/gcc-13 branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:24c352c41eb944d29b09f33a42662efad3f6f811 commit r13-7631-g24c352c41eb944d29b09f33a42662efad3f6f811 Author: Jonathan

[Bug libstdc++/110708] std::format("{:%EEC %OOd}", std::chrono::system_clock::now()) should be rejected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110708 --- Comment #4 from CVS Commits --- The releases/gcc-13 branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:74f1c016f44daf18e4bed76b283cd5bfd0b5c8c7 commit r13-7629-g74f1c016f44daf18e4bed76b283cd5bfd0b5c8c7 Author: Jonathan

[Bug libstdc++/110719] Should chrono formatters always use std::time_put for locale's representation?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110719 --- Comment #5 from CVS Commits --- The releases/gcc-13 branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:cb01a31ab2779b0252c4945924ba2163d9150642 commit r13-7630-gcb01a31ab2779b0252c4945924ba2163d9150642 Author: Jonathan

[Bug libstdc++/110593] The std::ratio meta arithmetic can accept non-std::ratio

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110593 --- Comment #3 from CVS Commits --- The releases/gcc-13 branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:13dd1501a1adc5d76c13ae36368bff3c3b64da37 commit r13-7627-g13dd1501a1adc5d76c13ae36368bff3c3b64da37 Author: Jonathan

[Bug libstdc++/110807] [13 Regression] Copy list initialisation of a vector raises a warning with -O2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110807 --- Comment #9 from CVS Commits --- The releases/gcc-13 branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:962cd3e2c475e8197fd0cfa7330a8f352b4ff5b2 commit r13-7625-g962cd3e2c475e8197fd0cfa7330a8f352b4ff5b2 Author: Jonathan

[Bug c++/84542] missing -Wdeprecated-declarations on a redeclared function template

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84542 --- Comment #6 from CVS Commits --- The releases/gcc-13 branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:3f78294969641cb762dc2abcd832c7d3edeefa79 commit r13-7624-g3f78294969641cb762dc2abcd832c7d3edeefa79 Author: Jonathan

[Bug other/110847] New: Inaccurate GCC documentation about -Wtsan and -Wxor-used-as-pow warnings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110847 Bug ID: 110847 Summary: Inaccurate GCC documentation about -Wtsan and -Wxor-used-as-pow warnings Product: gcc Version: unknown URL:

[Bug target/110625] [AArch64] Vect: SLP fails to vectorize a loop as the reduction_latency calculated by new costs is too large

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110625 --- Comment #10 from rsandifo at gcc dot gnu.org --- Created attachment 55654 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55654=edit Candidate patch (part 2) Sorry for the delay. I'm testing the attached two patches to fix the

[Bug c++/110846] Noinline attribute on a destructor only honored when on the member function declaration, does not wok on definition

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

[Bug modula2/109779] isolib SkipLine skips the first character of the successive line

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109779 --- Comment #5 from CVS Commits --- The releases/gcc-13 branch has been updated by Gaius Mulley : https://gcc.gnu.org/g:41e3fd01c204563fc892cd2e7606d01f6467c3e5 commit r13-7623-g41e3fd01c204563fc892cd2e7606d01f6467c3e5 Author: Gaius Mulley

[Bug target/110625] [AArch64] Vect: SLP fails to vectorize a loop as the reduction_latency calculated by new costs is too large

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110625 --- Comment #9 from rsandifo at gcc dot gnu.org --- Created attachment 55653 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55653=edit Candidate patch (part 1)

[Bug c++/110846] New: Noinline attribute on a destructor only honored when on the member function declaration, does not wok on definition

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110846 Bug ID: 110846 Summary: Noinline attribute on a destructor only honored when on the member function declaration, does not wok on definition Product: gcc

[Bug bootstrap/110684] unknown spec function ‘dumps’ error, C compiler cannot create executables

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110684 --- Comment #16 from AlexK --- I have copied already compileed shared libs into new directories: cp -v prev-libcpp/libcpp.so libcpp/ cp -v prev-libbacktrace/libbacktrace.so libbacktrace/ cp -v prev-libdecnumber/libdecnumber.so libdecnumber/

Re: [PATCH] RISC-V: Fix uninitialized and redundant use of which_alternative

No worries! I'm glad it was an easy fix ;) On 7/27/23 19:55, Demin Han wrote: Sorry for not consider rv32 config. The fix is OK. If convenient, please commit it. On 2023/7/28 4:46, Patrick O'Neill wrote: The newly added testcase fails on rv32 targets with this message: FAIL:

Re: [PATCH] RISC-V: Fix uninitialized and redundant use of which_alternative

Thanks! Here's the comitted patch: https://inbox.sourceware.org/gcc-patches/20230728163758.377962-1-patr...@rivosinc.com/T/#u On 7/27/23 15:11, juzhe.zhong wrote: LGTM.Thanks. You can go ahead commit it. Replied Message FromPatrick O'Neill Date

[Committed] RISC-V: Specify -mabi in rv64 autovec testcase

On rv32 targets, this patch fixes: FAIL: gcc.target/riscv/rvv/autovec/madd-split2-1.c -O3 -ftree-vectorize (test for excess errors) cc1: error: ABI requires '-march=rv32' gcc/testsuite/ChangeLog: * gcc.target/riscv/rvv/autovec/madd-split2-1.c: Add -mabi=lp64d to dg-options.

[RFC WIP PATCH] _BitInt bit-field support [PR102989]

On Fri, Jul 28, 2023 at 11:05:42AM +0200, Jakub Jelinek via Gcc-patches wrote: > On Thu, Jul 27, 2023 at 06:41:44PM +, Joseph Myers wrote: > > On Thu, 27 Jul 2023, Jakub Jelinek via Gcc-patches wrote: > > > > > - _BitInt(N) bit-fields aren't supported yet (the patch rejects them); > > > I'd

Re: _BitInt vs. _Atomic

Am Freitag, dem 28.07.2023 um 17:10 +0200 schrieb Jakub Jelinek: > On Fri, Jul 28, 2023 at 04:53:30PM +0200, Martin Uecker wrote: > > > The thing is that user doesn't have much control over those > > > padding bits, so whether _Atomic operations on long double (when it is 80 > > > bit and stores

Re: [PATCH v2] RISC-V: testsuite: Add vector_hw and zvfh_hw checks.

On 7/27/23 06:02, Robin Dapp wrote: LGTM, I just found this patch still on the list, I mostly tested with qemu, so I don't think that is a problem before, but I realize it's a problem when we run on a real board that does not support those extensions. I think we can skip this one as I

[Bug fortran/110360] ABI issue with character,value dummy argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110360 --- Comment #27 from David Edelsohn --- GFORTRAN parse output describes the characters as follow symtree: 'char'|| symbol: 'char' type spec : (UNKNOWN 0) attributes: (PROCEDURE INTRINSIC-PROC FUNCTION

[Bug middle-end/110832] [14 Regression] 14% capacita -O2 regression between g:9fdbd7d6fa5e0a76 (2023-07-26 01:45) and g:ca912a39cccdd990 (2023-07-27 03:44) on zen3 and core

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110832 --- Comment #8 from Uroš Bizjak --- (In reply to Richard Biener from comment #6) > Do we know whether we could in theory improve the sanitizing by optimization > without -funsafe-math-optimizations (I think -fno-trapping-math, >

Re: [PATCH] c++: devirtualization of array destruction [PR110057]

On 7/26/23 20:06, Ng YongXiang wrote: Hi Jason, I've made the following changes. 1. Add pr83054-2.C 2. Move the devirt tests to tree-ssa. 3. Remove dg do run for devirt tests 4. Add // PR c++/110057 5. Generate commit message with git gcc-commit-mklog 6. Check commit format with git gcc-verify

[Bug ipa/110057] Missed devirtualization opportunities

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110057 --- Comment #10 from CVS Commits --- The trunk branch has been updated by Jason Merrill : https://gcc.gnu.org/g:a47e615fbf9c6f4b24e5032df5d720b6bf9b63b5 commit r14-2853-ga47e615fbf9c6f4b24e5032df5d720b6bf9b63b5 Author: Ng YongXiang Date:

[Bug ipa/83054] [8 Regression] ICE in operator>, at profile-count.h:823

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83054 --- Comment #5 from CVS Commits --- The trunk branch has been updated by Jason Merrill : https://gcc.gnu.org/g:a47e615fbf9c6f4b24e5032df5d720b6bf9b63b5 commit r14-2853-ga47e615fbf9c6f4b24e5032df5d720b6bf9b63b5 Author: Ng YongXiang Date: Thu

[Bug c++/110845] Function call when it should inline?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110845 --- Comment #2 from KL --- Changed main to foo: same behavior

[Bug c++/110845] Function call when it should inline?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110845 --- Comment #1 from Andrew Pinski --- Gcc has an heuristic for main where gcc knows that main is called only once and does not inline as much into a function that will ever be called exactly once. My bet if you Rename main to foo, gcc will

[Bug modula2/110002] Using -fcpp only invokes cc1 from pre-configured path $(libexec)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110002 Gaius Mulley changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0

Re: _BitInt vs. _Atomic

On Fri, Jul 28, 2023 at 04:53:30PM +0200, Martin Uecker wrote: > > The thing is that user doesn't have much control over those > > padding bits, so whether _Atomic operations on long double (when it is 80 > > bit and stores from hw actually store 10 bytes rather than 12 or 16), or > > _BitInt(37)

Re: [PATCH 3/5] [RISC-V] Generate Zicond instruction for select pattern with condition eq or neq to 0

On 7/25/23 11:55, Andreas Schwab wrote: On Jul 19 2023, Xiao Zeng wrote: diff --git a/gcc/config/riscv/riscv.cc b/gcc/config/riscv/riscv.cc index 38d8eb2fcf5..7e6b24bd232 100644 --- a/gcc/config/riscv/riscv.cc +++ b/gcc/config/riscv/riscv.cc @@ -2448,6 +2448,17 @@ riscv_rtx_costs (rtx x,

Re: [PATCH 0/5] Recognize Zicond extension

On 7/28/23 00:34, Xiao Zeng wrote: Does that work for you? I'm going to look at 3/5 today pretty closely.  Exposing zicond to movcc is something we had implemented inside Ventana and I want to compare/contrast your work with ours. What a coincidence! Zicond is a direct descendant of

[PATCH] rs6000: Fix __builtin_altivec_vcmpne{b,h,w} implementation

GCC maintainers: The following patch cleans up the definition for the __builtin_altivec_vcmpnet. The current implementation implies that the built-in is only supported on Power 9 since it is defined under the Power 9 stanza. However the built-in has no ISA restrictions as stated in the Power

Re: _BitInt vs. _Atomic

Am Freitag, dem 28.07.2023 um 16:26 +0200 schrieb Jakub Jelinek: > On Fri, Jul 28, 2023 at 04:03:39PM +0200, Martin Uecker wrote: > > > On Thu, Jul 27, 2023 at 07:06:03PM +, Joseph Myers wrote: > > > > I think there should be tests for _Atomic _BitInt types. Hopefully > > > > atomic > > > >

[Bug target/110795] Bad code gen for vector compare booleans

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110795 --- Comment #5 from Steven Munroe --- Thanks, sorry I missed the obvious.

[Bug c++/110845] New: Function call when it should inline?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110845 Bug ID: 110845 Summary: Function call when it should inline? Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

Re: _BitInt vs. _Atomic

On Fri, Jul 28, 2023 at 04:03:39PM +0200, Martin Uecker wrote: > > On Thu, Jul 27, 2023 at 07:06:03PM +, Joseph Myers wrote: > > > I think there should be tests for _Atomic _BitInt types. Hopefully > > > atomic > > > compound assignment just works via the logic for compare-and-exchange > >

[Bug tree-optimization/77689] Missing vectorization lead to huge performance loss

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77689 --- Comment #18 from CVS Commits --- The master branch has been updated by Jan Hubicka : https://gcc.gnu.org/g:f5fb9ff2396fd41fdd2e6d35a412e936d2d42f75 commit r14-2852-gf5fb9ff2396fd41fdd2e6d35a412e936d2d42f75 Author: Jan Hubicka Date: Fri

[Bug modula2/110246] Using variables of type CHAR or BYTE as array index does not work

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110246 Gaius Mulley changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug modula2/110246] Using variables of type CHAR or BYTE as array index does not work

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

[Bug modula2/109729] gm2 (14.0.0) does not like a CHAR type FOR loop control variable any more

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109729 --- Comment #5 from CVS Commits --- The releases/gcc-13 branch has been updated by Gaius Mulley : https://gcc.gnu.org/g:3e9aaa9bcb2fc64e64f4e8a2aa0f6f7395a21c52 commit r13-7622-g3e9aaa9bcb2fc64e64f4e8a2aa0f6f7395a21c52 Author: Gaius Mulley

[Bug modula2/110246] Using variables of type CHAR or BYTE as array index does not work

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110246 --- Comment #2 from CVS Commits --- The releases/gcc-13 branch has been updated by Gaius Mulley : https://gcc.gnu.org/g:3e9aaa9bcb2fc64e64f4e8a2aa0f6f7395a21c52 commit r13-7622-g3e9aaa9bcb2fc64e64f4e8a2aa0f6f7395a21c52 Author: Gaius Mulley

Re: _BitInt vs. _Atomic

Am Freitag, dem 28.07.2023 um 16:03 +0200 schrieb Martin Uecker: > > > On Thu, Jul 27, 2023 at 07:06:03PM +, Joseph Myers wrote: > > > I think there should be tests for _Atomic _BitInt types. Hopefully > > > atomic > > > compound assignment just works via the logic for compare-and-exchange

Re: _BitInt vs. _Atomic

> On Thu, Jul 27, 2023 at 07:06:03PM +, Joseph Myers wrote: > > I think there should be tests for _Atomic _BitInt types. Hopefully atomic > > compound assignment just works via the logic for compare-and-exchange > > loops, but does e.g. atomic_fetch_add work with _Atomic _BitInt types? >

[Bug middle-end/110832] [14 Regression] 14% capacita -O2 regression between g:9fdbd7d6fa5e0a76 (2023-07-26 01:45) and g:ca912a39cccdd990 (2023-07-27 03:44) on zen3 and core

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110832 --- Comment #7 from Uroš Bizjak --- (In reply to Richard Biener from comment #6) > Do we know whether we could in theory improve the sanitizing by optimization > without -funsafe-math-optimizations (I think -fno-trapping-math, >

[Bug middle-end/110832] [14 Regression] 14% capacita -O2 regression between g:9fdbd7d6fa5e0a76 (2023-07-26 01:45) and g:ca912a39cccdd990 (2023-07-27 03:44) on zen3 and core

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110832 --- Comment #6 from Richard Biener --- Do we know whether we could in theory improve the sanitizing by optimization without -funsafe-math-optimizations (I think -fno-trapping-math, -ffinite-math-only -fno-signalling-nans should be a better

Re: Loop-split improvements, part 3

> On Fri, Jul 28, 2023 at 2:57 PM Jan Hubicka via Gcc-patches > wrote: > > > > Hi, > > This patch extends tree-ssa-loop-split to understand test of the form > > if (i==0) > > and > > if (i!=0) > > which triggers only during the first iteration. Naturally we should > > also be able to trigger

  1   2   3   >