[Bug lto/109428] GCC did not fix CVE-2022-37434, a heap overflow bug introduced by its dependency zlib code.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109428 --- Comment #5 from chluo at cse dot cuhk.edu.hk --- OK, also thanks for the kind explanations!

[Bug lto/109428] GCC did not fix CVE-2022-37434, a heap overflow bug introduced by its dependency zlib code.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109428 --- Comment #4 from Andrew Pinski --- (In reply to chluo from comment #2) > Thank you for your quick update! The commit might just list one approach to > exploit the bug in **inflate()** function. I am not sure if there are other > ways to

[Bug c/85696] OpenMP with variably modified and default(none) won't compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85696 zhonghao at pku dot org.cn changed: What|Removed |Added CC||zhonghao at pku dot org.cn

[Bug other/105404] new version of zlib

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105404 --- Comment #11 from Andrew Pinski --- *** Bug 109428 has been marked as a duplicate of this bug. ***

[Bug lto/109428] GCC did not fix CVE-2022-37434, a heap overflow bug introduced by its dependency zlib code.

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

[Bug lto/109428] GCC did not fix CVE-2022-37434, a heap overflow bug introduced by its dependency zlib code.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109428 chluo at cse dot cuhk.edu.hk changed: What|Removed |Added Resolution|DUPLICATE |---

[PATCHv3, rs6000] rs6000: correct vector sign extend built-ins on Big Endian [PR108812]

Hi, This patch removes byte reverse operation before vector integer sign extension on big endian. These built-ins require to sign extend the element of the input vector that would fall in the least significant portion of the result element. So both BE and LE should do the same operation and the

Re: [PATCH] [testsuite] [ppc] expect vectorization in gen-vect-11c.c

Hello, Kewen, On Mar 27, 2023, "Kewen.Lin" wrote: > on 2023/3/25 16:35, Alexandre Oliva wrote: >> The first loop in main gets stores "vectorized" on powerpc into >> full-word stores, even without any vector instruction support, so the >> test's expectation of no loop vectorization is not met.

[Bug other/105404] new version of zlib

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105404 --- Comment #10 from Andrew Pinski --- Note GCC does not call inflateGetHeader so it is not affected by CVE-2022-37434.

RE: [PATCH] Check hard_regno_mode_ok before setting lowest memory move cost for the mode with different reg classes.

> -Original Message- > From: Vladimir Makarov > Sent: Wednesday, April 5, 2023 8:59 PM > To: Jeff Law ; Liu, Hongtao > ; gcc-patches@gcc.gnu.org > Subject: Re: [PATCH] Check hard_regno_mode_ok before setting lowest > memory move cost for the mode with different reg classes. > > > On

[Bug lto/109428] GCC did not fix CVE-2022-37434, a heap overflow bug introduced by its dependency zlib code.

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

[Bug other/105404] new version of zlib

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105404 Andrew Pinski changed: What|Removed |Added CC||chluo at cse dot cuhk.edu.hk ---

[Bug c/109426] Gcc runs into Infinite loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109426 Xi Ruoyao changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[Bug lto/109428] New: GCC did not fix CVE-2022-37434, a heap overflow bug introduced by its dependency zlib code.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109428 Bug ID: 109428 Summary: GCC did not fix CVE-2022-37434, a heap overflow bug introduced by its dependency zlib code. Product: gcc Version: 13.0 Status: UNCONFIRMED

Re: [PATCH] [PR99708] [rs6000] don't expect __ibm128 with 64-bit long double

Hello, Kewen, Thanks for the feedback. On Mar 27, 2023, "Kewen.Lin" wrote: > on 2023/3/25 16:37, Alexandre Oliva via Gcc-patches wrote: >> >> When long double is 64-bit wide, as on vxworks, the rs6000 backend >> defines neither the __ibm128 type nor the __SIZEOF_IBM128__ macro, but >>

[Bug tree-optimization/109427] param=vect-induction-float= has a typo for IntegerRange

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

[Bug tree-optimization/109427] param=vect-induction-float= has a typo for IntegerRange

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109427 --- Comment #3 from CVS Commits --- The releases/gcc-12 branch has been updated by Andrew Pinski : https://gcc.gnu.org/g:6c5d6ed689d24418a3bc0647ab34a7ab017d7030 commit r12-9388-g6c5d6ed689d24418a3bc0647ab34a7ab017d7030 Author: Andrew Pinski

