[Bug tree-optimization/109154] [13/14 regression] jump threading de-optimizes nested floating point comparisons

2023-07-07 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109154 --- Comment #59 from Tamar Christina --- I've sent two patches upstream this morning to fix the remaining ifcvt issues: https://gcc.gnu.org/pipermail/gcc-patches/2023-July/623848.html

[Bug bootstrap/54179] please split insn-emit.c !

2023-07-07 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179 --- Comment #33 from Tamar Christina --- (In reply to Sam James from comment #32) > I'll tentatively reopen as IIRC tamar mentioned they've had some ideas about > this, apologies if I'm misremembering. Hello, yes I have a patch locally that I

[Bug ada/110336] New: Ada doesn't build with coverage enabled on Arm

2023-06-21 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110336 Bug ID: 110336 Summary: Ada doesn't build with coverage enabled on Arm Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: build Severity: normal

[Bug other/110329] [14 regression] build fails building documentation after r14-1949-g957ae904065917

2023-06-21 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110329 Tamar Christina changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug bootstrap/110324] [14 Regression][build][nvptx] build/genpreds: Internal error: RTL check: expected elt 2 type 'T', have 's' due to r14-1949-g957ae904065917

2023-06-20 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110324 Tamar Christina changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug tree-optimization/110223] New: Missed optimization vectorizing booleans comparisons

2023-06-12 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110223 Bug ID: 110223 Summary: Missed optimization vectorizing booleans comparisons Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: missed-optimization Severity:

[Bug middle-end/110142] [14 Regression] x264 from SPECCPU 2017 miscompares from g:2f482a07365d9f4a94a56edd13b7f01b8f78b5a0

2023-06-07 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110142 --- Comment #2 from Tamar Christina --- Thank you!

[Bug middle-end/110142] New: [14 Regression] x264 from SPECCPU 2017 miscompares from g:2f482a07365d9f4a94a56edd13b7f01b8f78b5a0

2023-06-06 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110142 Bug ID: 110142 Summary: [14 Regression] x264 from SPECCPU 2017 miscompares from g:2f482a07365d9f4a94a56edd13b7f01b8f78b5a0 Product: gcc Version: 14.0 Status:

[Bug rtl-optimization/109940] [13 Regression] ICE in decide_candidate_validity since g:53dddbfeb213ac4ec39f550aa81eaa4264375d2c

2023-05-23 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109940 Tamar Christina changed: What|Removed |Added Known to work|13.1.0 | CC|

[Bug ipa/109711] [14 regression] ICE (tree check: expected class ‘type’, have ‘exceptional’ (error_mark) in verify_range, at value-range.cc:1060) when building ffmpeg-4.4.4 since r14-377-gc92b8be9b52b

2023-05-03 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109711 --- Comment #6 from Tamar Christina --- my own bisect does indeed end up at r14-377-gc92b8be9b52b7e and cannot reproduce it on GCC 13.

[Bug ipa/109711] [14 regression] ICE (tree check: expected class ‘type’, have ‘exceptional’ (error_mark) in verify_range, at value-range.cc:1060) when building ffmpeg-4.4.4 since r14-377-gc92b8be9b52b

2023-05-03 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109711 --- Comment #5 from Tamar Christina --- (In reply to Martin Liška from comment #3) > Hm, on x86_64-linux-gnu, it started with r13-6616-g2246d576f922ba. $ cat prtest2.c void lspf2lpc(); int interpolate_lpc_q_0; void interpolate_lpc(int

[Bug target/109632] Inefficient codegen when complex numbers are emulated with structs

2023-04-27 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109632 --- Comment #9 from Tamar Christina --- Thank you!

[Bug target/109632] Inefficient codegen when complex numbers are emulated with structs

2023-04-27 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109632 --- Comment #6 from Tamar Christina --- That's an interesting approach, I think it would also fix https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109391 would it not? Since the int16x8x3_t return would be "scalarized" avoiding the bad expansion?

[Bug target/109632] Inefficient codegen when complex numbers are emulated with structs

2023-04-26 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109632 --- Comment #3 from Tamar Christina --- note that even if we can't stop SLP, we should be able to generate as efficient code by being creative about the instruction selection, that's why I marked it as a target bug :)

[Bug target/109632] Inefficient codegen when complex numbers are emulated with structs

2023-04-26 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109632 --- Comment #2 from Tamar Christina --- (In reply to Richard Biener from comment #1) > Well, the usual unknown ABI boundary at function entry/exit. Yes but LLVM gets it right, so should be a solve able computer science problem. :) Note that

[Bug target/109632] New: Inefficient codegen when complex numbers are emulated with structs

2023-04-26 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109632 Bug ID: 109632 Summary: Inefficient codegen when complex numbers are emulated with structs Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords:

[Bug tree-optimization/109154] [13/14 regression] jump threading de-optimizes nested floating point comparisons

2023-04-26 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109154 Tamar Christina changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |tnfchris at gcc dot gnu.org

[Bug tree-optimization/109154] [13/14 regression] jump threading de-optimizes nested floating point comparisons

2023-04-25 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109154 --- Comment #54 from Tamar Christina --- @Jakub, just to check to avoid doing duplicate work, did you intend to do the remaining ifcvt changes or should we?

[Bug tree-optimization/109587] Deeply nested loop unrolling overwhelms register allocator with -O3

2023-04-24 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109587 --- Comment #7 from Tamar Christina --- (In reply to Richard Biener from comment #5) > (In reply to Tamar Christina from comment #4) > > (In reply to Richard Biener from comment #3) > > > The issue isn't unrolling but invariant motion. We

[Bug tree-optimization/109587] Deeply nested loop unrolling overwhelms register allocator with -O3

2023-04-24 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109587 --- Comment #4 from Tamar Christina --- (In reply to Richard Biener from comment #3) > The issue isn't unrolling but invariant motion. We unroll the innermost > loop, vectorizer the middle loop and then unroll that as well. That leaves > us

[Bug tree-optimization/109587] New: Deeply nested loop unrolling overwhelms register allocator

2023-04-21 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109587 Bug ID: 109587 Summary: Deeply nested loop unrolling overwhelms register allocator Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords:

[Bug tree-optimization/109154] [13 regression] jump threading de-optimizes nested floating point comparisons

2023-04-05 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109154 --- Comment #42 from Tamar Christina --- Thanks for all the work so far folks! Just to clarify the current state, it looks like the first reduced testcase is now correct. But the larger example as in c26 is still suboptimal, but slightly

[Bug rtl-optimization/109391] New: Inefficient codegen on AArch64 when structure types are returned

2023-04-03 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109391 Bug ID: 109391 Summary: Inefficient codegen on AArch64 when structure types are returned Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords:

[Bug tree-optimization/109154] [13 regression] jump threading de-optimizes nested floating point comparisons

2023-03-28 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109154 --- Comment #25 from Tamar Christina --- Created attachment 54777 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54777=edit extracted codegen

[Bug tree-optimization/109154] [13 regression] jump threading de-optimizes nested floating point comparisons

2023-03-28 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109154 --- Comment #24 from Tamar Christina --- (In reply to Jakub Jelinek from comment #12) > (In reply to Richard Biener from comment #11) > > _1 shoud be [-Inf, nextafter (0.0, -Inf)], not [-Inf, -0.0] > The reduced testcase is invalid because it

[Bug tree-optimization/109230] [13 Regression] Maybe wrong code for opus package on aarch64 since r13-4122-g1bc7efa948f751

2023-03-21 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109230 --- Comment #11 from Tamar Christina --- Neither of those vec_perms are valid targets for this optimization. It looks like sel.series_p is not doing what I expected. It's matching even elements and ignoring the odd ones.

[Bug tree-optimization/109230] [13 Regression] Maybe wrong code for opus package on aarch64 since r13-4122-g1bc7efa948f751

2023-03-21 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109230 --- Comment #1 from Tamar Christina --- That patch only fixed the bootstrap, in any case I'm on holidays so have asked someone else to look.

[Bug target/109154] [13 regression] jump threading with de-optimizes nested floating point comparisons

2023-03-16 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109154 Tamar Christina changed: What|Removed |Added Summary|[13 regression] aarch64 |[13 regression] jump

[Bug target/109154] [13 regression] aarch64 -mcpu=neoverse-v1 microbude performance regression

2023-03-16 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109154 --- Comment #2 from Tamar Christina --- Confirmed, It looks like the extra range information from g:4fbe3e6aa74dae5c75a73c46ae6683fdecd1a75d is leading jump threading down the wrong path. Reduced testcase: --- int etot_0,

[Bug tree-optimization/109156] Support Absolute Difference detection in GCC

2023-03-16 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109156 Tamar Christina changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |tnfchris at gcc dot gnu.org

[Bug tree-optimization/109156] Support Absolute Difference detection in GCC

2023-03-16 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109156 --- Comment #2 from Tamar Christina --- (In reply to Richard Biener from comment #1) > (In reply to Tamar Christina from comment #0) > > 2. It looks like all targets that implement SAD do so with an instruction > > that does ABD and then

[Bug tree-optimization/109154] [13 regression] aarch64 -mcpu=neoverse-v1 microbude performance regression

2023-03-16 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109154 --- Comment #1 from Tamar Christina --- Thanks for the report, taking a look!

[Bug tree-optimization/109156] New: Support Absolute Difference detection in GCC

2023-03-16 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109156 Bug ID: 109156 Summary: Support Absolute Difference detection in GCC Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal

[Bug middle-end/109153] missed vector constructor optimizations

2023-03-16 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109153 Tamar Christina changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |tnfchris at gcc dot gnu.org

[Bug middle-end/109153] missed vector constructor optimizations

2023-03-16 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109153 --- Comment #3 from Tamar Christina --- (In reply to Richard Biener from comment #2) > On the GIMPLE side we should canonicalize here I think, at which point > inserts into a splatted vector become more profitable depends? > > _4 =

[Bug middle-end/109153] New: missed vector constructor optimizations

2023-03-16 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109153 Bug ID: 109153 Summary: missed vector constructor optimizations Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal

[Bug target/109130] 464.h264ref regressed by 6.5% on a Neoverse-N1 CPU with PGO, LTO, -Ofast and -march=native

2023-03-15 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109130 --- Comment #1 from Tamar Christina --- I can't reproduce that. on a Neoverse-N1 I see between those two commits: ./bench-compare.sh 2fc55f51f99 bad177e8487 A 1457 files D 0 files M 0 files Extracted

[Bug testsuite/109118] gcc.dg/mla_1.c failed on target w/o __Uint32x4_t support

2023-03-14 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109118 Tamar Christina changed: What|Removed |Added Resolution|--- |FIXED CC|

[Bug target/108583] [13 Regression] wrong code with vector division by uint16 at -O2

2023-03-12 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108583 Tamar Christina changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug target/109072] [12/13 Regression] SLP costs for vec duplicate too high since g:4963079769c99c4073adfd799885410ad484cbbe

2023-03-09 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109072 --- Comment #4 from Tamar Christina --- (In reply to rsand...@gcc.gnu.org from comment #3) > (In reply to Tamar Christina from comment #2) > > I thought the SLP algorithm was bottom up and stores were > > already sinks? > Yeah, they are. But

[Bug target/109072] [12/13 Regression] SLP costs for vec duplicate too high since g:4963079769c99c4073adfd799885410ad484cbbe

2023-03-09 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109072 --- Comment #2 from Tamar Christina --- (In reply to rsand...@gcc.gnu.org from comment #1) > (In reply to Tamar Christina from comment #0) > > The SLP costs went from: > > > > Vector cost: 2 > > Scalar cost: 4 > > > > to: > > > >

[Bug target/109072] New: [12/13 Regression] SLP costs for vec duplicate too high since g:4963079769c99c4073adfd799885410ad484cbbe

2023-03-08 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109072 Bug ID: 109072 Summary: [12/13 Regression] SLP costs for vec duplicate too high since g:4963079769c99c4073adfd799885410ad484cbbe Product: gcc Version: 12.0 Status:

[Bug rtl-optimization/106594] [13 Regression] sign-extensions no longer merged into addressing mode

2023-03-05 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106594 --- Comment #17 from Tamar Christina --- (In reply to Segher Boessenkool from comment #13) > Hi! > > Either this should not be P1, or the proposed patch is taking completely the > wrong direction. P1 means there is a regression. There is no

[Bug rtl-optimization/106594] [13 Regression] sign-extensions no longer merged into addressing mode

2023-02-27 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106594 Tamar Christina changed: What|Removed |Added CC||rsandifo at gcc dot gnu.org,

[Bug target/108583] [13 Regression] wrong code with vector division by uint16 at -O2

2023-02-08 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108583 --- Comment #24 from Tamar Christina --- > Sure that works I think, I'll do that then. Just to check, I'm regtesting the patch, I assume you want me to revert the hook as well right? Since nothing will be using it.

[Bug target/108583] [13 Regression] wrong code with vector division by uint16 at -O2

2023-02-02 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108583 --- Comment #23 from Tamar Christina --- (In reply to rguent...@suse.de from comment #22) > On Thu, 2 Feb 2023, tnfchris at gcc dot gnu.org wrote: > > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108583 > > > > --- Comment #21 from Tamar

[Bug target/108583] [13 Regression] wrong code with vector division by uint16 at -O2

2023-02-02 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108583 --- Comment #21 from Tamar Christina --- > > OK, so that's an ADD_HIGHPART_EXPR then? Though the highpart of an > add is only a single bit, isn't it? For scalar you'd use the > carry bit here and instructions like adc to consume it. Is

[Bug target/108583] [13 Regression] wrong code with vector division by uint16 at -O2

2023-02-01 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108583 --- Comment #20 from Tamar Christina --- > > I don't think so for addhn, because it wouldn't truncate the top bits, it > > truncates the bottom bits. > > > > The instruction does > > element1 = Elem[operand1, e, 2*esize]; > > element2

[Bug tree-optimization/108601] [13 Regression] vector peeling ICEs with VLA in gcc_r in SPEC2017 since g:c13223b790bbc5e4a3f5605e057eac59b61b2c85

2023-01-31 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108601 --- Comment #8 from Tamar Christina --- In case it helps, here's the reproducer on compiler explorer and the dump file https://godbolt.org/z/dWvqexjnv

[Bug tree-optimization/108601] [13 Regression] vector peeling ICEs with VLA in gcc_r in SPEC2017 since g:c13223b790bbc5e4a3f5605e057eac59b61b2c85

2023-01-31 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108601 Tamar Christina changed: What|Removed |Added Target||aarch64* Summary|[13

[Bug target/108583] [13 Regression] wrong code with vector division by uint16 at -O2

2023-01-31 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108583 --- Comment #18 from Tamar Christina --- > > > > Ack, that also tracks with what I tried before, we don't indeed track ranges > > for vector ops. The general case can still be handled slightly better (I > > think) > > but it doesn't become as

[Bug target/108583] [13 Regression] wrong code with vector division by uint16 at -O2

2023-01-31 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108583 --- Comment #15 from Tamar Christina --- > OK, hopefully I understand now. Sorry for being slow. Not at all, Sorry if it came across a bit cranky, it wasn't meant that way! > If that's the condition we want to test for, it seems like

[Bug target/108583] [13 Regression] wrong code with vector division by uint16 at -O2

2023-01-31 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108583 --- Comment #12 from Tamar Christina --- (In reply to rguent...@suse.de from comment #11) > On Tue, 31 Jan 2023, tnfchris at gcc dot gnu.org wrote: > > > I don't think passing in for example the tree operand 0 helps, the > target appearantly

[Bug target/108583] [13 Regression] wrong code with vector division by uint16 at -O2

2023-01-31 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108583 --- Comment #10 from Tamar Christina --- (In reply to rsand...@gcc.gnu.org from comment #9) > Are we sure this is a vectoriser vs. C vectors thing? it's not, the issue we're debating is how to fix it. As Richi pointed out

[Bug tree-optimization/108601] [13 Regression] vector peeling ICEs with PGO + LTO + IPA inlining in gcc_r in SPEC2017

2023-01-31 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108601 --- Comment #6 from Tamar Christina --- probably relevant that I can only reproduce it on an SVE/VLA system. non-VLA works fine. I have cvise running trying for a repro.

[Bug target/108583] [13 Regression] wrong code with vector division by uint16 at -O2

2023-01-30 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108583 --- Comment #7 from Tamar Christina --- (In reply to rsand...@gcc.gnu.org from comment #6) > (In reply to Tamar Christina from comment #3) > > The vectorizer has this context but since we didn't want a new IFN the > > context should instead be

[Bug tree-optimization/108601] New: [13 Regression] vector peeling ICEs with PGO + LTO + IPA inlining in gcc_r in SPEC2017

2023-01-30 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108601 Bug ID: 108601 Summary: [13 Regression] vector peeling ICEs with PGO + LTO + IPA inlining in gcc_r in SPEC2017 Product: gcc Version: 13.0 Status: UNCONFIRMED

[Bug target/108583] [13 Regression] wrong code with vector division by uint16 at -O2

2023-01-30 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108583 --- Comment #5 from Tamar Christina --- > > The vectorizer has this context but since we didn't want a new IFN the > > context should instead be derivable in > > targetm.vectorize.can_special_div_by_const hook. > > The vectorizer doesn't

[Bug target/108583] [13 Regression] wrong code with vector division by uint16 at -O2

2023-01-30 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108583 Tamar Christina changed: What|Removed |Added CC||rguenth at gcc dot gnu.org,

[Bug testsuite/108394] aarch64/cpunative/native_cpu_18.c fails in GCC 11 and 12

2023-01-27 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108394 Tamar Christina changed: What|Removed |Added CC||tnfchris at gcc dot gnu.org ---

[Bug ipa/107925] ICE in update_specialized_profile at gcc/ipa-cp.cc:5082 for 531.deepsjeng_r benchmark

2023-01-27 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107925 --- Comment #5 from Tamar Christina --- I seem to have the same failure in at least GCC 12 as well.

[Bug driver/97574] Allow for nul output with Windows

2023-01-18 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97574 Tamar Christina changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug target/108172] [13 Regression] ICE in emit_move_multi_word, at expr.cc:4087 since r13-4616-g2cba118e538ba0

2023-01-06 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108172 Tamar Christina changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug target/108172] [13 Regression] ICE in emit_move_multi_word, at expr.cc:4087 since r13-4616-g2cba118e538ba0

2023-01-06 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108172 Tamar Christina changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |tnfchris at gcc dot gnu.org

[Bug target/102218] 128-bit atomic compare and exchange does not honor memory model on AArch64 and Arm

2022-12-21 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102218 --- Comment #4 from Tamar Christina --- (In reply to ktkachov from comment #3) > Does this need to be backported to other release versions as it's a > wrong-code bug? Yes Ideally. I did ask for backport but was only approved for master.

[Bug target/107988] [13 Regression] ICE: in extract_insn, at recog.cc:2791 (unrecognizable insn) on aarch64-unknown-linux-gnu

2022-12-14 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107988 Tamar Christina changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug rtl-optimization/108070] failure to combine range test to bit test

2022-12-12 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108070 --- Comment #2 from Tamar Christina --- Committed, implementing the tbranch optab should allow this to be fixed.

[Bug rtl-optimization/108070] failure to combine range test to bit test

2022-12-12 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108070 --- Comment #1 from Tamar Christina --- Yes it's all been approved now, doing a regression after a rebase and will commit today.

[Bug target/107988] [13 Regression] ICE: in extract_insn, at recog.cc:2791 (unrecognizable insn) on aarch64-unknown-linux-gnu

2022-12-06 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107988 Tamar Christina changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |tnfchris at gcc dot gnu.org

[Bug target/107830] [13 Regression] ICE in gen_aarch64_bitmask_udiv3, at ./insn-opinit.h:813

2022-11-25 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107830 Tamar Christina changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug target/107830] [13 Regression] ICE in gen_aarch64_bitmask_udiv3, at ./insn-opinit.h:813

2022-11-23 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107830 Tamar Christina changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #3 from Tamar

[Bug libgcc/107675] [13 Regression] GCC-13 is significantly slower to startup on C++ programs

2022-11-22 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107675 Thomas Neumann changed: What|Removed |Added CC||tneumann at users dot sourceforge.

