Cross compilation: Difference between revisions
m
→{{header|Phix}}: sp, more
m (sp) |
m (→{{header|Phix}}: sp, more) |
||
Line 14:
The compiler tries hard to avoid emitting unnecessary binary, which is likely to be more successful when those routines are used as plainly as possible, without any and/or parts to the conditional. Likewise #ilASM{} aka inline assembly can contain guards
such as [32] to emit (only) the relevant code for different target architectures, see
[[Conditional_structures#ilASM]] and [[Pragmatic_directives#Phix]] for more
The requires() routine can help ensure time is not needlessly wasted trying to get things to work on
platform(s) where it currently simply does not.
Lastly, pwa
compiler directive "with javascript_semantics" explicitly stating that is possible, and the "without"
variant explicitly blocking it, with similar implications as requires().
|