public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "matthias291999 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/105872] GNAT Bug Box compiling spark_xrefs.adb Date: Tue, 07 Jun 2022 18:58:30 +0000 [thread overview] Message-ID: <bug-105872-4-8sUTuGnhWH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105872-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105872 --- Comment #1 from Matthias Zimmerman <matthias291999 at gmail dot com> --- analyzing Node_Id = 2490 system.ads:81:48 N_ENTRY_CALL_STATEMENT This should not be N_ENTRY_CALL_STATEMENT, an earlier pass should have converted it into N_OP_MINUS (grep " 2490 " on gcc-12.1) analyzing Node_Id = 2490 system.ads:81:48 N_OP_MINUS
next prev parent reply other threads:[~2022-06-07 18:58 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-07 11:17 [Bug ada/105872] New: " matthias291999 at gmail dot com 2022-06-07 18:58 ` matthias291999 at gmail dot com [this message] 2022-06-08 9:06 ` [Bug ada/105872] GNAT Bug Box compiling gcc/ada/spark_xrefs.adb mikpelinux at gmail dot com 2022-06-08 9:08 ` mikpelinux at gmail dot com 2022-06-08 9:13 ` matthias291999 at gmail dot com 2022-06-08 19:43 ` ebotcazou 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-105872-4-8sUTuGnhWH@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: linkBe 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).