-
Notifications
You must be signed in to change notification settings - Fork 3.4k
FIX Turn off settings.LTO
if -fno-lto
is passed
#20309
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work coming up with test case. Does this test indeed fail without this patch?
I made a PR too but was going to pass on the trying to write a test. (#20310) :) I'll close mine.
Yes I checked that the test fails without the patch. |
test/test_other.py
Outdated
@@ -11148,6 +11148,23 @@ def test_setjmp_emulated_casts(self): | |||
''') | |||
self.do_runf('src.c', 'ok\ndone\n', emcc_args=['-sEMULATE_FUNCTION_POINTER_CASTS']) | |||
|
|||
def test_setjmp_no_lto(self): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps just call this test_no_lto
.. and add a comment with a link to the bug, since this seems like a very specific regression test.
Thanks for looking into this and fixed it! |
test-browser-chrome seems to have some flakes... |
Resolves #20308.