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

build: turn on -fno-strict-aliasing #2588

Merged
merged 1 commit into from Nov 6, 2020
Merged

Conversation

bnoordhuis
Copy link
Member

Turn on -fno-strict-aliasing and, in the case of the gyp build, export
it to projects that depend on libuv.

Fixes: #1230
CI: https://ci.nodejs.org/job/libuv-test-commit/1668/

@vcunat
Copy link
Contributor

vcunat commented Dec 29, 2019

Well, note that it doesn't solve the whole problem, as some fields of the aliasing types are meant to be used directly. EDIT: now I see the README change :-)

@vtjnash
Copy link
Member

vtjnash commented Jul 28, 2020

@bnoordhuis rebase and merge this?

@vtjnash
Copy link
Member

vtjnash commented Aug 12, 2020

bump?

Turn on `-fno-strict-aliasing` in libuv and add a note in the README for
downstream projects.

Fixes: libuv#1230
PR-URL: libuv#2588
Reviewed-By: Jameson Nash <vtjnash@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
@vtjnash
Copy link
Member

vtjnash commented Nov 5, 2020

Hopefully I got the cmake part correct in the rebase.

CI ✅: https://ci.nodejs.org/job/libuv-test-commit/2083/

@vtjnash vtjnash merged commit cbcd0cf into libuv:v1.x Nov 6, 2020
@bnoordhuis bnoordhuis deleted the fix1230 branch February 18, 2022 10:01
JeffroMF pushed a commit to JeffroMF/libuv that referenced this pull request May 16, 2022
Turn on `-fno-strict-aliasing` in libuv and add a note in the README for
downstream projects.

Fixes: libuv#1230
PR-URL: libuv#2588
Reviewed-By: Jameson Nash <vtjnash@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
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.

The way libuv does inheritance violates strict aliasing
5 participants