[Bug tree-optimization/107647] [12 Regression] GCC 12.2.0 may produce FMAs even with -ffp-contract=off

2022-11-21 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107647 --- Comment #19 from Tamar Christina --- FWIW, the testsuite on AArch64 was clean after the patch.

[Bug libgcc/107675] [13 Regression] GCC-13 is significantly slower to startup on C++ programs

2022-11-20 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107675 Tamar Christina changed: What|Removed |Added Component|libstdc++ |libgcc --- Comment #11 from Tamar

[Bug libstdc++/107675] [13 Regression] GCC-13 is significantly slower to startup on C++ programs

2022-11-20 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107675 --- Comment #10 from Tamar Christina --- I've bisected this to: commit 6e80a1d164d1f996ad08a512c25a7c2ca893 Author: Thomas Neumann Date: Tue Mar 1 21:57:35 2022 +0100 eliminate mutex in fast path of __register_frame The

[Bug libstdc++/107675] [13 Regression] GCC-13 is significantly slower to startup on C++ programs

2022-11-17 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107675 --- Comment #9 from Tamar Christina --- (In reply to Florian Weimer from comment #8) > (In reply to Tamar Christina from comment #4) > > /opt/buildAgent/work/5c94c4ced6ebfcd0/libgcc/unwind-dw2-fde.c:111 > > #6 __register_frame_info (begin=,

[Bug libstdc++/107675] [13 Regression] GCC-13 is significantly slower to startup on C++ programs

2022-11-17 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107675 --- Comment #7 from Tamar Christina --- (In reply to Andrew Pinski from comment #5) > Can you try right before r13-3707-g4e4e3ffd10f53e and right afterwards? > > I would have assumed, the exception would not happen really. Sadly doesn't seem

[Bug tree-optimization/107647] [12/13 Regression] GCC 12.2.0 may produce FMAs even with -ffp-contract=off

2022-11-17 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107647 --- Comment #14 from Tamar Christina --- (In reply to Richard Biener from comment #13) > Created attachment 53917 [details] > patch I am testing > > OK, I'm testing the following then - can you see if that works for the > complex fmas and if

[Bug tree-optimization/107647] [12/13 Regression] GCC 12.2.0 may produce FMAs even with -ffp-contract=off

2022-11-17 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107647 --- Comment #12 from Tamar Christina --- Note that the same IFN is used for integer MLA as well. We didn't split them apart.

[Bug tree-optimization/107647] [12/13 Regression] GCC 12.2.0 may produce FMAs even with -ffp-contract=off

2022-11-17 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107647 --- Comment #11 from Tamar Christina --- (In reply to Richard Biener from comment #10) > Tamar, are the IFN_COMPLEX_FMA and IFN_COMPLEX_FMA_CONJ FP contracting > operations as well? Yes, they have no intermediate rounding.

[Bug tree-optimization/107717] [13 Regression] ICEs expanding permutes after g:dc95e1e9702f2f6367bbc108c8d01169be1b66d2

2022-11-17 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107717 Tamar Christina changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug tree-optimization/107717] [13 Regression] ICEs expanding permutes after g:dc95e1e9702f2f6367bbc108c8d01169be1b66d2

2022-11-16 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107717 Tamar Christina changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |tnfchris at gcc dot gnu.org

[Bug tree-optimization/107717] New: [13 Regression] ICEs expanding permutes after g:dc95e1e9702f2f6367bbc108c8d01169be1b66d2

2022-11-16 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107717 Bug ID: 107717 Summary: [13 Regression] ICEs expanding permutes after g:dc95e1e9702f2f6367bbc108c8d01169be1b66d2 Product: gcc Version: 13.0 Status: UNCONFIRMED

[Bug libstdc++/107675] [13 Regression] GCC-13 is significantly slower to startup on C++ programs

2022-11-14 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107675 --- Comment #4 from Tamar Christina --- (In reply to Jakub Jelinek from comment #2) > Does the binary and libstdc++.so have PT_GNU_EH_FRAME header including > binary search table (readelf -Wl | grep GNU_EH_FRAME)? > During startup I think there

[Bug libstdc++/107675] [13 Regression] GCC-13 is significantly slower to startup on C++ programs

2022-11-14 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107675 --- Comment #1 from Tamar Christina --- Note that to test this, the glibc version stayed the same. Also when using the default dynamically linked version, pointing to the GCC-12 libstdc++ from the GCC-13 also has no slowdown. So this seems to

[Bug libstdc++/107675] New: [13 Regression] GCC-13 is significantly slower to startup on C++ programs

2022-11-14 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107675 Bug ID: 107675 Summary: [13 Regression] GCC-13 is significantly slower to startup on C++ programs Product: gcc Version: 13.0 Status: UNCONFIRMED Severity:

[Bug middle-end/26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)

2022-11-11 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163 Bug 26163 depends on bug 89430, which changed state. Bug 89430 Summary: A missing ifcvt optimization to generate csel https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89430 What|Removed |Added

[Bug rtl-optimization/46279] cmov not hoisted out of the loop

2022-11-11 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46279 Bug 46279 depends on bug 89430, which changed state. Bug 89430 Summary: A missing ifcvt optimization to generate csel https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89430 What|Removed |Added

[Bug tree-optimization/89430] A missing ifcvt optimization to generate csel

2022-11-11 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89430 Tamar Christina changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[Bug tree-optimization/89430] A missing ifcvt optimization to generate csel

2022-11-11 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89430 --- Comment #16 from Tamar Christina --- I think this can be closed now right?

[Bug target/107102] New: SVE function fails to realize it doesn't need the frame-pointer in the tail call.

2022-09-30 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107102 Bug ID: 107102 Summary: SVE function fails to realize it doesn't need the frame-pointer in the tail call. Product: gcc Version: 13.0 Status: UNCONFIRMED

[Bug bootstrap/107059] [13 regression] bootstrap failure after r13-2887-gb04208895fed34

2022-09-28 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107059 Tamar Christina changed: What|Removed |Added CC||tnfchris at gcc dot gnu.org

[Bug libgcc/107026] [13 Regression] gcc_assert (in_shutdown || ob); build failure for i586-msdosdjgpp target

2022-09-25 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107026 Tamar Christina changed: What|Removed |Added CC||tneumann at users dot sourceforge.

[Bug libgcc/107026] [13 Regression] gcc_assert (in_shutdown || ob); build failure for i586-msdosdjgpp target

2022-09-25 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107026 Tamar Christina changed: What|Removed |Added Target|i586-msdosdjgpp |i586-msdosdjgpp, |

[Bug other/106782] dump_printf_loc has incorrect format attribute

2022-08-31 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106782 --- Comment #4 from Tamar Christina --- (In reply to Jakub Jelinek from comment #3) > Tamar, any thoughts on that? Apologies, didn't notice that earlier. That should be "Target does not support vector type for %G\n" with STMT_VINFO_STMT

[Bug target/106524] [12 Regression] ICE in extract_insn, at recog.cc:2791 (error: unrecognizable insn) since r12-4349-ge36206c9940d22.

2022-08-30 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106524 Tamar Christina changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug tree-optimization/106744] [13 Regression] phiopt miscompiles min/max since r13-1950-g9bb19e143cfe8863

2022-08-30 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106744 Tamar Christina changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug tree-optimization/106744] [13 Regression] phiopt miscompiles min/max

2022-08-26 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106744 Tamar Christina changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |tnfchris at gcc dot gnu.org

[Bug rtl-optimization/106594] [13 Regression] sign-extensions no longer merged into addressing mode

2022-08-14 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106594 --- Comment #6 from Tamar Christina --- Hi Roger, before you spend too much time on this, I just wanted to clarify. If you're saying this is a target issue where we lack some symmetry on patterns I would be happy to fix it up and don't really

[Bug tree-optimization/106594] [13 Regression] sign-extensions no longer merged into addressing mode

2022-08-12 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106594 --- Comment #4 from Tamar Christina --- Hmm my concern here is though that we've now introduced two forms to represent this and may cause an issue in other places where we sink extensions. Perhaps there should be some canonization somewhere?

<    1   2   3   4   5   6   7   8   >