[PATCH] Fix typo in -param=vect-induction-float= attributes

There was a typo in the attributes of the option -param=vect-induction-float= for IntegerRange. This fixes that typo. Committed to GCC 12 branch as obvious after a build/test. gcc/ChangeLog: PR tree-optimization/109427 * params.opt (-param=vect-induction-float=): Fix

[Bug tree-optimization/109427] param=vect-induction-float= has a typo for IntegerRange

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109427 --- Comment #2 from CVS Commits --- The trunk branch has been updated by Andrew Pinski : https://gcc.gnu.org/g:0f816116356fec32e3a3a2fb5af790a0438c5da4 commit r13-7022-g0f816116356fec32e3a3a2fb5af790a0438c5da4 Author: Andrew Pinski Date:

[PATCH] Fix typo in -param=vect-induction-float= attributes

There was a typo in the attributes of the option -param=vect-induction-float= for IntegerRange. This fixes that typo. Committed as obvious after a build/test. gcc/ChangeLog: PR tree-optimization/109427 * params.opt (-param=vect-induction-float=): Fix option attribute

[Bug tree-optimization/109427] param=vect-induction-float= has a typo for IntegerRange

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

[Bug fortran/109358] Wrong formatting with T-descriptor during stream output

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

[Bug tree-optimization/109427] New: Wrong param description in param.opt

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109427 Bug ID: 109427 Summary: Wrong param description in param.opt Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component:

Re: Re: [PATCH v2] RISC-V: Add Z*inx imcompatible check in gcc.

-原始邮件- 发件人: "Jeff Law" 发送时间: 2023-04-05 09:30:43 (星期三) 收件人: "Hans-Peter Nilsson" , Jiawei 抄送: gcc-patches@gcc.gnu.org, kito.ch...@sifive.com, pal...@dabbelt.com, christoph.muell...@vrull.eu, wuwei2...@iscas.ac.cn 主题: Re: [PATCH v2] RISC-V: Add Z*inx imcompatible check in gcc.

[Bug target/109384] [13 Regression] unquoted keyword 'float' in format [-Werror=format-diag]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109384 --- Comment #8 from jiawei --- Thank you for this fix, I neglected to confirm the format, sorry for that.

[Bug fortran/109358] Wrong formatting with T-descriptor during stream output

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

[Bug testsuite/108899] [13 Regression] ERROR: can't rename to "saved-unsupported": command already exists on i386

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108899 --- Comment #10 from CVS Commits --- The master branch has been updated by Alexandre Oliva : https://gcc.gnu.org/g:673a2a6445a79bcce5ba433d6bbec4b99a1bc7c6 commit r13-7021-g673a2a6445a79bcce5ba433d6bbec4b99a1bc7c6 Author: Alexandre Oliva

Re: 'g++.dg/modules/modules.exp': don't leak local 'unsupported' proc [PR108899]

On Apr 5, 2023, Thomas Schwinge wrote: > Given the two "OK"s that you got end of last week, are you going to push > that anytime soon, please? Apologies for the delay. > With... > Co-authored-by: Thomas Schwinge > ... added, I suppose. I wrote the patch based on your report, before

Re: [PATCH 0/2] Support Intel AMX-COMPLEX

On Mon, Apr 3, 2023 at 4:51 PM Haochen Jiang via Gcc-patches wrote: > > Hi all, > > These patch aims to add Intel AMX-COMPLEX instructions. Also we added > AMX-COMPLEX to -march=graniterapids. > > The information is based on newly released > Intel Architecture Instruction Set Extensions and

[GSoC] gcc-rs - Unicode Support or Metadata

Dear GCC members, I understand that I am late in submitting this proposal. However, I found out about gcc-rust and Google of Code three hours ago, and instead of doing nothing, I decided that it is in my best interest to apply nonetheless. I'm interested in Rust and the GCC frontend for many

[GSoC] gcc-rs - Unicode Support or Metadata

Dear GCC members, I understand that I am late in submitting this proposal. However, I found out about gcc-rust and Google of Code three hours ago, and instead of doing nothing, I decided that it is in my best interest to apply nonetheless. I'm interested in Rust and the GCC frontend for many

