Skip to content

Conversation

eli-schwartz
Copy link
Contributor

I actually cannot find any traces of it ever being used but it certainly isn't used now. It builds a bunch of code for a static library that is never consumed, which is both slow and also potentially erroring out (since the unused code contains strict-aliasing violations).

Fixes: #148

I actually cannot find any traces of it *ever* being used but it
certainly isn't used now. It builds a bunch of code for a static library
that is never consumed, which is both slow and also potentially erroring
out (since the unused code contains strict-aliasing violations).

Fixes: nmeum#148
@eli-schwartz
Copy link
Contributor Author

CI failure is the return of the terrible horrible no good very bad GitHub Actions Python...

@anatol anatol merged commit 32559b1 into nmeum:master Jun 18, 2024
@anatol
Copy link
Collaborator

anatol commented Jun 18, 2024

thank you @eli-schwartz for your contribution!

@eli-schwartz
Copy link
Contributor Author

I actually realized I should have deleted the patches/base/ as well, and pushed an amended commit approximately 90 seconds after you merged the PR. :D

@anatol
Copy link
Collaborator

anatol commented Jun 18, 2024

I actually realized I should have deleted the patches/base/ as well, and pushed an amended commit approximately 90 seconds after you merged the PR. :D

np, please send another PR.

@eli-schwartz
Copy link
Contributor Author

#150

@Biswa96
Copy link
Collaborator

Biswa96 commented Jun 18, 2024

There are some leftovers that can be removed. I shall create a pull request with those change.

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.

Build fails with strict-aliasing violations
3 participants