JohnReagan added a comment.
As a legacy OS provider on a platform that needs/requires ABI compatibility, I
don't like the direction this is going. Like @rnk, I would having MORE control
over struct layout is better than less. I'm adapting non-traditional languages
to LLVM which allow very exp
JohnReagan added a comment.
Does any of this impact the -f128 support? We use f128 x-float on OpenVMS.
We've historically only aligned on 8-byte boundaries for legacy reasons (I'm
not opposed to having my own mods to control the record layout and/or data
layout)
Repository:
rG LLVM Github
JohnReagan added a comment.
Does the current code generate all the prologue cfi directives?
Epilogue too? The last time I checked, it did not (especially for
epilogues).
Fully asynch prologue/epilogue is one of the things that we need for
OpenVMS and will be doing that work. We're also looking