Hi,
> File magic was wrong in my version of manpage.
> Changed references to C in source and compiler to Fortran.
> Changed options back to " -O2 -Wall " to match the rest.
>
> You need to balance compile time with run time.
> Is -O2 wise?
>
> You need at least -O for some of the important compile time checks so
> -O may be a better option.
>
> These can be given after magic so could also be empty.
Thanks for your interest in binfmtc.
For most code which you can compile-and-run on-the-fly -O2 doesn't
take too long to build, and it generates good enough code. So the
trade-off is good-enough code that doesn't take too long.
Rather than optiomization process itself, looking for the files,
parsing the header files and loading the compiler etc takes the big
chunk.
So, that's my rationale for -O2 as default.
If there's a language that significantly takes longer with -O2, I
might consider changing the default value.
regards,
junichi
--
[EMAIL PROTECTED],debian.org}
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
