Skip to content
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

Fix readnone attribute for llvm 16 #7152

Merged
merged 2 commits into from
Nov 8, 2022

Conversation

abadams
Copy link
Member

@abadams abadams commented Nov 7, 2022

The readnone flag was changed to memory(none) when applied to functions. llvm-as dynamically upgrades readnone applied to functions, so our .ll is fine for now, but there were places in the compiler we were manually sticking 'readnone' on a function.

Also did a driveby makefile fix to remove some vestigial wasm stuff that was throwing errors with newer versions of llvm-config

The readnone flag was changed to memory(none) when applied to functions.
llvm-as dynamically upgrades readnone applied to functions, so our .ll
is fine for now, but there were places in the compiler we were manually
sticking 'readnone' on a function.

Also did a driveby makefile fix to remove some vestigial wasm stuff that
was throwing errors with newer versions of llvm-config
@steven-johnson steven-johnson merged commit 102c059 into main Nov 8, 2022
ardier pushed a commit to ardier/Halide-mutation that referenced this pull request Mar 3, 2024
* Fix readnone attribute for llvm 16

The readnone flag was changed to memory(none) when applied to functions.
llvm-as dynamically upgrades readnone applied to functions, so our .ll
is fine for now, but there were places in the compiler we were manually
sticking 'readnone' on a function.

Also did a driveby makefile fix to remove some vestigial wasm stuff that
was throwing errors with newer versions of llvm-config

* Revert formatting changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants