-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
gcc-11 builds with --enable-lto cause test segfaults + runtime errors #38501
Comments
Here is the output of the test suite. |
@mkszuba Any chance you can use a native debugger to get a backtrace here, or provide binary + coredump? |
Sure, here you go. |
Upstream Bug: nodejs/node#38501 Gentoo Bug: https://bugs.gentoo.org/787158 Signed-off-by: Patrick McCarty <patrick.mccarty@intel.com>
Ping this issue still exist and with GCC 11 being used more and more, also more and more people are affected by the lack of possible optimisations. Is there a chance that someone with more experience can take a look into what is the cause of the problems when building with LTO enabled? |
I have confirmed that there are NO ERRORs in gcc-11 + --enable-lto. src: master branch + cherry-pick c6e4596 (#41772) export CFLAGS="-march=native"
export CXXFLAGS="-march=native"
export CPPFLAGS="-march=native"
./configure --experimental-enable-pointer-compression --enable-lto
make -j60
make -j60 test |
What steps will reproduce the bug?
3a. To reproduce test segfault, run cctest
3b. To reproduce runtime errors, use this build of node to e.g. compile a recent version of Firefox
How often does it reproduce? Is there a required condition?
Every time.
What is the expected behavior?
Node passes tests and runs correctly.
What do you see instead?
See e.g. https://bugs.gentoo.org/787158
Additional information
Enabling LTO for the same node versions works fine with gcc-10.
The text was updated successfully, but these errors were encountered: