Re: MicroBlaze symver attribute support

All On Mon, Feb 20, 2023 at 7:35 PM Michael Eager wrote: > On 2/20/23 06:54, Joel Sherrill wrote: > > > > > > On Mon, Feb 20, 2023 at 7:56 AM Vincent Fazio via Gcc > > wrote: > > > > Michael, all, > > > > Regarding: > >

M

W I’maI hope w S

gcc-11-20230303 is now available

Snapshot gcc-11-20230303 is now available on https://gcc.gnu.org/pub/gcc/snapshots/11-20230303/ 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

[GSOC] Looking for small patch/project to work on

Hi everyone, My name is Rishi Raj, and I am a third-year undergraduate studying Computer Science and Engineering at the Indian Institute of Technology Kharagpur in India. I wish to participate in this year's GSOC with GCC. My progress so far: 1. Successfully built the GCC from source using

[gnu.org #1880318] Antoni Boucher, modified employer disclaimer

On 2023-02-28 17:44:55, boua...@zoho.com wrote: > Hi. > Here is the document signed. > Thank you. > My apologies, I was unexpectedly out the last couple of days. This has been resolved and you are clear to contribute with the new employer disclaimer in place. Thank you for your patience and I

Re: [GSoC] Introduction and query on LTO object emmission project

Hello, > Hi! I've been interested in compiler development for a while, and would love > to > work with any of you as part of GSoC, or even just as a side-project on my > own. > > I'm an 18 year-old student going into university next year with a passion for > all > things open source and low

Re: [libstdc++] Use __gthread_join in jthread/95989

On Feb 17, 2023, Jonathan Wakely wrote: > The proper fix is to ensure the program has a non-weak reference to > pthread_join without extra help (or use a recent glibc where it always > works). Indeed! How about this? Regstrapped on x86_64-linux-gnu, also tested on arm-vx7r2 (gcc-12); verified

Re: [PATCH] [arm] adjust expectations for armv8_2-fp16-move-[12].c

On Feb 17, 2023, Alexandre Oliva wrote: > * gcc.target/arm/armv8_2-fp16-move-1.c: Combine vcmp and vcmpe > expected counts into a single pattern. > * gcc.target/arm/armv8_2-fp16-move-2.c: Accept conditional > return and reversed conditions. Ping?

[Bug tree-optimization/108997] GCC prediction on bool comparisons seems wrong

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108997 Richard Biener changed: What|Removed |Added CC||hubicka at gcc dot gnu.org ---

[Bug tree-optimization/109002] -O1 -ftree-pre -ftree-partial-pre results in stall value

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109002 Richard Biener changed: What|Removed |Added Last reconfirmed||2023-03-03

[PATCHv2, gfortran] Escalate failure when Hollerith constant to real conversion fails [PR103628]

Hi, The patch escalates the failure when Hollerith constant to real conversion fails in native_interpret_expr. It finally reports an "Unclassifiable statement" error. The patch of pr95450 added a verification for decoding/encoding checking in native_interpret_expr. native_interpret_expr may

Re: Re: [PATCH] RISC-V: Optimize the MASK opt generation

On 2023-03-03 16:54  jiawei wrote: > >The Mask flag in the single TargetVariable is not enough due to more >and more extensions were added.So I optimize the defination of Mask >flag, please refer to the below case: >There are some new MASK flags for 'v' extension(ZVL32B,ZVL64B,...,ZVL65536B), >but

RE: [PATCH] [arm] adjust tests for quotes around +cdecp

> -Original Message- > From: Gcc-patches bounces+kyrylo.tkachov=arm@gcc.gnu.org> On Behalf Of Alexandre > Oliva via Gcc-patches > Sent: Friday, March 3, 2023 8:24 AM > To: Christophe Lyon > Cc: gcc-patches@gcc.gnu.org > Subject: Re: [PATCH] [arm] adjust tests for quotes around

[Bug debug/108996] Proposal for adding DWARF call site information in GCC with -O0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108996 --- Comment #2 from Jakub Jelinek --- I think there are several open PRs about var-tracking at -O0, which would be nice e.g. for VLAs. The main problem is that var-tracking is very expensive, so if we do it, it should track a very small subset

Re: [PATCHv2, gfortran] Escalate failure when Hollerith constant to real conversion fails [PR103628]

Hi Haochen, thanks for fixing 'gcc/fortran/target-memory.cc'. But could you also include the 'gcc/fortran/intrinsic.cc' change proposed in https://gcc.gnu.org/pipermail/gcc-patches/2023-March/613030.html (and acknowledged by Steve)? This will replace "Unclassifiable statement" by "Cannot

Re: [libstdc++] Use __gthread_join in jthread/95989

On Fri, 3 Mar 2023 at 08:20, Alexandre Oliva via Libstdc++ < libstd...@gcc.gnu.org> wrote: > On Feb 17, 2023, Jonathan Wakely wrote: > > > The proper fix is to ensure the program has a non-weak reference to > > pthread_join without extra help (or use a recent glibc where it always > > works). >

[Bug libstdc++/108630] build failure with LTO enabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108630 --- Comment #6 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #5) > LTO will almost certainly break src/c++98/globals_io.cc so I don'tthink we > can support building libstdc++ with LTO for now. And would probably break the

[PATCH] gimple-fold: Fix up fputs -> fwrite folding [PR108988]

Hi! gimple_fold_builtin_fputs when folding fputs into fwrite emits the third argument (INTEGER_CST) with incorrect type - get_maxval_strlen or c_strlen return ssizetype, while fwrite argument is size_type_node. The following patch fixes that, I've skimmed through the rest of gimple-fold.cc and in

Re: [libstdc++] Use __gthread_join in jthread/95989

On Fri, 3 Mar 2023 at 09:33, Jonathan Wakely wrote: > > > On Fri, 3 Mar 2023 at 08:20, Alexandre Oliva via Libstdc++ < > libstd...@gcc.gnu.org> wrote: > >> On Feb 17, 2023, Jonathan Wakely wrote: >> >> > The proper fix is to ensure the program has a non-weak reference to >> > pthread_join

[Bug target/109004] New: wrong code for -O2 (any above -O0) with g++ 11.3 for POWER9 (cross-compiler on x86_64 host)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109004 Bug ID: 109004 Summary: wrong code for -O2 (any above -O0) with g++ 11.3 for POWER9 (cross-compiler on x86_64 host) Product: gcc Version: 11.3.0 Status: UNCONFIRMED

[PATCH] waccess: Fix two -Wnonnull warning issues [PR108986]

Hi! The following patch fixes 2 issues with the -Wnonnull warning. One, fixed by the second hunk, is that the warning wording is bogus since r11-3305, instead of printing warning: argument 1 to ‘int[static 7]’ is null where non-null expected [-Wnonnull] it prints warning: argument 1 to

[PATCH v2] LoongArch: Stop -mfpu from silently breaking ABI [PR109000]

In the toolchain convention, we describe -mfpu= as: "Selects the allowed set of basic floating-point instructions and registers. This option should not change the FP calling convention unless it's necessary." Though not explicitly stated, the rationale of this rule is to allow combinations like

Re: [PATCH] [arm] adjust tests for quotes around +cdecp

Hello, Christophe, On Feb 22, 2023, Christophe Lyon wrote: > OK thanks for the clarification. > (and for the other cleanup patches!) Was this meant as approval? I hadn't taken it as such. Otherwise, please consider this a ping :-)

Re: [PATCH] -Wdangling-pointer: don't mark SSA lhs sets as stores

On Feb 17, 2023, Richard Biener wrote: >> * gimple-ssa-warn-access.cc >> (pass_waccess::check_dangling_stores): Skip non-stores. >> >> for gcc/testsuite/ChangeLog >> >> * g++.dg/warn/Wdangling-pointer.C (warn_init_ref_member): Add >> two new variants, one fixed, one xfailed. >> *

[Bug target/108994] [13 Regression] LLVM JIT segfaults in libgcc after upgrading from gcc 12.2.1 to 13.0.1

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

[Bug libffi/108682] libffi needs to merge upstream to get LoongArch support

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108682 --- Comment #4 from Xi Ruoyao --- (In reply to Andreas Schwab from comment #3) > libgo/goarch.sh is missing LoongArch support. We ship a go 1.18 runtime but LoongArch support was added in 1.19. Updating go runtime in stage 3 is definitely not

Re: [PATCH] RISC-V: Optimize the MASK opt generation

The Mask flag in the single TargetVariable is not enough due to more and more extensions were added.So I optimize the defination of Mask flag, please refer to the below case: There are some new MASK flags for 'v' extension(ZVL32B,ZVL64B,...,ZVL65536B), but these MASK flags can't store into

[PATCH] driver: toplev: Fix a typo

The driver emits a warning when -fstack-check and -fstack-clash-protection are used together, but the message refers to "-fstack-clash_protection" (underline instead of dash). gcc/ChangeLog: * toplev.cc (process_options): Fix the spelling of "-fstack-clash-protection". ---

RE: [PATCH] [PR104882] [arm] require mve hw for mve run test

> -Original Message- > From: Alexandre Oliva > Sent: Friday, February 17, 2023 7:39 AM > To: gcc-patches@gcc.gnu.org > Cc: ni...@redhat.com; Richard Earnshaw ; > ramana@gmail.com; Kyrylo Tkachov > Subject: [PATCH] [PR104882] [arm] require mve hw for mve run test > > > The

Re: [PATCH] libgccjit: Fix a failing test

Thanks! Le jeu. 2 mars 2023 à 23:54, David Malcolm a écrit : > On Thu, 2023-03-02 at 23:35 +0100, Guillaume Gomez wrote: > > I don't have push rights so if you could push it, it'd be super > > appreciated! > > Done, as r13-6425-g6b432c0f777ab9; I took the liberty of slightly > tweaking the

[Bug c++/108219] [12 Regression] requirement fails on a valid expression since r12-5253-g4df7f8c79835d569

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108219 --- Comment #5 from Ivan Sorokin --- (In reply to Patrick Palka from comment #4) > Fixed for GCC 13 so far Thank you very much!

[PATCH] diagnostics: Fix up selftests with $COLUMNS < 42 [PR108973]

Hi! As mentioned in the PR, GCC's diagnostics self-tests fail if $COLUMNS < 42. Guarding each self-test with if (get_terminal_width () > 41) or similar would be a maintainance nightmare (PR has a patch to do so without reformatting to make it work for $COLUMNS in [30, 41] inclusive, but I'm

[Bug tree-optimization/109002] -O1 -ftree-pre -ftree-partial-pre results in stall value

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109002 --- Comment #4 from Richard Biener --- When doing partial PRE we somehow lose the effect of g = 1; we also generate weird PHIs: pretmp_20 = h; pretmp_22 = g; # prephitmp_21 = PHI # prephitmp_23 = PHI # prephitmp_24 = PHI

Re: [PATCH] libstdc++: Update Solaris baselines for GCC 13.0

On Tue, 21 Feb 2023 at 08:34, Rainer Orth wrote: > This patch updates the libstdc++ Solaris baselines for GCC 13. > > Tested on i386-pc-solaris2.11 and sparc-sun-solaris2.11 (Solaris 11.3 > and 11.4). > > Ok for trunk? > OK, thanks.

[Bug tree-optimization/108988] gimple_fold_builtin_fputs doesn't preserve gimple_builtin_call_types_compatible_p

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108988 --- Comment #5 from CVS Commits --- The master branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:dbeccab7a1f5dcc1876c854f17816047ba1ef137 commit r13-6441-gdbeccab7a1f5dcc1876c854f17816047ba1ef137 Author: Jakub Jelinek Date:

[Bug libgcc/108727] gcc.dg/split-5.c fails on power 9 BE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108727 Kewen Lin changed: What|Removed |Added CC||amodra at gcc dot gnu.org,

Re: [PATCH v3] RISC-V: Bugfix for rvv bool mode precision adjustment

Thanks! RISC-V part is LGTM, and I would like to wait for Richard Sandiford to say OK to the genmodes.cc part :) On Fri, Mar 3, 2023 at 10:31 AM wrote: > > From: Pan Li > > Fix the bug of the rvv bool mode precision with the adjustment. > The bits size of vbool*_t will be

Re: [PATCH] [PR104882] [arm] require mve hw for mve run test

On Feb 20, 2023, Andrea Corallo wrote: > Alexandre Oliva via Gcc-patches writes: >> PR target/104882 >> * gcc.target/arm/simd/pr104882.c: Require mve hardware. > no approver here but LGTM, thanks. Ping? https://gcc.gnu.org/pipermail/gcc-patches/2023-February/612194.html -- Alexandre Oliva,

[Bug debug/108996] Proposal for adding DWARF call site information in GCC with -O0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108996 Richard Biener changed: What|Removed |Added Last reconfirmed||2023-03-03 Ever confirmed|0

Re: [PATCH] RISC-V: Optimize the MASK opt generation

> The Mask flag in the single TargetVariable is not enough due to more> and > more extensions were added.So I optimize the defination of Mask> flag, please > refer to the below case:> There are some new MASK flags for 'v' > extension(ZVL32B,ZVL64B,...,ZVL65536B),> but these MASK flags can't

Re: [PATCH] driver: toplev: Fix a typo

On Fri, 2023-03-03 at 16:54 +0800, Xi Ruoyao wrote: > The driver emits a warning when -fstack-check and > -fstack-clash-protection are used together, but the message refers to > "-fstack-clash_protection" (underline instead of dash). Forgot: Ok for trunk? Though I think it's obvious but let's

Re: [PATCH] [arm] adjust tests for quotes around +cdecp

On 3/3/23 09:24, Alexandre Oliva wrote: Hello, Christophe, On Feb 22, 2023, Christophe Lyon wrote: OK thanks for the clarification. (and for the other cleanup patches!) Was this meant as approval? I hadn't taken it as such. Unfortunately, no, I don't have such powers :-)

Re: [PATCHv2, gfortran] Escalate failure when Hollerith constant to real conversion fails [PR103628]

Hi, The patch passed regression test on Power linux platforms. Sorry for missing the information. Gui Haochen 在 2023/3/3 17:12, HAO CHEN GUI via Gcc-patches 写道: > Hi, > The patch escalates the failure when Hollerith constant to real conversion > fails in native_interpret_expr. It finally

[Bug debug/108996] Proposal for adding DWARF call site information in GCC with -O0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108996 --- Comment #3 from Jakub Jelinek --- What is done on other arches? I mean the situation is basically the same on x86_64, where the artificial return value pointer argument is spilled early, then clobbered on calls and again b debug info is

Re: [PATCHv2, gfortran] Escalate failure when Hollerith constant to real conversion fails [PR103628]

Hi Tobias, 在 2023/3/3 17:29, Tobias Burnus 写道: > But could you also include the 'gcc/fortran/intrinsic.cc' change > proposed in > https://gcc.gnu.org/pipermail/gcc-patches/2023-March/613030.html (and > acknowledged by Steve)? Sure, I will merge it into the patch and do the regression test.

[Bug middle-end/108990] Too restrictive precision check in fold and simplify pattern for PR70920

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108990 --- Comment #2 from Richard Biener --- Consolidating these kind of duplicates would be nice. Note in this particular case we should order the more specific pattern earlier (diagnosing that with -v would be nice). Implementing order preserving

[Bug libquadmath/94756] strtoflt128 assigns some subnormals incorrectly on MS Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94756 --- Comment #14 from niXman --- (In reply to Jakub Jelinek from comment #13) > Fixed now on the trunk. I'd wait a little bit with backports, though I > think the gmp-param.h change doesn't need backporting. Thank you Jakub!

Re: [PATCH] [arm] complete vmsr/vmrs blank and case adjustments

On Feb 20, 2023, Andrea Corallo via Gcc-patches wrote: > Alexandre Oliva writes: >> Back in September last year, some of the vmsr and vmrs patterns had an >> extraneous blank removed, and the case of register names lowered, but >> another instance remained, and so did a few testcases. > I'm

Re: [PATCH] [PR51534] [arm] split out pr51534 test for softfp

On Feb 17, 2023, Alexandre Oliva wrote: > PR target/51534 > * gcc.target/arm/pr51534.c: Split softfp variant into... > * gcc.target/arm/pr51534s.c: ... this, and support ARM too. Ping? https://gcc.gnu.org/pipermail/gcc-patches/2023-February/612189.html -- Alexandre Oliva,

RE: [PATCH] [PR51534] [arm] split out pr51534 test for softfp

> -Original Message- > From: Alexandre Oliva > Sent: Friday, February 17, 2023 7:14 AM > To: gcc-patches@gcc.gnu.org > Cc: ni...@redhat.com; Richard Earnshaw > Subject: [PATCH] [PR51534] [arm] split out pr51534 test for softfp > > > The test uses arm_hard_ok and arm_softfp_ok as if

RE: [PATCH] [arm] adjust expectations for armv8_2-fp16-move-[12].c

> -Original Message- > From: Alexandre Oliva > Sent: Friday, February 17, 2023 7:12 AM > To: gcc-patches@gcc.gnu.org > Cc: ni...@redhat.com; Richard Earnshaw > Subject: [PATCH] [arm] adjust expectations for armv8_2-fp16-move-[12].c > > > Commit

[Bug tree-optimization/109002] [13 Regression] -O1 -ftree-pre -ftree-partial-pre results in stall value

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109002 Richard Biener changed: What|Removed |Added Summary|-O1 -ftree-pre |[13 Regression] -O1

[Bug tree-optimization/108988] gimple_fold_builtin_fputs doesn't preserve gimple_builtin_call_types_compatible_p

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108988 Jakub Jelinek changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug c/108989] Two small almost identical programs give different results

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108989 --- Comment #2 from Dave Allerton --- Apologies - should have spotted it but thanks for sorting it out. Best regards Dave Allerton On 02/03/2023 13:32,

[Bug libffi/108682] libffi needs to merge upstream to get LoongArch support

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108682 --- Comment #3 from Andreas Schwab --- libgo/goarch.sh is missing LoongArch support.

[PATCH 2/2] LoongArch: testsuite: Adjust stack offsets in stack-check-cfa tests

Once upon the time we used to save two registers unnecessarily, costing 16 bytes. Now the issue seems fixed (not sure by which commit though), adjust the stack offsets to reflex the change. gcc/testsuite/ChangeLog: * gcc.target/loongarch/stack-check-cfa-1.c (dg-final): Adjust

[PATCH 0/2] LoongArch: testsuite: Fix tests related to stack

Some trivial test case fixes. Ok for trunk? Xi Ruoyao (2): LoongArch: testsuite: Disable stack protector for some tests LoongArch: testsuite: Adjust stack offsets in stack-check-cfa tests gcc/testsuite/gcc.target/loongarch/prolog-opt.c| 2 +-

[PATCH 1/2] LoongArch: testsuite: Disable stack protector for some tests

Stack protector will affect stack layout and break the expectation of these tests, causing test failures if GCC is configured with --enable-default-ssp. gcc/testsuite/ChangeLog: * gcc.target/loongarch/prolog-opt.c (dg-options): Add -fno-stack-protector. *

RE: [PATCH] [arm] complete vmsr/vmrs blank and case adjustments

> -Original Message- > From: Alexandre Oliva > Sent: Friday, February 17, 2023 7:36 AM > To: gcc-patches@gcc.gnu.org > Cc: ni...@redhat.com; Richard Earnshaw ; > ramana@gmail.com; Kyrylo Tkachov ; > Andrea Corallo > Subject: [PATCH] [arm] complete vmsr/vmrs blank and case

Re: [PATCH] gimple-fold: Fix up fputs -> fwrite folding [PR108988]

On Fri, 3 Mar 2023, Jakub Jelinek wrote: > Hi! > > gimple_fold_builtin_fputs when folding fputs into fwrite emits the third > argument (INTEGER_CST) with incorrect type - get_maxval_strlen or c_strlen > return ssizetype, while fwrite argument is size_type_node. > The following patch fixes that,

[PATCH] tree-optimization/109002 - partial PRE miscompilation

Partial PRE ends up miscompiling the testcase in PR109002, likely involving a corner case when inifinite loops are involved. The following avoids the miscompilation by addressing a long-standing oddity that manifests in odd partial partial redundancies eliminated that are full redundancies. The

[Bug tree-optimization/109002] [13 Regression] -O1 -ftree-pre -ftree-partial-pre results in stall value

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109002 --- Comment #6 from CVS Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:0132acc03cada2c3b47c48a205e821563153fc80 commit r13-6443-g0132acc03cada2c3b47c48a205e821563153fc80 Author: Richard Biener Date:

Re: [PATCH] -Wdangling-pointer: don't mark SSA lhs sets as stores

On Fri, Mar 3, 2023 at 9:30 AM Alexandre Oliva wrote: > > On Feb 17, 2023, Richard Biener wrote: > > >> * gimple-ssa-warn-access.cc > >> (pass_waccess::check_dangling_stores): Skip non-stores. > >> > >> for gcc/testsuite/ChangeLog > >> > >> * g++.dg/warn/Wdangling-pointer.C

[Bug middle-end/109006] New: [13 Regression] Python Exception : There is no member or method named m_vecdata. since r13-6332

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109006 Bug ID: 109006 Summary: [13 Regression] Python Exception : There is no member or method named m_vecdata. since r13-6332 Product: gcc Version: 13.0

[Bug ada/109005] New: [13 Regression] ICE during GIMPLE pass: ifcvt

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109005 Bug ID: 109005 Summary: [13 Regression] ICE during GIMPLE pass: ifcvt Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug middle-end/109006] [13 Regression] Python Exception : There is no member or method named m_vecdata. since r13-6332

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

[Bug target/109007] New: building for POWER8 leaks into POWER9 ISA with g++ 11.3 (cross-compiler on x86_64 host)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109007 Bug ID: 109007 Summary: building for POWER8 leaks into POWER9 ISA with g++ 11.3 (cross-compiler on x86_64 host) Product: gcc Version: 11.3.0 Status: UNCONFIRMED

[Bug tree-optimization/109008] [13 Regression] Maybe wrong code in scipy package since r13-3926-gd4c2f1d376da6f

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109008 Richard Biener changed: What|Removed |Added Target||x86_64-linux-gnu Target

[Bug tree-optimization/109008] [13 Regression] Wrong code in scipy package since r13-3926-gd4c2f1d376da6f

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109008 --- Comment #2 from Richard Biener --- So it boils down to us optimizing d = 1. + eps; if (d == 1.) return eps; to return 0. which is of course wrong. double eps_or_zero (double eps) { double d = 1. + eps; if (d == 1.) return

[Bug tree-optimization/109008] [13 Regression] Wrong code in scipy package since r13-3926-gd4c2f1d376da6f

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109008 --- Comment #3 from Richard Biener --- So with [1., 1.] = [1., 1.] + op2 we are calculating op2 = [1., 1.] - [1., 1.] but with FP math we cannot apply such simplification without considering rounding or exponent ranges. Maybe it's enough to

[Bug target/109004] [10/11/12/13 Regression] wrong code for -O2 (any above -O0) with g++ 11.3 for POWER9 (cross-compiler on x86_64 host)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109004 Richard Biener changed: What|Removed |Added Known to work||9.5.0 Summary|wrong code

[Bug ada/109005] [13 Regression] ICE during GIMPLE pass: ifcvt

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109005 Richard Biener changed: What|Removed |Added CC||avieira at gcc dot gnu.org ---

[Bug debug/108996] Proposal for adding DWARF call site information in GCC with -O0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108996 --- Comment #4 from Ulrich Weigand --- (In reply to Jakub Jelinek from comment #3) > What is done on other arches? That depends on the platform ABI. On some arches, including x86/x86_64 and arm/aarch64, the ABI requires the generated code

[Bug tree-optimization/109008] [13 Regression] Wrong code in scipy package since r13-3926-gd4c2f1d376da6f

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109008 --- Comment #9 from Richard Biener --- (In reply to Richard Biener from comment #8) > We basically have to consider an input range [a, b] as [a - x, b + y] > with the largest positive x and y so that correctly rounding the value > yields a and

[Bug tree-optimization/109002] [13 Regression] -O1 -ftree-pre -ftree-partial-pre results in stall value

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109002 Richard Biener changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug tree-optimization/109008] New: [13 Regression ]Maybe wrong code in scipy package since r13-3926-gd4c2f1d376da6f

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109008 Bug ID: 109008 Summary: [13 Regression ]Maybe wrong code in scipy package since r13-3926-gd4c2f1d376da6f Product: gcc Version: 13.0 Status: UNCONFIRMED

[Bug tree-optimization/109008] [13 Regression] Maybe wrong code in scipy package since r13-3926-gd4c2f1d376da6f

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

[Bug tree-optimization/109008] [13 Regression] Wrong code in scipy package since r13-3926-gd4c2f1d376da6f

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109008 --- Comment #4 from Richard Biener --- The "easiest" way would be if the range endpoints would have one bit more of mantissa and so we can represent all endpoints with one ulp off (aka nextafter/nextbefore). So constants would always become

[Bug ada/109005] [13 Regression] ICE during GIMPLE pass: ifcvt

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109005 --- Comment #4 from simon at pushface dot org --- (In reply to Richard Biener from comment #3) > Eh, I'm hoping for a C testcase ... what's the actual ICE? This is an LLDB session -- hope that helps $ lldb

[Bug libgcc/108727] gcc.dg/split-5.c fails on power 9 BE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108727 --- Comment #3 from Alan Modra --- Yes, looks good to me.

[Bug tree-optimization/109008] [13 Regression] Wrong code in scipy package since r13-3926-gd4c2f1d376da6f

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109008 --- Comment #10 from Jakub Jelinek --- So, can't we say compute what we compute right now for the reverse operation and then call some helper function which will try to extended that range a little bit in both directions by performing

Re: [PATCH] testsuite: Do not expect partial vectorization for s390.

On Thu, Mar 2, 2023 at 7:24 PM Robin Dapp via Gcc-patches wrote: > > Hi, > > this patch changes SLP test expectations. As we only vectorize when no > more than one rgroup is present, no vectorization is performed. > > I was also considering using a separate target selector (something like >

Re: [PATCH] driver: toplev: Fix a typo

On Fri, Mar 3, 2023 at 9:58 AM Xi Ruoyao via Gcc-patches wrote: > > On Fri, 2023-03-03 at 16:54 +0800, Xi Ruoyao wrote: > > The driver emits a warning when -fstack-check and > > -fstack-clash-protection are used together, but the message refers to > > "-fstack-clash_protection" (underline instead

[Bug driver/71850] @file should be used to cc1/cc1plus when @file is used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71850 --- Comment #7 from Costas Argyris --- Created attachment 54575 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54575=edit Treat include path args the same way between cpp_unique_options and asm_options The proposed patch extends the logic

[Bug ada/109005] [13 Regression] ICE during GIMPLE pass: ifcvt

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109005 --- Comment #1 from simon at pushface dot org --- Created attachment 54576 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54576=edit Reproducer

[Bug middle-end/109006] [13 Regression] Python Exception : There is no member or method named m_vecdata. since r13-6332

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109006 --- Comment #1 from Jakub Jelinek --- As for the non-*.py comments, perhaps: 2023-03-03 Jakub Jelinek PR middle-end/109006 * vec.cc (test_auto_alias): Adjust comment for removal of m_vecdata. *

[Bug tree-optimization/109008] [13 Regression] Wrong code in scipy package since r13-3926-gd4c2f1d376da6f

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109008 --- Comment #7 from Richard Biener --- (In reply to Jakub Jelinek from comment #6) > Note, the ulps frange_arithmetic are ulps of the result, result is in this > case 0.0, > so 1ulp is the smallest subnormal number. > That is something

Re: [PATCH] swap: Fix incorrect lane extraction by vec_extract() [PR106770]

On 27/02/23 9:58 pm, Segher Boessenkool wrote: > Hi! > > On Wed, Jan 04, 2023 at 01:58:19PM +0530, Surya Kumari Jangala wrote: >> In the routine rs6000_analyze_swaps(), special handling of swappable >> instructions is done even if the webs that contain the swappable >> instructions are not

Re: [PATCH] waccess: Fix two -Wnonnull warning issues [PR108986]

On Fri, 3 Mar 2023, Jakub Jelinek wrote: > Hi! > > The following patch fixes 2 issues with the -Wnonnull warning. > > One, fixed by the second hunk, is that the warning wording is bogus > since r11-3305, instead of printing > warning: argument 1 to ‘int[static 7]’ is null where non-null

Re: [PATCH] libiberty: fix memory leak in pex-win32.c and refactor

On Thu, Mar 2, 2023 at 3:02 PM Costas Argyris wrote: > > Thanks for the review. > > What is the next step please? Somebody pushed the patch already. Richard. > Thanks, > Costas > > On Thu, 2 Mar 2023 at 10:08, Richard Biener > wrote: >> >> On Thu, Mar 2, 2023 at 10:21 AM Costas Argyris >>

[Bug ada/109005] [13 Regression] ICE during GIMPLE pass: ifcvt

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109005 simon at pushface dot org changed: What|Removed |Added Target||x86_64-apple-darwin

[Bug tree-optimization/109008] [13 Regression] Wrong code in scipy package since r13-3926-gd4c2f1d376da6f

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109008 --- Comment #5 from Jakub Jelinek --- Well, we already do that half ulp fuzzing in frange_arithmetic. The thing is that for forward [1., 1.] - [1., -1.] it is really correctly [0., 0.], the subtraction is exact in that case. It is just the

[Bug ada/109005] [13 Regression] ICE during GIMPLE pass: ifcvt

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109005 Richard Biener changed: What|Removed |Added Target Milestone|--- |13.0 Keywords|

Re: [PATCH] apply debug-remap to file names in .su files

On 13/02/2023 20.27, Rasmus Villemoes wrote: > The .su files generated with -fstack-usage are arguably debug info. In > order to make builds more reproducible, apply the same remapping logic > to the recorded file names as for when producing the debug info > embedded in the object files. > > To

[Bug tree-optimization/109008] [13 Regression] Wrong code in scipy package since r13-3926-gd4c2f1d376da6f

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109008 --- Comment #6 from Jakub Jelinek --- Note, the ulps frange_arithmetic are ulps of the result, result is in this case 0.0, so 1ulp is the smallest subnormal number. That is something completely different from what we need here though for the

Re: [PATCHv2, gfortran] Escalate failure when Hollerith constant to real conversion fails [PR103628]

Hi Haochen, On 03.03.23 10:56, HAO CHEN GUI via Gcc-patches wrote: Sure, I will merge it into the patch and do the regression test. Thanks :-) Additionally, Kewen suggested: Since this test case is powerpc only, I think it can be moved to

[Bug tree-optimization/109008] [13 Regression] Wrong code in scipy package since r13-3926-gd4c2f1d376da6f

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109008 --- Comment #8 from Richard Biener --- We basically have to consider an input range [a, b] as [a - x, b + y] with the largest positive x and y so that correctly rounding the value yields a and b again.

[Bug tree-optimization/109008] [13 Regression] Wrong code in scipy package since r13-3926-gd4c2f1d376da6f

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109008 --- Comment #11 from Richard Biener --- I think for the reverse op I'd naiively try to compute the result as we do now and then extend the range by one ulp of the input range with the largest magnitude. Does real_nextafter (0.0) result in a

[Bug debug/108996] Proposal for adding DWARF call site information in GCC with -O0

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

Re: [PATCH] diagnostics: Fix up selftests with $COLUMNS < 42 [PR108973]

On Fri, 2023-03-03 at 10:35 +0100, Jakub Jelinek wrote: > Hi! > > As mentioned in the PR, GCC's diagnostics self-tests fail if $COLUMNS > < 42. > Guarding each self-test with if (get_terminal_width () > 41) or > similar > would be a maintainance nightmare (PR has a patch to do so without >

  1   2   3   >