You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'm always frustrated with 32 bit go programs that pass and return on the stack because it creates a handful of problems. Not only do you need to manually use custom storage and apply and correct all function signatures by hand, but all interface functions will never decompile correctly because no function pointer will be able to have the correct return storage, even after going out of the way to create an appropriate itab.
Describe the solution you'd like
Support for returning values on the stack after the parameters.
Describe alternatives you've considered
I've gotten really good at the necessary mental gymnastics for this sort of thing but any help would be great.
Additional Context
This issue actually applies to all of the incomplete go calling conventions, which is all of them, because they all currently require custom storage, which means no proper function pointers.
The text was updated successfully, but these errors were encountered:
I'm managing to get by for now by using a similar technique used for syscalls with call overrides in an artificial overlay. I have to do this manually for every interface function and every runtime.newobject. I also have to manually set custom storage on every single function which is about as tedious as you can imagine.
Is your feature request related to a problem? Please describe.
I'm always frustrated with 32 bit go programs that pass and return on the stack because it creates a handful of problems. Not only do you need to manually use custom storage and apply and correct all function signatures by hand, but all interface functions will never decompile correctly because no function pointer will be able to have the correct return storage, even after going out of the way to create an appropriate
itab
.Describe the solution you'd like
Support for returning values on the stack after the parameters.
Describe alternatives you've considered
I've gotten really good at the necessary mental gymnastics for this sort of thing but any help would be great.
Additional Context
This issue actually applies to all of the incomplete go calling conventions, which is all of them, because they all currently require custom storage, which means no proper function pointers.
The text was updated successfully, but these errors were encountered: