This is believed to match behavior by ML.EXE and ML64.EXE.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
Thanks!
I wonder if ml allows nested procs to refer to the parameters of the outer proc – then we'd have to handle activation records like gcc creates them for its nested functions.
But we don't even implement parameters for proc at all, so that's moot for now :)
Comment Actions
"Good" news - if you provide arguments to PROC that would require prologue/epilogue support (even if prologues and epilogues are disabled), nesting is suddenly disallowed. This is true if the arguments are provided to the inner PROC, the outer PROC, or both. So this will never come up... when we add parameter support, we'll just need to block nesting when parameters are provided.