forked from ocaml-flambda/flambda-backend
-
Notifications
You must be signed in to change notification settings - Fork 0
Remove old x86 directives #5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
spiessimon
wants to merge
23
commits into
new-directives-in-x86
Choose a base branch
from
new-directives-x86-remove-old-ones
base: new-directives-in-x86
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Remove old x86 directives #5
spiessimon
wants to merge
23
commits into
new-directives-in-x86
from
new-directives-x86-remove-old-ones
Conversation
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
63f364e
to
f9bd95d
Compare
dd5e4e9
to
8c7611e
Compare
0ca1d52
to
bd498a6
Compare
1775d6a
to
fb842d5
Compare
bd498a6
to
7bf1756
Compare
…_name.t` (ocaml-flambda#3708) * Introduce `Global_module.Parameter_name.t` Takes the place of any `Global_module.t` or `Global_module.Name.t` that is known to be the name of a parameter. Can't have parameters. (Notably, even the current half-worked-out plans for parameterized parameters would actually keep this type in many places, so this isn't as much in the way as one might think.) * Don't call `global_of_global_name` on parameter names This has the benefit of not loading the .cmi file for something whose signature we don't need (say because the parameter is only used as part of an instance name). * Code review
This reorganizes the docs for easy deployment to the oxcaml website
* Reverse the instruction sequence at the end of pop_all * Reenable checking top trap vs popped handler
…caml-flambda#3302) * Replay history * Apply suggestions from code review Co-authored-by: Nathanaëlle Courant <[email protected]> * Remove dead code * update CR * Remove now incorrect comment * make fmt --------- Co-authored-by: Nathanaëlle Courant <[email protected]>
Remove unused [Cfg_to_linear.print_assembly]
Use "caml_simd*" instead of "caml_sse*" builtins in simd array tests
remove duplicate prefix
formatted bytecomp/bytegen.ml
Adds a new IR called "Blambda" for compiling complicated things to bytecode slightly more easily than via Lambda. Blambda is designed to be a lambda-like expression language where every primitive is also a bytecode primitive. Control flow is still the same as lambda, except switch statements have already been elaborated somewhat. This allows us to separate the bytecode backend into two stages: First, Lambda -> Blambda: Preserves the expression structure, but compiles all complex primitives down to ones with corresponding bytecode instructions. This will become more important as we continue to add more primitives to Lambda which have no corresponding bytecode instruction. The translation of non-native operations and switches that was previously done in bytecomp/bytegen.ml is now done in a separate pass in bytecomp/blambda_of_lambda.ml. Second, Blambda -> Instructions: Only has to deal with linearizing the Lambda-like control flow. The comparatively fragile stack size maintenance and stack index computations can remain in their own module which doesn't need to be modified every time we change Lambda. As with any IR, there is also code to print blambda in bytegen/printblambda.ml, as well as a new command-line flag for ocamlc to dump the blambda code.
Correct sort in coercion case of [type_argument]
7bf1756
to
c73e03b
Compare
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.
No description provided.