implement markdown generator for compiler backend compatibility table #2388
+629
−11
Conversation
This file contains 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
|
Stopped the CI because it does not test the script. |
SimeonEhrig
force-pushed
the
markdownGenReadme
branch
from
55e40b7
to
f822c16
Compare
fwyzard
approved these changes
Sep 20, 2024
|
@SimeonEhrig is this ready to go ? |
|
Yes. The generator is ready and I replaced the table with the generated version. The content is the same like before. Only the white space and so matches now. |
psychocoderHPC
approved these changes
Sep 20, 2024
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.
The Python script generates the Markdown table for compiler back-end compatibility from a json config.
Solves the problem, that at least a 4K display is required to change the table :-(
Can be combined with the scripts of
job_generator.pylater to automatically generates some of the columns.Should be merged after #2387 to solve the merge conflict.Removed Clang 18 and 19. Looks like #2387 requires some work. Therefore merge this PR first.