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

Disallow alwaysinline and noinline on functions #726

Merged
merged 2 commits into from Jun 16, 2021

Conversation

gmarkall
Copy link
Member

@gmarkall gmarkall commented Jun 9, 2021

Adding "alwaysinline" and "noinline" attributes to a function results in an error similar to the following when compiling with LLVM:

Attributes 'noinline and alwaysinline' are incompatible!
LLVM ERROR: Broken module found, compilation aborted!

and then the interpreter is killed. This PR prevents both attributes being added at the Python level, to prevent the above error message and termination.

Adding "alwaysinline" and "noinline" attributes to a function results in
an error similar to the following when compiling with LLVM:

```
Attributes 'noinline and alwaysinline' are incompatible!
LLVM ERROR: Broken module found, compilation aborted!
```

and then the interpreter is killed. This commit prevents both attributes
being added at the Python level, to prevent the above error message and
termination.
@esc
Copy link
Member

esc commented Jun 16, 2021

I looked at the build failure, this has nothing to do with the PR but is caused by an upgrade of sphinx from v3.2.1 to v4.0.1 and can be triggered by including -Wn which treats this new warning as an error and breaks the build. Confirmed locally, I can reproduce this build failure.

The `llvm:ref` directive seems to be unknown. I'm not sure how it did
work, but as this is used precisely once in the docs it seems reasonable
to just replace it with a URL.
@esc esc added this to the Version 0.37.0 RC milestone Jun 16, 2021
@esc
Copy link
Member

esc commented Jun 16, 2021

Thanks for the patch!

@esc esc merged commit a1dcfe5 into numba:master Jun 16, 2021
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.

None yet

2 participants