-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hcode-hw062823a.opmst failed to compile with Fedora 39 ppc64le #4
Comments
I can also confirm this issue also impacts |
@runlevel5 - What was your previously working level? |
Looks like a real bug. embeddedAddr is declared on line 922 based on io_rs4; then io_rs4 is realloc'ed on line 927, so its pointer could change and point somewhere different. The simple fix here is to declare embeddedAddr after realloc. @sumitk56 , could you please take a look? |
This issue only occur on Fedora 37, 38 and 39 (rawhide) ppc64le. I do not run into this issue with Ubuntu 22.04 ppc64le (with GCC 8.4.0) |
track pervasive scan region and SCOM ring hookups based on drop R VHDL and current Clock Voltage spec XLS match scan region updates FSI added fsi0inv (region #5) TP added dpllpau (region #8), dpllnest (region #9) N0 shifted pe1 to own region (region #4), added iopsi (region #6) N1 remove region #1 (mcd -> region #2, pe0 -> region #4) PCI add pcs0..3 (region #2-#5), psm0..3 (region #6-#9) MC remove region #2 (dl01 -> region #3, dl23 -> region #4, ioo0 -> region #5, ioo1 -> region #6) EQ added clkadj (region #10) AXON remove odl (region #3) match scom ring updates NMMU extend match to second SCOM satellite (#1) on ring #3 PEC,PHB correct n0/n1 instance numbering cover additional sat IDs (#4-#6) on PCI chiplet ring #2 PAUC rename from PPE remove non-IO PPE entries, P10 target will only cover IO PPEs add PTL, IO PPE matching rules (direct and per-bus indirect) support match for PAU chiplet pervasive resources PAU update ring matching rules (#2,#3 for first pau unit in chiplet, #4,#5 for second) IOHS limit ring match for direct AXON chiplet access to ring #4 (pdl) update matching rules for indirect PAU chiplet access via IOPPE, remove rules matching direct PAU chiplet access EQ fix matching rules for EQ,C target split of ring space on PSCOM endpoint #1 MC,MI adjust ring ID (mc_0 shifted from #2 to #3) change satellite ID matches to cover MCBIST and PBI MCC adjust ring ID (mc_0 shifted from #2 to #3), cover upstream and downstream TL layer registers as well as MCBIST/PBI indirect access to the channel facilities OMIC add matches for IO PPE indirect per-group regs, MC direct access through omi rings (#5-#6) for shared DL regs OMI add matches for IO PPE indirect per-lane regs, MC direct access through omi rings (#5-#6) for sub-channel specific DL regs (separate range for non PM and PM specific regs) update HWP metadata comments for scan xlate source files fix unitialized variables in p10_scom_xlate impacting clock domain analysis for chip target scoped input update unit test to cover matching changes Change-Id: I66ad0419be5b0915fef81769c82d9f3c3bbea768 Original-Change-Id: I769a4d76266ffcf94d803887e73c6acdf57e5107 Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/76629 Tested-by: Jenkins Server <[email protected]> Reviewed-by: Benjamin Gass <[email protected]> Tested-by: PPE CI <[email protected]> Reviewed-by: Thi N. Tran <[email protected]> Reviewed-by: Joseph J. McGill <[email protected]>
Info
I tried to build a RaptorCS blackbird firmware open-power/op-build#5256 on Fedora 39 ppc64le but got error with hcode-hw062823a.opmst (see Error Output)
I have tried GCC 8.4.0, 9.4, 10.4.0 and 12.3.0 but still produce the same error.
System Details Report
Report details
Hardware Information:
Software Information:
Error Output
The text was updated successfully, but these errors were encountered: