Opened 6 months ago
Last modified 5 months ago
#72847 new defect
flang-16, flang-17, flang-20, flang-devel: kernel panic while compiling
| Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.11.4 |
| Keywords: | bigsur arm64 | Cc: | cjones051073 (Chris Jones) |
| Port: | flang-16, flang-17, flang-20, flang-devel |
Description
Compiling flang-20 @20.1.8 caused the macOS 11 arm64 buildbot worker to kernel panic at step 6693 of 7650 three times in a row:
Change History (4)
comment:1 Changed 6 months ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 5 months ago by ryandesign (Ryan Carsten Schmidt)
| Port: | flang-16 flang-17 added |
|---|---|
| Summary: | flang-20 @20.1.8: kernel panic while compiling → flang-16, flang-17, flang-20: kernel panic while compiling |
Also happens with:
- flang-16: https://build.macports.org/builders/ports-11_arm64-builder/builds/116799/steps/install-port/logs/stdio
- flang-17: https://build.macports.org/builders/ports-11_arm64-builder/builds/116802/steps/install-port/logs/stdio
It's perhaps relevant that this machine also has macOS 15 on another volume in the same APFS container, and so "iBoot" has presumably been updated to a macOS 15-compatible and perhaps no longer entirely macOS 11-compatible version.
comment:3 Changed 5 months ago by ryandesign (Ryan Carsten Schmidt)
Now reported to Apple as FB20004407.
comment:4 Changed 5 months ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | cjones051073 added |
|---|---|
| Port: | flang-devel added |
| Summary: | flang-16, flang-17, flang-20: kernel panic while compiling → flang-16, flang-17, flang-20, flang-devel: kernel panic while compiling |
flang-17 didn't kernel panic after we set build.mem_per_job properly (#72954):
https://build.macports.org/builders/ports-11_arm64-builder/builds/119631
flang-devel still kernel panics; we haven't set build.mem_per_job there (nor in flang-16):
https://build.macports.org/builders/ports-11_arm64-builder/builds/119632

Instead of the usual crash log with backtrace, the crash reporter window only says: