[Bug other/106429] make clean in libgcc fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106429 --- Comment #10 from Andrew Pinski --- It should be noted almost nobody does "make clean" really. Most just remove the build directory instead. Is there a reason why you build scripts are doing "make clean"?

[Bug other/106429] make clean in libgcc fails

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

Re: [PATCH 2/2] xtensa: Fix conflicting hard regno between indirect sibcall fixups and EH_RETURN_STACKADJ_RTX

On Fri, Jul 29, 2022 at 12:34 PM Takayuki 'January June' Suwa wrote: > > The hard register A10 was already allocated for EH_RETURN_STACKADJ_RTX. > (although exception handling and sibling call may not apply at the same time, > but for safety) > > gcc/ChangeLog: > > *

Re: [PATCH 1/2] xtensa: Add RTX costs for if_then_else

On Fri, Jul 29, 2022 at 12:34 PM Takayuki 'January June' Suwa wrote: > > It takes one machine instruction for both condtional branch and move. > > gcc/ChangeLog: > > * config/xtensa/xtensa.cc (xtensa_rtx_costs): > Add new case for IF_THEN_ELSE. > --- > gcc/config/xtensa/xtensa.cc

Re: [PATCH v3] LoongArch: add addr_global attribute

在 2022/7/30 上午1:17, Xi Ruoyao 写道: Change v2 to v3: - Disable section anchor for addr_global symbols. - Use -O2 in test to make sure section anchor is disabled. -- Background:

[Bug libfortran/106079] [12/13 regression] gfortran.dg/boz_15.f90 fails after r12-6498-g07c60b8e33

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106079 --- Comment #4 from seurer at gcc dot gnu.org --- The patch causes a bunch of new failures: FAIL: gfortran.dg/c-interop/allocatable-dummy.f90 -Os execution test FAIL: gfortran.dg/c-interop/allocate-errors.f90 -O0 execution test FAIL:

[Bug other/106429] Building GCC is Inhibited on old Linux Distributions due to the use of "#!/bin/bash"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106429 --- Comment #8 from Martin Vahi --- Thank You for the answers/replies. As of 2022_07_30 I am not familiar with the GCC source code, nor do I know the GCC build system, but as someone, who can do configure-make-make_install, I have the following

[Bug other/106429] Building GCC is Inhibited on old Linux Distributions due to the use of "#!/bin/bash"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106429 --- Comment #7 from Andrew Pinski --- (In reply to Martin Vahi from comment #5) > Created attachment 53385 [details] This is a failure while "make clean". And your patch does not even touch anything related to libgcc and "make clean". So

[Bug other/106429] Building GCC is Inhibited on old Linux Distributions due to the use of "#!/bin/bash"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106429 --- Comment #6 from Martin Vahi --- Created attachment 53386 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53386=edit List of changes that allow temporary use of an alternative Bash binary. Too old Bash version: GNU bash, version

[Bug other/106429] Building GCC is Inhibited on old Linux Distributions due to the use of "#!/bin/bash"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106429 --- Comment #5 from Martin Vahi --- Created attachment 53385 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53385=edit Console Output of the Bash Version Related GCC Build Failure ... gmake[1]: Entering directory

Re: [PATCH] analyzer: support for creat, dup, dup2 and dup3 in sm-fd.cc [PR106300]

On Fri, 2022-07-29 at 21:59 +0530, Immad Mir wrote: > This patch extends the state machine in sm-fd.cc to support > creat, dup, dup2 and dup3 functions. Thanks for the patch. Please can you use PR 106298 for this (in the ChangeLog and subject line), rather than 106300, as it's more specific.

gcc-11-20220729 is now available

Snapshot gcc-11-20220729 is now available on https://gcc.gnu.org/pub/gcc/snapshots/11-20220729/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 11 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

Re: FW: Redesigning the GCC website

> However, the website for the GCC is... shall we say... "bad". No, we shall not say that. We shall in fact loudly compliment the GCC web site as being "very well designed", because it serves exactly the purpose it's meant to serve with minimal distraction, while loading quickly on my slow

[Bug analyzer/106147] RFE: -fanalyzer could complain about some cases of infinite loops and infinite recursion

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

FW: Redesigning the GCC website

Hello! Nothing contained in this email is meant as an attack. The GCC compiler is a wonderful piece of software and by God I'll do anything to avoid writing ASM code. However, the website for the GCC is... shall we say... "bad". It looks outdated compared to the GNU project's homepage.

[PATCH, v3] Fortran: detect blanks within literal constants in free-form mode [PR92805]

Hi Mikael, Am 29.07.22 um 22:36 schrieb Mikael Morin: Indeed, I overlooked that, but my opinion remains that we shouldn’t play with fixed vs free form considerations here. So the options I can see are:  - handle the locus in get_kind; we do it a lot already in matching functions, so it

[Bug libfortran/106079] [12/13 regression] gfortran.dg/boz_15.f90 fails after r12-6498-g07c60b8e33

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106079 --- Comment #3 from seurer at gcc dot gnu.org --- I tried the patch on trunk and it fixed the failure. I am trying a full make check there and with gcc 12.

[Bug target/105980] [11/12/13 Regression] ICE in final_scan_insn_1, at final.cc:2811

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105980 --- Comment #6 from H.J. Lu --- (In reply to Jakub Jelinek from comment #5) > So, shall we temporarily disable -mforce-indirect-call during the mi thunk > output? Something like this diff --git a/gcc/config/i386/i386.cc

Re: [PATCH, v2] Fortran: detect blanks within literal constants in free-form mode [PR92805]

Le 29/07/2022 à 21:59, Harald Anlauf via Fortran a écrit : Am 29.07.22 um 13:11 schrieb Mikael Morin: > and use gfc_next_char instead of gfc_match_char in get_kind. There is one important functionality in gfc_match_char(): it manages the locus.  We would need then to add this explicitly to

[Bug target/105980] [11/12/13 Regression] ICE in final_scan_insn_1, at final.cc:2811

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105980 --- Comment #5 from Jakub Jelinek --- So, shall we temporarily disable -mforce-indirect-call during the mi thunk output?

Re: [PATCH] openmp-simd-clone: Match shift type

On Fri, Jul 29, 2022 at 06:03:18PM +0100, Andrew Stubbs wrote: > On 29/07/2022 16:59, Jakub Jelinek wrote: > > Doing the fold_convert seems to be a wasted effort to me. > > Can't this be done conditional on whether some change is needed at all > > and just using gimple_build_assign with NOP_EXPR,

Re: [PATCH, v2] Fortran: fix invalid rank error in ASSOCIATED when rank is remapped [PR77652]

Am 28.07.22 um 22:19 schrieb Mikael Morin: Hello, Le 27/07/2022 à 21:45, Harald Anlauf via Fortran a écrit : ok, I have thought about your comments in the review process, and played with the Cray compiler.  Attached is a refined version of the patch that now rejects in addition these cases for

[PATCH, v2] Fortran: detect blanks within literal constants in free-form mode [PR92805]

Hi Mikael, Am 29.07.22 um 13:11 schrieb Mikael Morin: Hello, Le 28/07/2022 à 22:11, Harald Anlauf via Fortran a écrit : Dear all, in free-form mode, blanks are significant, so they cannot appear in literal constants, especially not before or after the "_" that separates the literal and the

Re: [GCC13][Patch][V2][1/2]Add a new option -fstrict-flex-array[=n] and attribute strict_flex_array(n) and use it in PR101836

Hi, Richard, Thanks a lot for your comments and suggestions. (And sorry for my late reply). > On Jul 28, 2022, at 3:26 AM, Richard Biener wrote: > > On Tue, 19 Jul 2022, Qing Zhao wrote: > >> From 3854004802b8e2f132ebf218fc35a632f5e80c6a Mon Sep 17 00:00:00 2001 >> From: Qing Zhao >> Date:

[PATCH 2/2] xtensa: Fix conflicting hard regno between indirect sibcall fixups and EH_RETURN_STACKADJ_RTX

The hard register A10 was already allocated for EH_RETURN_STACKADJ_RTX. (although exception handling and sibling call may not apply at the same time, but for safety) gcc/ChangeLog: * config/xtensa/xtensa.md: Change hard register number used in the split patterns for indirect

[PATCH 1/2] xtensa: Add RTX costs for if_then_else

It takes one machine instruction for both condtional branch and move. gcc/ChangeLog: * config/xtensa/xtensa.cc (xtensa_rtx_costs): Add new case for IF_THEN_ELSE. --- gcc/config/xtensa/xtensa.cc | 1 + 1 file changed, 1 insertion(+) diff --git a/gcc/config/xtensa/xtensa.cc

[Bug target/105980] [11/12/13 Regression] ICE in final_scan_insn_1, at final.cc:2811

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105980 --- Comment #4 from H.J. Lu --- We don't have available scratch registers in 32-bit mode for x86_output_mi_thunk.

[Bug libstdc++/106469] Undefined behavior triggered on Mersenne Twister engine due to unsigned integer overflow

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106469 --- Comment #7 from Andrew Pinski --- "An unsigned overflow" does not exist. That is the point here. And that is why this sanitizer is bogus and should never be used. And yes overflow wrapping is sometimes a bug in the code but if the code

[Bug testsuite/105959] new test case c-c++-common/diagnostic-format-sarif-file-4.c from r13-967-g6cf276ddf22066 fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105959 John David Anglin changed: What|Removed |Added Build|powerpc64-linux-gnu,|powerpc64-linux-gnu,

[Bug tree-optimization/106480] New: FAIL: gcc.dg/Warray-bounds-48.c pr102706 (test for warnings, line 33)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106480 Bug ID: 106480 Summary: FAIL: gcc.dg/Warray-bounds-48.c pr102706 (test for warnings, line 33) Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[Bug libstdc++/106469] Undefined behavior triggered on Mersenne Twister engine due to unsigned integer overflow

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106469 --- Comment #6 from Henry --- > This sanitizer is stupid. That is an unjust comment on great work from the LLVM team. An unsigned overflow in user code is almost always a bug due to some oversight, there is no denying that. Look at Arianne 5

[Bug analyzer/106479] New: FAIL: gcc.dg/analyzer/pr104308.c (test for warnings, line 9)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106479 Bug ID: 106479 Summary: FAIL: gcc.dg/analyzer/pr104308.c (test for warnings, line 9) Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[PATCH v3] LoongArch: add addr_global attribute

Change v2 to v3: - Disable section anchor for addr_global symbols. - Use -O2 in test to make sure section anchor is disabled. -- Background: https://lore.kernel.org/loongarch/d7670b60-2782-4642-995b-7baa01779...@loongson.cn/T/#e1d47e2fe185f2e2be8fdc0784f0db2f644119379 Question: Do you have a

☺ Buildbot (GNU Toolchain): gccrust - build successful (master)

A passing build has been detected on builder gccrust-rawhide-x86_64 while building gccrust. Full details are available at: https://builder.sourceware.org/buildbot/#builders/132/builds/70 Build state: build successful Revision: e88a55ab6919346e0afe79bfd13f84ecf9634889 Worker: bb1 Build

Re: [PATCH] openmp-simd-clone: Match shift type

On 29/07/2022 16:59, Jakub Jelinek wrote: Doing the fold_convert seems to be a wasted effort to me. Can't this be done conditional on whether some change is needed at all and just using gimple_build_assign with NOP_EXPR, so something like: I'm just not familiar enough with this stuff to run

[Bug c++/106478] New: GCC rejects valid code involving partial specialization of variable template

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106478 Bug ID: 106478 Summary: GCC rejects valid code involving partial specialization of variable template Product: gcc Version: 11.2.0 Status: UNCONFIRMED

[Bug libstdc++/106477] With -fno-exception operator new(nothrow) aborts instead of returning null

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

[Bug tree-optimization/106474] DCE depends on how if expressions are nested

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106474 --- Comment #2 from Andrew Macleod --- (In reply to Richard Biener from comment #1) > For the failing case we see > >: > if (c_5(D) == s_6(D)) > goto ; [INV] > else > goto ; [INV] > >: > if (c_5(D) != 0) > goto ;

[PATCH] analyzer: support for creat, dup, dup2 and dup3 in sm-fd.cc [PR106300]

This patch extends the state machine in sm-fd.cc to support creat, dup, dup2 and dup3 functions. Lightly tested on x86_64 Linux. gcc/analyzer/ChangeLog: PR analyzer/106300 * sm-fd.cc (fd_state_machine::on_open): Add creat, dup, dup2 and dup3 functions. (enum dup):

[Bug libstdc++/68210] nothrow operator fails to call default new

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68210 Matthijs Kooijman changed: What|Removed |Added CC||matthijs at stdin dot nl ---

[Bug libstdc++/106477] With -fno-exception operator new(nothrow) aborts instead of returning null

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106477 --- Comment #3 from Matthijs Kooijman --- Created attachment 53384 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53384=edit Testcase - linker script for ATSAMD21G18 (Arduino zero)

[Bug libstdc++/106477] With -fno-exception operator new(nothrow) aborts instead of returning null

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106477 --- Comment #2 from Matthijs Kooijman --- Created attachment 53383 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53383=edit Testcase - startup code

[Bug libstdc++/106477] With -fno-exception operator new(nothrow) aborts instead of returning null

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106477 --- Comment #1 from Matthijs Kooijman --- Created attachment 53382 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53382=edit Testcase - main code

[Bug libstdc++/106477] New: With -fno-exception operator new(nothrow) aborts instead of returning null

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106477 Bug ID: 106477 Summary: With -fno-exception operator new(nothrow) aborts instead of returning null Product: gcc Version: 11.2.1 Status: UNCONFIRMED Severity:

[Bug target/99410] Nios II Error: branch offset out of range

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99410 --- Comment #9 from Giulio Benetti --- This bug shows up with gcc 11.3.0 and 12.1.0

Re: [PATCH] openmp-simd-clone: Match shift type

On Fri, Jul 29, 2022 at 04:53:51PM +0100, Andrew Stubbs wrote: > This patch adjusts the generation of SIMD "inbranch" clones that use integer > masks to ensure that it vectorizes on amdgcn. > > The problem was only that an amdgcn mask is DImode and the shift amount was > SImode, and the

[PATCH] openmp-simd-clone: Match shift type

This patch adjusts the generation of SIMD "inbranch" clones that use integer masks to ensure that it vectorizes on amdgcn. The problem was only that an amdgcn mask is DImode and the shift amount was SImode, and the difference causes vectorization to fail. OK for mainline?

Re: Regarding gnu.org

Hi, So, what do you think? Regards, Mark Smith [image: Mailtrack] Sender notified by Mailtrack 07/29/22, 09:10:46 PM

[PATCH v2] LoongArch: add addr_global attribute

Don't look at V1 patch: I selected wrong file and sent a draft with bugs mistakenly. Background: https://lore.kernel.org/loongarch/d7670b60-2782-4642-995b-7baa01779...@loongson.cn/T/#e1d47e2fe185f2e2be8fdc0784f0db2f644119379 Question: Do you have a better name than "addr_global"? Alternatives:

[Bug tree-optimization/106315] [13 Regression] 7.8% increased codesize on specfp 507.cactuBSSN_r

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106315 --- Comment #5 from H.J. Lu --- Here is the testcase: --- void bar(int *indices, int max_iter, int *actual_indices, int *iters_per_dim, int N_dims) { int iter = 0; int sum_indices = 0; int flag, k; while (iter < max_iter) { for

[Bug target/106458] [12/13 Regression] glibc's malloc/tst-scratch_buffer.c test is miscompiled with gcc-12

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106458 --- Comment #6 from dave.anglin at bell dot net --- On 2022-07-29 8:50 a.m., dave.anglin at bell dot net wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106458 > > --- Comment #5 from dave.anglin at bell dot net --- > On 2022-07-28 4:12

[Bug libfortran/106079] [12/13 regression] gfortran.dg/boz_15.f90 fails after r12-6498-g07c60b8e33

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106079 Jakub Jelinek changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned

GCC warns on defined behavior with Wrestrict?

Hi everyone, while testing a new buffer overlap and restrict checker in the analyzer, it emitted a warning inside coreutils. During the discussion [0], Paul Eggert posted a link to the current draft of the next C standard [1] with new examples for the definition of 'restrict'. Especially example

Re: [GCC13][Patch][V2][2/2]Add a new option -fstrict-flex-array[=n] and attribute strict_flex_array(n) and use it in PR101836

> On Jul 28, 2022, at 3:28 AM, Richard Biener wrote: > > On Tue, 19 Jul 2022, Qing Zhao wrote: > >> From a09f39ded462611286a44d9e8273de8342673ba2 Mon Sep 17 00:00:00 2001 >> From: Qing Zhao >> Date: Mon, 18 Jul 2022 18:12:26 + >> Subject: [PATCH 2/2] Use new flag DECL_NOT_FLEXARRAY in

[PATCH] LoongArch: add addr_global attribute

Background: https://lore.kernel.org/loongarch/d7670b60-2782-4642-995b-7baa01779...@loongson.cn/T/#e1d47e2fe185f2e2be8fdc0784f0db2f644119379 Question: Do you have a better name than "addr_global"? Alternatives: 1. Just use "-mno-explicit-relocs -mla-local-with-abs" for kernel modules. It's

[PATCH v2] cselib: add function to check if SET is redundant [PR106187]

A SET operation that writes memory may have the same value as an earlier store but if the alias sets of the new and earlier store do not conflict then the set is not truly redundant. This can happen, for example, if objects of different types share a stack slot. To fix this we define a new

[Bug tree-optimization/106475] Loop vectorizer prevents vectorization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106475 Christoph Müllner changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug tree-optimization/53947] [meta-bug] vectorizer missed-optimizations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947 Bug 53947 depends on bug 106475, which changed state. Bug 106475 Summary: Loop vectorizer prevents vectorization https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106475 What|Removed |Added

[Bug target/105980] [11/12/13 Regression] ICE in final_scan_insn_1, at final.cc:2811

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

[Bug tree-optimization/106475] Loop vectorizer prevents vectorization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106475 --- Comment #2 from Christoph Müllner --- Yes, you are right! I haven't noticed that the longer sequence requires only half of the loop iterations when compared to the shorter sequence.

[Bug analyzer/106007] RFE: analyzer should complain about exec/system/putenv of tainted args

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106007 Tim Lange changed: What|Removed |Added CC||tlange at gcc dot gnu.org --- Comment #3

[Bug target/105617] [12/13 Regression] Slp is maybe too aggressive in some/many cases

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105617 --- Comment #15 from Michael_S --- (In reply to Richard Biener from comment #14) > (In reply to Michael_S from comment #12) > > On related note... > > One of the historical good features of gcc relatively to other popular > > compilers was

[Bug c++/106466] ICE in In function 'bool jxl_skcms_Parse(const void*, size_t, skcms_ICCProfile*)': at skcms/skcms.cc:1004:6 internal compiler error: Segmentation fault

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106466 --- Comment #6 from tt_1 --- works with: gcc-10.3.0 gcc-10.3.1_p20211126 gcc-11.3.0 does not work with: gcc-10.4.0 the segfault is sort of spurious, its an about 1/5 to 1/7 chance for me. Is that something you can work with? and

Re: [PATCH v2] powerpc: add documentation for HWCAPs

On Fri, 15 Jul 2022 11:26:36 +1000, Nicholas Piggin wrote: > Take the arm64 HWCAP documentation file and adjust it for powerpc. > > Applied to powerpc/next. [1/1] powerpc: add documentation for HWCAPs https://git.kernel.org/powerpc/c/ef1911c6d26678b0e91fea33f076e98925997f0c cheers

[Bug tree-optimization/106476] New: ICE generating FOLD_EXTRACT_LAST

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106476 Bug ID: 106476 Summary: ICE generating FOLD_EXTRACT_LAST Product: gcc Version: unknown Status: UNCONFIRMED Severity: major Priority: P3 Component:

[Bug target/106458] [12/13 Regression] glibc's malloc/tst-scratch_buffer.c test is miscompiled with gcc-12

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106458 --- Comment #5 from dave.anglin at bell dot net --- On 2022-07-28 4:12 a.m., rguenth at gcc dot gnu.org wrote: > Can you check trunk / the gcc 12 branch head? Test fails in the same way with trunk.

Progress of the new linking implementation

Hello, the non shared library linking is complete and the gm2 driver has been rewritten using the fortran/c++ code base. Once the shared library scaffold is complete the focus will be on tidying up and platform/architecture testing. All 11.7k tests pass on amd64 and aarch64 debian regards,

[Bug rtl-optimization/102446] [10/11 Regression] wrong code at -O3 on x86_64-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102446 --- Comment #17 from Jakub Jelinek --- So dup or related to PR106032.

[Bug rtl-optimization/102446] [10/11 Regression] wrong code at -O3 on x86_64-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102446 Jakub Jelinek changed: What|Removed |Added Keywords|needs-bisection | --- Comment #16 from Jakub Jelinek

[Bug tree-optimization/106475] Loop vectorizer prevents vectorization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106475 --- Comment #1 from Richard Biener --- The loop seems to be vectorized just fine? The issue is just that we need a runtime alias check because of the variable stride and the fact that we need a VF of two to fill up to 16 byte vectors: .L5:

Re: Setting up editors for the GNU/GCC coding style?

On 28/07/2022 22:43, Iannetta Paul wrote: About configuring recent editors to follow the GNU coding style, I don't really know but it should always be possible to register a hook that will run `indent` when the file is saved. I don't think that's a good idea. It will result in quite a

[Bug target/68485] ICE while building gpsd package on microblaze

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68485 --- Comment #11 from Giulio Benetti --- And it shows up on gcc 12.1.0 too.

[Bug ipa/101839] [10/11/12/13 Regression] Hang in C++ code with -fdevirtualize

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101839 --- Comment #7 from Richard Biener --- Honza?

[Bug rtl-optimization/102446] [10/11 Regression] wrong code at -O3 on x86_64-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102446 Richard Biener changed: What|Removed |Added Summary|[10/11/12/13 Regression]|[10/11 Regression] wrong

Re: [PATCH] tree-optimization/105679 - disable backward threading of unlikely entry

On Fri, 29 Jul 2022, Aldy Hernandez wrote: > On Fri, Jul 29, 2022 at 11:02 AM Richard Biener wrote: > > > > The following makes the backward threader reject threads whose entry > > edge is probably never executed according to the profile. That in > > particular, for the testcase, avoids

[committed] amdgcn: 64-bit vector shifts

I've committed this patch to implement V64DImode vector-vector and vector-scalar shifts. In particular, these are used by the SIMD "inbranch" clones that I'm working on right now, but it's an omission that ought to have been fixed anyway. Andrewamdgcn: 64-bit vector shifts Enable 64-bit

[committed] amdgcn: 64-bit not

I've committed this patch to enable DImode one's-complement on amdgcn. The hardware doesn't have 64-bit not, and this isn't needed by expand which is happy to use two SImode operations, but the vectorizer isn't so clever. Vector condition masks are DImode on amdgcn, so this has been causing

[Bug tree-optimization/106073] [12/13 Regression] wrong code at -O3 on x86_64-linux-gnu since r12-3903-g0288527f47cec669

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106073 Richard Biener changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug target/68485] ICE while building gpsd package on microblaze

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68485 Giulio Benetti changed: What|Removed |Added CC||giulio.benetti@benettiengin

Re: spaceship_replacement cannot see through simplified set of FP conditionals

On Fri, Jul 29, 2022 at 01:51:00PM +0200, Aldy Hernandez wrote: > Swt! > > Would you like me to XFAIL the test or leave it as a failure? Either is fine. Jakub

Re: spaceship_replacement cannot see through simplified set of FP conditionals

Swt! Would you like me to XFAIL the test or leave it as a failure? Thanks. Aldy On Fri, Jul 29, 2022 at 1:50 PM Jakub Jelinek wrote: > > On Fri, Jul 29, 2022 at 01:40:12PM +0200, Aldy Hernandez wrote: > > With my upcoming patch enabling floating point VRP, > > g++.dg/opt/pr94589-2.C is

Re: spaceship_replacement cannot see through simplified set of FP conditionals

On Fri, Jul 29, 2022 at 01:40:12PM +0200, Aldy Hernandez wrote: > With my upcoming patch enabling floating point VRP, > g++.dg/opt/pr94589-2.C is failing: > > https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598788.html > > The problem is that phiopt no longer sees the following snippet, >

[Bug tree-optimization/106475] New: Loop vectorizer prevents vectorization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106475 Bug ID: 106475 Summary: Loop vectorizer prevents vectorization Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

Re: [PATCH] tree-optimization/105679 - disable backward threading of unlikely entry

On Fri, Jul 29, 2022 at 11:02 AM Richard Biener wrote: > > The following makes the backward threader reject threads whose entry > edge is probably never executed according to the profile. That in > particular, for the testcase, avoids threading the irq == 1 check > on the path where irq > 31,

spaceship_replacement cannot see through simplified set of FP conditionals

Hi. With my upcoming patch enabling floating point VRP, g++.dg/opt/pr94589-2.C is failing: https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598788.html The problem is that phiopt no longer sees the following snippet, because we have folded away the final conditional as true: bool f5 (double

Re: [patch] libgompd: Add thread handles

On Mon, Jul 04, 2022 at 10:34:03PM +0200, Ahmed Sayed Mousse wrote: > *This patch is the initial implementation of OpenMP-API specs book section > **20.5.5 with title "Thread Handles".* Sorry for the delay, have been on vacation. > *I have fixed the first version after revising the notes on it.*

[Bug target/106069] [12/13 Regression] wrong code with -O -fno-tree-forwprop -maltivec on ppc64le

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106069 --- Comment #18 from Richard Biener --- (In reply to Richard Biener from comment #17) > Seeing > > Trying 21 -> 24: >21: r150:V4SI=vec_select(vec_concat(r146:V4SI,r141:V4SI),parallel) > REG_DEAD r146:V4SI > REG_DEAD r141:V4SI >

Re: [PATCH] Fortran: detect blanks within literal constants in free-form mode [PR92805]

Hello, Le 28/07/2022 à 22:11, Harald Anlauf via Fortran a écrit : Dear all, in free-form mode, blanks are significant, so they cannot appear in literal constants, especially not before or after the "_" that separates the literal and the kind specifier. The initial patch from Steve addressed

[Bug target/106069] [12/13 Regression] wrong code with -O -fno-tree-forwprop -maltivec on ppc64le

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106069 --- Comment #17 from Richard Biener --- Seeing Trying 21 -> 24: 21: r150:V4SI=vec_select(vec_concat(r146:V4SI,r141:V4SI),parallel) REG_DEAD r146:V4SI REG_DEAD r141:V4SI 24: {r151:SI=vec_select(r150:V4SI,parallel);clobber

Re: [RFC] Teach vectorizer to deal with bitfield reads

On Fri, 29 Jul 2022, Jakub Jelinek wrote: > On Fri, Jul 29, 2022 at 09:57:29AM +0100, Andre Vieira (lists) via > Gcc-patches wrote: > > The 'only on the vectorized code path' remains the same though as vect_recog > > also only happens on the vectorized code path right? > > if conversion (in

[Bug middle-end/106467] [OpenMP] Wrong code with collapse – tree sharing issue.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106467 --- Comment #4 from Tobias Burnus --- For completeness, the testcase https://gcc.gnu.org/pipermail/gcc-patches/2022-July/599041.html was committed as https://gcc.gnu.org/r13-1893-g85fe7e7dd1f1461b86d92a3a0c1bfd97a06efcc0

[PATCH] Mips: Enable TSAN for 64-bit ABIs

The following patch enables TSAN for mips64, on which it is supported. Signed-off-by: Dimitrije Milosevic . libsanitizer/ChangeLog: * configure.tgt: Enable TSAN for 64-bit ABIs. --- libsanitizer/configure.tgt | 4 1 file changed, 4 insertions(+) diff --git

Re: [Patch] Add libgomp.c-c++-common/pr106449-2.c (was: [committed] openmp: Fix up handling of non-rectangular simd loops with pointer type iterators [PR106449])

On Fri, Jul 29, 2022 at 11:48:08AM +0200, Tobias Burnus wrote: > On 29.07.22 10:03, Jakub Jelinek wrote: > > There were 2 issues visible on this new testcase, one that we didn't have > > special POINTER_TYPE_P handling in a few spots of expand_omp_simd ... > > The other issue was that we put n2

Re: [Patch] OpenMP/Fortran: Permit assumed-size arrays in uniform clause

On Fri, Jul 29, 2022 at 11:47:54AM +0200, Tobias Burnus wrote: > Testcase wise, the run-time testcase libgomp.fortran/examples-4/simd-2.f90 > checks essentially the same, except that it uses an array-descriptor array > (assumed shape) while this testcase uses an assumed-size array. > > I decided

Re: [RFC] Teach vectorizer to deal with bitfield reads

On Fri, Jul 29, 2022 at 09:57:29AM +0100, Andre Vieira (lists) via Gcc-patches wrote: > The 'only on the vectorized code path' remains the same though as vect_recog > also only happens on the vectorized code path right? if conversion (in some cases) duplicates a loop and guards one copy with an

[Bug tree-optimization/105679] [12 Regression] extra -Warray-bounds warning added with -fsanitize=shift due to jump threading

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105679 Richard Biener changed: What|Removed |Added Known to work||13.0 Summary|[12/13

[Bug tree-optimization/105679] [12/13 Regression] extra -Warray-bounds warning added with -fsanitize=shift due to jump threading

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105679 --- Comment #4 from CVS Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:49ba4fdeb648c149fa7d964ba812084262c3d06f commit r13-1891-g49ba4fdeb648c149fa7d964ba812084262c3d06f Author: Richard Biener Date:

Re: cselib: add function to check if SET is redundant [PR106187]

On Fri, Jul 29, 2022 at 11:52 AM Richard Earnshaw wrote: > > > > On 29/07/2022 08:06, Richard Biener via Gcc-patches wrote: > > On Thu, Jul 28, 2022 at 6:46 PM Richard Earnshaw > > wrote: > >> > >> [resend with correct subject line] > >> > >> A SET operation that writes memory may have the same

Re: cselib: add function to check if SET is redundant [PR106187]

On 29/07/2022 08:06, Richard Biener via Gcc-patches wrote: On Thu, Jul 28, 2022 at 6:46 PM Richard Earnshaw wrote: [resend with correct subject line] A SET operation that writes memory may have the same value as an earlier store but if the alias sets of the new and earlier store do not

[Bug tree-optimization/106474] DCE depends on how if expressions are nested

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106474 Richard Biener changed: What|Removed |Added Keywords||missed-optimization

  1   2   >