Skip to content

Conversation

@yashssh
Copy link
Contributor

@yashssh yashssh commented Oct 8, 2025

@yashssh
Copy link
Contributor Author

yashssh commented Oct 8, 2025

Not sure what the macOS failure is about

@stuartarchibald
Copy link
Contributor

Not sure what the macOS failure is about

I've restarted it, it may have been network related and a download was interrupted but a process returned 0 and so continued to the next step in the CI build.

Copy link
Contributor

@stuartarchibald stuartarchibald left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the patch. From inspection, I think this now matches the LLVM logic.

@stuartarchibald stuartarchibald added this to the 0.46.0rc1 milestone Oct 8, 2025
@esc esc merged commit c3a1bbb into numba:main Oct 8, 2025
22 checks passed
@dnadlinger
Copy link
Contributor

dnadlinger commented Oct 8, 2025

As mentioned in #1306, I wonder about the backwards compatibility angle here, though – as an llvmlite user, there now isn't a piece of code I can write to access Os that works with both 0.44 as well as the next release.

@yashssh
Copy link
Contributor Author

yashssh commented Oct 9, 2025

While I agree there isn't a piece of code that will work with both 0.44 and the next release for Os. I think adding backward compatibility for this might not be ideal.

(Edit: Deleted a part of the comment, got confused in the release timeline)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

llvm.create_pipeline_tuning_options(size_level=…) not accessible

4 participants