Repository navigation
SPEC 12.2, 12.3: the floating-point state is part of the image's convention - #63
Merged
Merged
Conversation
…ention Co-authored-by: speak-agent <248744407+speak-agent@users.noreply.github.com>
…hen this version is in it Co-authored-by: speak-agent <248744407+speak-agent@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Clause 12.2 gains a row: an image runs, at its entry and in each context, in its convention's floating-point state — on x86-64 the x87 control word
0x037Fand MXCSR0x1F80, on AArch64 FPCR zero. Clause 12.3 states that the loader establishes it at the entry, for initialisers and finalisers and in each context, and that a call from a program of the environment into an image's function is made in it with the caller's restored after it.The System V convention already implied the state; one environment (Windows) begins a thread with the x87 at double precision, under which openkal-musl's
strtod("0.4")gave0x1.99999999998p-2. No declaration changes, so the specification stays at 0.24. The loader's side is mcpplibs/openkal-image#33 (0.5.3).