Re: [PATCH] Introduce -nolibstdc++ option

On Mar 30, 2023, Gerald Pfeifer wrote: > On Thu, 30 Mar 2023, Alexandre Oliva wrote: >> How about this, does this seem useful? > I like it - helpful and easy to understand. :-) 'k, I'm putting it in, thanks On Mar 30, 2023, Arsen Arsenović wrote: > IMO, yes - in fact, the libstdc++ manual

[Bug c/109426] Gcc runs into Infinite loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109426 Andrew Pinski changed: What|Removed |Added Component|c++ |c --- Comment #2 from Andrew Pinski

[Bug c++/109426] Gcc runs into Infinite loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109426 Andrew Pinski changed: What|Removed |Added Summary|Gcc runs into Infinite |Gcc runs into Infinite loop

[Bug c++/109426] New: Gcc runs into Infinite loop, when resolving templates

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109426 Bug ID: 109426 Summary: Gcc runs into Infinite loop, when resolving templates Product: gcc Version: 12.2.1 Status: UNCONFIRMED Severity: normal Priority: P3

Re: -Wanalyzer-use-of-uninitialized-value always shadows -Wanalyzer-out-of-bounds

On Wed, 2023-04-05 at 19:50 +0200, Benjamin Priour wrote: > Hi David, > > I used the below code snippet to experiment with out-of-bounds (OOB) > on > trunk. Three things occurred that I believe could see some > improvement. See > https://godbolt.org/z/57n459cEs for the warnings. > > int

[Bug c++/109425] mismatched argument pack lengths while expanding

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109425 --- Comment #2 from Hannes Hauswedell --- Thanks for the quick reply, and nice that it is already fixed for 13! I assume this will not be backported? It wouldn't be a huge problem, because it is possible to workaround with non-friend

[Bug target/70243] PowerPC V4SFmode should not use Altivec instructions on VSX systems

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70243 --- Comment #5 from Michael Meissner --- Created attachment 54814 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54814=edit Test case This is test case that shows the generation of fmaddfp and fnmsubfp.

[Bug target/109399] RISC-V: RVV VSETVL PASS backward demand fusiton bug

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

[Bug target/70243] PowerPC V4SFmode should not use Altivec instructions on VSX systems

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70243 --- Comment #4 from Chip Kerchner --- It shows up as a rounding difference on BE machines.

[Bug target/70243] PowerPC V4SFmode should not use Altivec instructions on VSX systems

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70243 Chip Kerchner changed: What|Removed |Added CC||chip.kerchner at ibm dot com ---

[Bug modula2/109423] cc1gm2 ICE if an INCL or EXCL is performced on an unknown set

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

[Bug modula2/109423] cc1gm2 ICE if an INCL or EXCL is performced on an unknown set

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

[Bug modula2/109423] cc1gm2 ICE if an INCL or EXCL is performced on an unknown set

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109423 --- Comment #1 from CVS Commits --- The master branch has been updated by Gaius Mulley : https://gcc.gnu.org/g:1bd13193fab77a19da323974aec876f0fc1817ee commit r13-7019-g1bd13193fab77a19da323974aec876f0fc1817ee Author: Gaius Mulley Date:

Re: [PATCH] PR tree-optimization/109417 - Check if dependency is valid before using in may_recompute_p.

On 4/5/23 14:10, Andrew MacLeod via Gcc-patches wrote: When a statement is first processed, any SSA_NAMEs that are dependencies are cached for quick future access. if we ;later rewrite the statement (say propagate a constant into it), its possible the ssa-name in this cache is no longer

Ping^7: [PATCH] jit: Install jit headers in $(libsubincludedir) [PR 101491]

Hello, Ping https://gcc.gnu.org/pipermail/gcc-patches/2022-November/606450.html Thanks, Lorenzo Salvadore > From f8e2c2ee89a7d8741bb65163d1f1c20edcd546ac Mon Sep 17 00:00:00 2001 > From: Lorenzo Salvadore develo...@lorenzosalvadore.it > > Date: Wed, 16 Nov 2022 11:27:38 +0100 > Subject:

[PATCH v2 8/8] RISCV: Weaken mem_thread_fence

This change brings atomic fences in line with table A.6 of the ISA manual. Relax mem_thread_fence according to the memmodel given. 2023-04-05 Patrick O'Neill * riscv.cc: Expose helper functions to sync.md. * riscv-protos.h: Likewise. * sync.md (mem_thread_fence_1):

[PATCH v2 7/8] RISCV: Weaken atomic stores

This change brings atomic stores in line with table A.6 of the ISA manual. 2023-04-05 Patrick O'Neill PR target/89835 * sync.md (atomic_store): Use simple store instruction in combination with a fence. * pr89835.c: New test. Signed-off-by: Patrick

[PATCH v2 3/8] RISCV: Enforce atomic compare_exchange SEQ_CST

This patch enforces SEQ_CST for atomic compare_exchange ops. Replace Fence/LR.aq/SC.aq pairs with strong SEQ_CST LR.aqrl/SC.rl pairs recommended by table A.6 of the ISA manual. 2023-04-05 Patrick O'Neill * sync.md: Change FENCE/LR.aq/SC.aq into sequentially consistent

[PATCH v2 2/8] RISCV: Enforce Libatomic LR/SC SEQ_CST

Replace LR.aq/SC.rl pairs with the SEQ_CST LR.aqrl/SC.rl pairs recommended by table A.6 of the ISA manual. 2023-04-05 Patrick O'Neill * atomic.c: Change LR.aq/SC.rl pairs into sequentially consistent LR.aqrl/SC.rl pair. Signed-off-by: Patrick O'Neill ---

[PATCH v2 6/8] RISCV: Weaken compare_exchange LR/SC pairs

Introduce the %I and %J flags for setting the .aqrl bits on LR/SC pairs as needed. Atomic compare and exchange ops provide success and failure memory models. C++17 and later place no restrictions on the relative strength of each model, so ensure we cover both by using a model that enforces the

[PATCH v2 5/8] RISCV: Eliminate AMO op fences

Atomic operations with the appropriate bits set already enfore release semantics. Remove unnecessary release fences from atomic ops. This change brings AMO ops in line with table A.6 of the ISA manual. 2023-04-05 Patrick O'Neill * riscv.cc (riscv_memmodel_needs_amo_acquire): Change

[PATCH v2 4/8] RISCV: Add AMO release bits

This patch sets the relevant .rl bits on amo operations. 2023-04-05 Patrick O'Neill * riscv.cc (riscv_print_operand): change behavior of %A to include release bits. Signed-off-by: Patrick O'Neill --- gcc/config/riscv/riscv.cc | 7 ++- 1 file changed, 6 insertions(+), 1

[PATCH v2 1/8] RISCV: Eliminate SYNC memory models

Remove references to MEMMODEL_SYNC_* models by converting via memmodel_base(). 2023-04-05 Patrick O'Neill * atomic.c: Remove MEMMODEL_SYNC_* cases and sanitize memmodel input with memmodel_base Signed-off-by: Patrick O'Neill --- gcc/config/riscv/riscv.cc | 11 +++ 1

[PATCH v2 0/8] RISCV: Implement ISA Manual Table A.6 Mappings

This patchset aims to bring the RISCV atomics implementation in line with the recommended mapping present in table A.6 of the ISA manual. https://github.com/riscv/riscv-isa-manual/blob/c7cf84547b3aefacab5463add1734c1602b67a49/src/memory.tex#L1083-L1157 The current mapping in GCC is not

Re: [Patch, fortran] PR104272 - finalizer gets called during allocate

Hi Harald, Quite right - good spot. There was an 'else' that turned out to be unnecessary. Thanks Paul On Wed, 5 Apr 2023 at 19:50, Harald Anlauf wrote: > Hi Paul, > > On 4/5/23 08:53, Paul Richard Thomas via Gcc-patches wrote: > > Hi All, > > > > This is a first in my recent experience - a

Re: [PATCH] c++: satisfaction and ARGUMENT_PACK_SELECT [PR105644]

On Mon, 3 Apr 2023, Jason Merrill wrote: > On 4/3/23 10:49, Patrick Palka wrote: > > This testcase demonstrates we can legitimately enter satisfaction with > > an ARGUMENT_PACK_SELECT argument, which is problematic because we can't > > store such arguments in the satisfaction cache (or any other

[Bug fortran/104312] ICE with -ff2c in fold_convert_loc, at fold-const.cc:2451

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

[Bug c++/107853] [10/11/12 Regression] variadic template with a variadic template friend with a requires of fold expression

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107853 Marek Polacek changed: What|Removed |Added CC||h2+bugs at fsfe dot org --- Comment #8

[Bug c++/109425] mismatched argument pack lengths while expanding

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109425 Marek Polacek changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[PATCH] PR tree-optimization/109417 - Check if dependency is valid before using in may_recompute_p.

When a statement is first processed, any SSA_NAMEs that are dependencies are cached for quick future access. if we ;later rewrite the statement (say propagate a constant into it), its possible the ssa-name in this cache is no longer active.   Normally this is not a problem, but the changed to

[Bug tree-optimization/109417] [13 Regression] ICE on valid code at -O3 on x86_64-linux-gnu: Segmentation fault since r13-6945

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109417 --- Comment #2 from Andrew Macleod --- (In reply to Jakub Jelinek from comment #1) > Started with r13-6945-g429a7a88438cc80e I've run into this before. _54 = _22 is processed, and we cache _22 as a dependency fo _54. then we do some

[Bug c++/109425] New: mismatched argument pack lengths while expanding

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109425 Bug ID: 109425 Summary: mismatched argument pack lengths while expanding Product: gcc Version: 12.2.1 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug tree-optimization/109424] ~((x > y) ? x : y) produces two not instructions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109424 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug tree-optimization/109424] ~((x > y) ? x : y) produces two not instructions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109424 Andrew Pinski changed: What|Removed |Added Summary|~ |~((x > y) ? x : y) produces

[Bug tree-optimization/109424] New: ~

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109424 Bug ID: 109424 Summary: ~ Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: enhancement Priority: P3 Component:

[Bug tree-optimization/101024] Missed min expression at phiopt1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101024 --- Comment #6 from Andrew Pinski --- Part of this is in the patch set in bug 25290 comment # 27 patch set. Mostly the "c ? min/max : min/max" part, I still need to implement the "c ? min : d" part.

[Bug tree-optimization/25290] PHI-OPT could be rewritten so that is uses match

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25290 Andrew Pinski changed: What|Removed |Added Attachment #40185|0 |1 is obsolete|

[Bug target/103100] [11/12/13 Regression] unaligned access generated with memset or {} and -O2 -mstrict-align

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103100 Andrew Pinski changed: What|Removed |Added URL|https://gcc.gnu.org/piperma |

Re: [RFA][Bug target/108892 ][13 regression] Force re-recognition after changing RTL structure of an insn

Hi again, On Wed, Apr 05, 2023 at 11:43:30AM -0600, Jeff Law wrote: > On 4/5/23 11:38, Segher Boessenkool wrote: > >Right. But it seems to me it has been there all those years? Does the > >new testcase fail on older branches? Even if not, it seems clear it is > >wrong on the older branches as

Re: [Patch, fortran] PR104272 - finalizer gets called during allocate

On 4/5/23 20:50, Harald Anlauf via Gcc-patches wrote: can you have a look again at the logic in the hunk touching trans-stmt.cc (gfc_trans_allocate)?  I haven't checked in detail, but it seems possible that you get a stale tmp in the gfc_prepend_expr_to_block if

Re: [Patch, fortran] PR104272 - finalizer gets called during allocate

Hi Paul, On 4/5/23 08:53, Paul Richard Thomas via Gcc-patches wrote: Hi All, This is a first in my recent experience - a very old bug that produces too many finalizations! It results from a bit of a fix up, where class objects are allocated using the derived typespec, rather than a source or

[Bug target/108947] [13 Regression] wrong code with -O2 -fno-forward-propagate and vector compare on riscv64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108947 Sam James changed: What|Removed |Added CC||sjames at gcc dot gnu.org --- Comment #3

[Bug libstdc++/88508] std::bad_cast in std::basic_ostringstream.oss.fill()

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88508 Frank Heckenbach changed: What|Removed |Added CC||f.heckenb...@fh-soft.de --- Comment

[RFC PATCH] driver: unfilter default library path [PR 104707]

Currently, gcc delibrately filters out default library paths "/lib/" and "/usr/lib/", causing some linkers like mold fails to find libraries. This behavior was introduced at least 31 years ago in the initial revision of the git repo, personally I think it's obsolete because: 1. The less than 20

[Bug modula2/109423] New: cc1gm2 ICE if an INCL or EXCL is performced on an unknown set

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109423 Bug ID: 109423 Summary: cc1gm2 ICE if an INCL or EXCL is performced on an unknown set Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[Bug tree-optimization/109417] [13 Regression] ICE on valid code at -O3 on x86_64-linux-gnu: Segmentation fault since r13-6945

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109417 Jakub Jelinek changed: What|Removed |Added Target Milestone|--- |13.0 Priority|P3

-Wanalyzer-use-of-uninitialized-value always shadows -Wanalyzer-out-of-bounds

Hi David, I used the below code snippet to experiment with out-of-bounds (OOB) on trunk. Three things occurred that I believe could see some improvement. See https://godbolt.org/z/57n459cEs for the warnings. int consecutive_oob_in_frame () { int arr[] = {1,2,3,4,5,6,7}; int y1 = arr[9];

Re: [RFA][Bug target/108892 ][13 regression] Force re-recognition after changing RTL structure of an insn

On 4/5/23 11:38, Segher Boessenkool wrote: On Wed, Apr 05, 2023 at 09:07:30AM -0600, Jeff Law wrote: On 4/5/23 08:21, Segher Boessenkool wrote: On Wed, Mar 29, 2023 at 07:48:00AM -0600, Jeff Law wrote: So as mentioned in the PR the underlying issue here is combine changes the form of an

[Bug c++/109422] wrong depth used for template parameter mangling for lambdas in function signatures

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109422 --- Comment #1 from Richard Smith --- > This should instead be mangled as T_TL__ Sorry, that's wrong; the rule we ended up with would mangle this as T_TL0__.

Re: [RFA][Bug target/108892 ][13 regression] Force re-recognition after changing RTL structure of an insn

On Wed, Apr 05, 2023 at 09:07:30AM -0600, Jeff Law wrote: > On 4/5/23 08:21, Segher Boessenkool wrote: > >On Wed, Mar 29, 2023 at 07:48:00AM -0600, Jeff Law wrote: > >>So as mentioned in the PR the underlying issue here is combine changes > >>the form of an existing insn, but fails to force

Re: [PATCH] c++: 'typename T::X' vs 'struct T::X' lookup [PR109420]

On Wed, Apr 5, 2023 at 10:32 AM Patrick Palka via Gcc-patches wrote: > > On Wed, 5 Apr 2023, Patrick Palka wrote: > > > r13-6098-g46711ff8e60d64 made make_typename_type no longer ignore > > non-types during the lookup, unless the TYPENAME_TYPE in question was > > followed by the :: scope

[Bug c++/109422] New: wrong depth used for template parameter mangling for lambdas in function signatures

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109422 Bug ID: 109422 Summary: wrong depth used for template parameter mangling for lambdas in function signatures Product: gcc Version: unknown Status: UNCONFIRMED

Re: [PATCH] c++: 'typename T::X' vs 'struct T::X' lookup [PR109420]

On Wed, 5 Apr 2023, Patrick Palka wrote: > r13-6098-g46711ff8e60d64 made make_typename_type no longer ignore > non-types during the lookup, unless the TYPENAME_TYPE in question was > followed by the :: scope resolution operator. But there is another > exception to this rule: we need to ignore

Re: [PATCH] dse: Handle SUBREGs of word REGs differently for WORD_REGISTER_OPERATIONS targets [PR109040]

On 4/5/23 10:48, Jakub Jelinek wrote: On Wed, Apr 05, 2023 at 10:17:59AM -0600, Jeff Law wrote: It is true that an instruction like (insn 8 7 9 2 (set (reg:HI 141) (subreg:HI (reg:SI 142) 0)) "aauu.c":6:18 181 {*movhi_internal} (nil)) can appear in the IL on

[Bug c++/109421] Compilation takes a long time for struct that contains a large default-initialized array

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

[Bug c++/92385] extremely long and memory intensive compilation for brace construction of array member

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92385 Andrew Pinski changed: What|Removed |Added CC||ejakobs at boerboeltrading dot com ---

[Bug c++/109421] Compilation takes a long time for struct that contains a large default-initialized array

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109421 --- Comment #1 from Andrew Pinski --- Looks to be fixed with GCC 12.1.0 .

[Bug c++/109421] New: Compilation takes a long time for struct that contains a large default-initialized array

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109421 Bug ID: 109421 Summary: Compilation takes a long time for struct that contains a large default-initialized array Product: gcc Version: 11.2.1 Status: UNCONFIRMED

[PATCH] c++: 'typename T::X' vs 'struct T::X' lookup [PR109420]

r13-6098-g46711ff8e60d64 made make_typename_type no longer ignore non-types during the lookup, unless the TYPENAME_TYPE in question was followed by the :: scope resolution operator. But there is another exception to this rule: we need to ignore non-types during the lookup also if the

Ping: [PATCH, V3] PR target/105325, Make load/cmp fusion know about prefixed loads

Ping patch: | Date: Mon, 27 Mar 2023 23:19:55 -0400 | From: Michael Meissner | Subject: [PATCH, V3] PR target/105325, Make load/cmp fusion know about prefixed loads | Message-ID: -- Michael Meissner, IBM PO Box 98, Ayer, Massachusetts, USA, 01432 email: meiss...@linux.ibm.com

[Bug libstdc++/98678] 30_threads/future/members/poll.cc execution test FAILs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98678 John David Anglin changed: What|Removed |Added CC||danglin at gcc dot gnu.org ---

Re: [PATCH] dse: Handle SUBREGs of word REGs differently for WORD_REGISTER_OPERATIONS targets [PR109040]

On Wed, Apr 05, 2023 at 10:17:59AM -0600, Jeff Law wrote: > > It is true that an instruction like > > (insn 8 7 9 2 (set (reg:HI 141) > > (subreg:HI (reg:SI 142) 0)) "aauu.c":6:18 181 {*movhi_internal} > > (nil)) > > can appear in the IL on WORD_REGISTER_OPERATIONS target, but I

Re: [PATCH] dse: Handle SUBREGs of word REGs differently for WORD_REGISTER_OPERATIONS targets [PR109040]

On 4/5/23 08:51, Jakub Jelinek wrote: On Wed, Apr 05, 2023 at 07:14:23AM -0600, Jeff Law wrote: The following testcase is miscompiled on riscv since the addition of *mvconst_internal define_insn_and_split. I believe the bug is in DSE. We have: (insn 36 35 39 2 (set (mem/c:SI (plus:SI

[committed] hppa: Fix 22_locale/locale/cons/12658_thread-2.cc on hppa

Committed to trunk. Dave --- Fix 22_locale/locale/cons/12658_thread-2.cc on hppa. 2023-04-05 John David Anglin libstdc++-v3/ChangeLog: * testsuite/22_locale/locale/cons/12658_thread-2.cc: Double timeout factor on hppa*-*-*. diff --git

[Bug middle-end/108892] [13 Regression] unable to generate reloads for at -Og on riscv64 since r13-4907

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108892 Jeffrey A. Law changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug middle-end/108892] [13 Regression] unable to generate reloads for at -Og on riscv64 since r13-4907

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108892 --- Comment #6 from CVS Commits --- The master branch has been updated by Jeff Law : https://gcc.gnu.org/g:4a45f5d6a9b53f7f5446dee47e25b07d413bb7eb commit r13-7013-g4a45f5d6a9b53f7f5446dee47e25b07d413bb7eb Author: Jeff Law Date: Wed Apr 5

[Bug target/109374] FAIL: gnat.dg/div_zero.adb execution test

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109374 --- Comment #12 from dave.anglin at bell dot net --- On 2023-04-05 10:56 a.m., ebotcazou at gcc dot gnu.org wrote: > Nice work! Your comments were accurate and very helpful. Thanks, dave

Re: [RFA][Bug target/108892 ][13 regression] Force re-recognition after changing RTL structure of an insn

On 4/5/23 08:21, Segher Boessenkool wrote: Hi! On Wed, Mar 29, 2023 at 07:48:00AM -0600, Jeff Law wrote: So as mentioned in the PR the underlying issue here is combine changes the form of an existing insn, but fails to force re-recognition. As a result other parts of the compiler blow up.

[Bug target/109374] FAIL: gnat.dg/div_zero.adb execution test

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109374 --- Comment #11 from Eric Botcazou --- Nice work!

  1   2   3   4   >