public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug c++/111964] New: 13.2.1: potential GIMPLE bug in inline assempler
@ 2023-10-24 17:45 kloczko.tomasz at gmail dot com
2023-10-24 18:00 ` [Bug middle-end/111964] " pinskia at gcc dot gnu.org
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: kloczko.tomasz at gmail dot com @ 2023-10-24 17:45 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111964
Bug ID: 111964
Summary: 13.2.1: potential GIMPLE bug in inline assempler
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: kloczko.tomasz at gmail dot com
Target Milestone: ---
According to node developers it is bug in GIMPLE and inline assembler causing
that node build with enabled LTO fails with missing
PushAllRegistersAndIterateStack symbol.
More details about how to build nodejs 21.0.0 to reproduce this issue is on
https://github.com/nodejs/node/issues/50347
^ permalink raw reply [flat|nested] 5+ messages in thread* [Bug middle-end/111964] 13.2.1: potential GIMPLE bug in inline assempler 2023-10-24 17:45 [Bug c++/111964] New: 13.2.1: potential GIMPLE bug in inline assempler kloczko.tomasz at gmail dot com @ 2023-10-24 18:00 ` pinskia at gcc dot gnu.org 2023-10-24 18:09 ` kloczko.tomasz at gmail dot com ` (2 subsequent siblings) 3 siblings, 0 replies; 5+ messages in thread From: pinskia at gcc dot gnu.org @ 2023-10-24 18:00 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111964 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |lto Component|c++ |middle-end --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- There are some known issues with top-level inline-asm and lto. It would be better if folks moved away from toplevel inline-asm really. ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug middle-end/111964] 13.2.1: potential GIMPLE bug in inline assempler 2023-10-24 17:45 [Bug c++/111964] New: 13.2.1: potential GIMPLE bug in inline assempler kloczko.tomasz at gmail dot com 2023-10-24 18:00 ` [Bug middle-end/111964] " pinskia at gcc dot gnu.org @ 2023-10-24 18:09 ` kloczko.tomasz at gmail dot com 2023-10-24 21:32 ` pinskia at gcc dot gnu.org 2023-10-24 21:32 ` pinskia at gcc dot gnu.org 3 siblings, 0 replies; 5+ messages in thread From: kloczko.tomasz at gmail dot com @ 2023-10-24 18:09 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111964 --- Comment #2 from Tomasz Kłoczko <kloczko.tomasz at gmail dot com> --- (In reply to Andrew Pinski from comment #1) > There are some known issues with top-level inline-asm and lto. > > It would be better if folks moved away from toplevel inline-asm really. May I ask to drop some comment about that with some instruction what needs to be done instead under https://github.com/nodejs/node/issues/50347 ? ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug middle-end/111964] 13.2.1: potential GIMPLE bug in inline assempler 2023-10-24 17:45 [Bug c++/111964] New: 13.2.1: potential GIMPLE bug in inline assempler kloczko.tomasz at gmail dot com 2023-10-24 18:00 ` [Bug middle-end/111964] " pinskia at gcc dot gnu.org 2023-10-24 18:09 ` kloczko.tomasz at gmail dot com @ 2023-10-24 21:32 ` pinskia at gcc dot gnu.org 2023-10-24 21:32 ` pinskia at gcc dot gnu.org 3 siblings, 0 replies; 5+ messages in thread From: pinskia at gcc dot gnu.org @ 2023-10-24 21:32 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111964 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Dup of bug 46820 (and others). Again the big issue is top-level inline-asm is just broken for LTO really. Things like PushAllRegistersAndIterateStack in this case should be put into a .s file. I see they did that for deps/v8/src/heap/base/asm/arm64/push_registers_masm.S already too. *** This bug has been marked as a duplicate of bug 46820 *** ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug middle-end/111964] 13.2.1: potential GIMPLE bug in inline assempler 2023-10-24 17:45 [Bug c++/111964] New: 13.2.1: potential GIMPLE bug in inline assempler kloczko.tomasz at gmail dot com ` (2 preceding siblings ...) 2023-10-24 21:32 ` pinskia at gcc dot gnu.org @ 2023-10-24 21:32 ` pinskia at gcc dot gnu.org 3 siblings, 0 replies; 5+ messages in thread From: pinskia at gcc dot gnu.org @ 2023-10-24 21:32 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111964 --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- And: v8/src/heap/base/asm/ia32/push_registers_masm.asm ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2023-10-24 21:32 UTC | newest] Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2023-10-24 17:45 [Bug c++/111964] New: 13.2.1: potential GIMPLE bug in inline assempler kloczko.tomasz at gmail dot com 2023-10-24 18:00 ` [Bug middle-end/111964] " pinskia at gcc dot gnu.org 2023-10-24 18:09 ` kloczko.tomasz at gmail dot com 2023-10-24 21:32 ` pinskia at gcc dot gnu.org 2023-10-24 21:32 ` pinskia at gcc dot gnu.org
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).