public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "admin@tho-otto.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/110633] New: Using an unknown identifier as argument to ORD results in ICE Date: Tue, 11 Jul 2023 17:51:58 +0000 [thread overview] Message-ID: <bug-110633-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110633 Bug ID: 110633 Summary: Using an unknown identifier as argument to ORD results in ICE Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: modula2 Assignee: gaius at gcc dot gnu.org Reporter: admin@tho-otto.de Target Milestone: --- When compiling MODULE foo; VAR x: CARDINAL; BEGIN x := ORD(nosuchvar); END foo. I get: M2MetaError.mod:1535:internalformat error detected errorBlock type = abort out = || in = |the parameter to {%A1k%a} must be a variable or constant, seen {%2ad}| Length (out) = 0 len = 69 highplus1 = 2*** WARNING *** there are active plugins, do not report this as a bug unless you can reproduce it without enabling any plugins. Event | Plugins PLUGIN_FINISH | m2rte cc1gm2: internal compiler error: in libc_abort, at m2/mc-boot-ch/Glibc.c:70 Might be a general problem when using builtin functions (replacing ORD by CHR gives the same ICE). Maybe a similar problem as in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110189
next reply other threads:[~2023-07-11 17:51 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-11 17:51 admin@tho-otto.de [this message] 2023-08-01 18:13 ` [Bug modula2/110633] " gaius at gcc dot gnu.org 2023-08-01 18:18 ` gaius 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-110633-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: 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).