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
Currently maspsx expects bss/sbss to use .comm or .lcomm directives and so these symbols will not end up in sbss (and so will not be considered for any special $gp-related flows.
Whilst the nice solution would be to omit the attribute modifier when using gcc+maspsx+gnu as, it shouldn't be too hard to handle this (to make it easier to compare psyq vs maspsx)
The text was updated successfully, but these errors were encountered:
Using the
__attribute__
modifier e.g.to force gcc to put symbols in the
.sbss
section results in the following assembly:Currently
maspsx
expects bss/sbss to use.comm
or.lcomm
directives and so these symbols will not end up in sbss (and so will not be considered for any special $gp-related flows.Whilst the nice solution would be to omit the attribute modifier when using gcc+maspsx+gnu as, it shouldn't be too hard to handle this (to make it easier to compare psyq vs maspsx)
The text was updated successfully, but these errors were encountered: