public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kloczko.tomasz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/111964] New: 13.2.1: potential GIMPLE bug in inline assempler
Date: Tue, 24 Oct 2023 17:45:46 +0000 [thread overview]
Message-ID: <bug-111964-4@http.gcc.gnu.org/bugzilla/> (raw)
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
next reply other threads:[~2023-10-24 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 17:45 kloczko.tomasz at gmail dot com [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-111964-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).