gcc-11 builds with --enable-lto cause test segfaults + runtime errors #38501

Activity

1. mkszuba commented on May 1, 2021

   

   mkszuba

   on May 1, 2021

   Author

   More actions

   Here is the output of the test suite.

   cctest-segfault.log
2. addaleax commented on May 2, 2021

   

   addaleax

   on May 2, 2021

   Member

   More actions

   @mkszuba Any chance you can use a native debugger to get a backtrace here, or provide binary + coredump?
3. mkszuba commented on May 2, 2021

   

   mkszuba

   on May 2, 2021

   Author

   More actions

   Sure, here you go.
   node-14.16.1-cctest_backtrace.log
4. clrpackages

   added a commit that references this issue on May 18, 2021

   Disable LTO, since runtime errors occur with GCC 11

   ...

   51c5850
5. targos

   added

   buildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.

   on Aug 9, 2021
6. janhenke commented on Jan 23, 2022

   

   janhenke

   on Jan 23, 2022

   More actions

   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?
7. richardlau commented on Jan 23, 2022

   

   richardlau

   on Jan 23, 2022

   Member

   More actions

   Does this happen with Node.js >=17.2.0/builds from the master branch? In particular, does #40631 (which fixed #40368) help?

   I have already cherry-picked #40631 onto the v16.x-staging and v14.x-staging branches so it should go out in the releases planned for the end of January/beginning of February.
8. sapics commented on Jan 30, 2022

   

   sapics

   on Jan 30, 2022

   Last edited by sapics

   Contributor

   More actions

   I have confirmed that there are NO ERRORs in gcc-11 + --enable-lto.
   Sorry, I have no idea that my test is equivalent to cctest or not.
   I have tested as follows.

   src: master branch + cherry-pick c6e4596 (#41772)
   Platform: Ubuntu 20.04
   cpu: Ryzen Threadripper
   gcc -v: gcc 11.1.0
   test as root with following command

   export CFLAGS="-march=native"
   export CXXFLAGS="-march=native"
   export CPPFLAGS="-march=native"
   ./configure --experimental-enable-pointer-compression --enable-lto
   make -j60
   make -j60 test
9. github-actions commented on Jun 27, 2026

   

   github-actionsbot

   on Jun 27, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue has been marked as stale due to 210 days of inactivity.
   It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
10. github-actions

    added

    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.

    on Jun 27, 2026
11. github-actions commented on Jul 28, 2026

    

    github-actionsbot

    on Jul 28, 2026 – with GitHub Actions

    Contributor

    More actions

    This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
    If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
12. github-actions

    closed this as not plannedon Jul 28, 2026