[Bug target/118505] [15 regression] aarch64: 25% regression in TSVC s258 since r15-3436-gb2b20b277988ab

2025-01-29 Thread dhruvc at nvidia dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118505 --- Comment #18 from Dhruv Chawla --- (In reply to Andrew Pinski from comment #16) > So if we add: > if ((rand() & 1)) > arr[i] *= -1; > > For the initialization loop. > > And increase the 2D size from 256 to 1000 (th

[Bug tree-optimization/118505] [15 regression] aarch64: 25% regression in TSVC s258 since r15-3436-gb2b20b277988ab

2025-01-19 Thread dhruvc at nvidia dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118505 --- Comment #11 from Dhruv Chawla --- (In reply to Andrew Pinski from comment #10) > Created https://github.com/UoB-HPC/TSVC_2/issues/8 for the issue in the > benchmarking code. Let's see what they say too. I think it is unlikely to get a reply

[Bug tree-optimization/118505] [15 regression] aarch64: 25% regression in TSVC s258 since r15-3436-gb2b20b277988ab

2025-01-16 Thread dhruvc at nvidia dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118505 --- Comment #8 from Dhruv Chawla --- (In reply to Andrew Pinski from comment #7) > I do have to wonder if splitting the path here helps because the condition > (a[i] > 0.) Is predictable. > > I can't think it would be predictable but maybe on a

[Bug tree-optimization/118505] [15 regression] aarch64: 25% regression in TSVC s258 since r15-3436-gb2b20b277988ab

2025-01-16 Thread dhruvc at nvidia dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118505 --- Comment #5 from Dhruv Chawla --- (In reply to Andrew Pinski from comment #3) > Note there is also a fma forming missing: > _69 = s_64 + 1.0e+0; > ... > _71 = _69 * _70; > > which is: > `(s_64 + 1.0) * _70` which can be rewritten as

[Bug rtl-optimization/118505] [15 regression] aarch64: 25% regression in TSVC s258 since r15-3436-gb2b20b277988ab

2025-01-15 Thread dhruvc at nvidia dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118505 --- Comment #1 from Dhruv Chawla --- I'm not sure if this is an aarch64-specific issue or a middle-end issue, so I've filed it under aarch64 for now.

[Bug rtl-optimization/118505] New: [15 regression] aarch64: 25% regression in TSVC s258 since r15-3436-gb2b20b277988ab

2025-01-15 Thread dhruvc at nvidia dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118505 Bug ID: 118505 Summary: [15 regression] aarch64: 25% regression in TSVC s258 since r15-3436-gb2b20b277988ab Product: gcc Version: 15.0 Status: UNCONFIRMED Seve

[Bug middle-end/118188] New: [15 regression] aarch64: 30% regression in TSVC s4115 since r15-5565-gdbc38dd9e96a99

2024-12-23 Thread dhruvc at nvidia dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118188 Bug ID: 118188 Summary: [15 regression] aarch64: 30% regression in TSVC s4115 since r15-5565-gdbc38dd9e96a99 Product: gcc Version: 15.0 Status: UNCONFIRMED Sev

[Bug rtl-optimization/117801] [15 regression] aarch64: 20% regression in TSVC s278 since r15-3509-gd34cda72098867

2024-11-28 Thread dhruvc at nvidia dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117801 --- Comment #12 from Dhruv Chawla --- (In reply to Richard Biener from comment #11) > Created attachment 59722 [details] > patch > > This patch passed bootstrap & regtest on x86_64-unknown-linux-gnu. I did > not check whether it solves the aar

[Bug target/117801] New: aarch64: 20% regression in TSVC s278 since r15-3509-gd34cda72098867

2024-11-26 Thread dhruvc at nvidia dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117801 Bug ID: 117801 Summary: aarch64: 20% regression in TSVC s278 since r15-3509-gd34cda72098867 Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal

[Bug target/117477] Register allocator chooses a slot location instead a new callee saved register and not taking inot account pair allocation

2024-11-18 Thread dhruvc at nvidia dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117477 --- Comment #4 from Dhruv Chawla --- (In reply to Andrew Pinski from comment #3) > Do you have a testcase which comes from some real code that shows the issue > or is this just noticed from the small testcase you produced? Hi, I noticed this oc

[Bug rtl-optimization/117477] New: aarch64: Unnecessary stack spill generated around function call

2024-11-07 Thread dhruvc at nvidia dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117477 Bug ID: 117477 Summary: aarch64: Unnecessary stack spill generated around function call Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal