[Bug tree-optimization/118032] Bootstrap slowdown for risc-v

2024-12-16 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118032 --- Comment #10 from Andreas Schwab --- The 64bit location_t is not part of 92e0e0f8177530b8c6fcafe1d61ba03b00dff6a6..b563a3a00db064d4d47fd171379e1d34d0698faa, it was installed three days earlier.

[Bug tree-optimization/118032] Bootstrap slowdown for risc-v

2024-12-15 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118032 --- Comment #9 from Andrew Pinski --- (In reply to Andreas Schwab from comment #7) > 20241206: 2d 12:19:19 > 20241213: 2d 20:08:16 The big things between this are: 64bit location_t. I wonder if that introduced the slow down.

[Bug tree-optimization/118032] Bootstrap slowdown for risc-v

2024-12-15 Thread jvdelisle at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118032 Jerry DeLisle changed: What|Removed |Added CC||jvdelisle at gcc dot gnu.org --- Commen

[Bug tree-optimization/118032] Bootstrap slowdown for risc-v

2024-12-15 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118032 --- Comment #7 from Andreas Schwab --- 20240920: 2d 09:32:07 20240927: 2d 09:49:40 20241004: 2d 10:05:11 20241020: 2d 09:50:24 20241025: 2d 10:01:37 20241101: 2d 10:36:27 20241108: 2d 11:34:26 20241115: 2d 10:59:49 20241130: 2d 11:50:58

[Bug tree-optimization/118032] Bootstrap slowdown for risc-v

2024-12-15 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118032 --- Comment #6 from Andreas Schwab --- Here are the bootstrap times on the HiFive Unleashed (all languages): 20240920: 3d 09:32:07 20240927: 3d 09:49:40 20241004: 3d 10:05:11 20241020: 3d 09:50:24 20241025: 3d 10:01:37 20241101: 3d 10:36:

[Bug tree-optimization/118032] Bootstrap slowdown for risc-v

2024-12-15 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118032 --- Comment #5 from Jeffrey A. Law --- Oh, on the pioneer. Hard to even guess. Given how under-powered each core is, if you don't keep them all busy it's going to be bad... So I'd be looking for a serialization problem in the build. Or your

[Bug tree-optimization/118032] Bootstrap slowdown for risc-v

2024-12-15 Thread mark at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118032 --- Comment #4 from Mark Wielaard --- The slowdown is on the pioneer box, which has 64 cores and 128GB ram. https://builder.sourceware.org/buildbot/#/builders/gcc-full-fedora-riscv See the build times tab on that page. It used to do builds in 4

[Bug tree-optimization/118032] Bootstrap slowdown for risc-v

2024-12-15 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118032 --- Comment #3 from Jeffrey A. Law --- Could be. I've got the 4G model and a swap partition on an m.2 drive rather than the silly (and insanely slow) mmc card. If Mark's got the 2G version or is using the MMC card, it'd be much more sensitive

[Bug tree-optimization/118032] Bootstrap slowdown for risc-v

2024-12-15 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118032 Richard Biener changed: What|Removed |Added Version|unknown |15.0 Keywords|

[Bug tree-optimization/118032] Bootstrap slowdown for risc-v

2024-12-14 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118032 --- Comment #1 from Jeffrey A. Law --- No, I'm not seeing this in my BPI bootstraps. My bootstrap + regression test is sitting at 26-27hrs. It's been in that range since I turned bootstrapping on back in mid Oct.