https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89893
--- Comment #30 from 康 珊 <kangshan0910 at hotmail dot com> --- (In reply to Martin Liška from comment #29) > > Thanks for your reminder. Currently I found there were 3 ways to solve the > > issue. > > 1.Remove “enable-lto” in configure and open “fno-strict-aliasing”. > > 2.Add “__attribute__((noipa))” to the uv_unref(uv_handle_t*) function. > > 3.Add “__attribute__((noinline))” to the uv_unref(uv_handle_t*) function. > > Maybe the first solution is a more reliable one in contrast to the other two > > solutions. As solution 2 and 3 are more likely a workaround. Do you have any > > suggestions? > > It's always needed to use -fno-strict-aliasing as mentioned here: > https://github.com/nodejs/node/issues/27054 > > and the using --enable-lto should be fine. But if using "--enable-lto" and "-fno-strict-aliasing", the issue cannot be solved. In order to solve the issue, besides those options, “__attribute__((noipa))” has to be added to the uv_unref(uv_handle_t*) function. So you recommend this solution, right?
