public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/108553] New: GM2 ICEs on mistyped command line options Date: Thu, 26 Jan 2023 08:29:19 +0000 [thread overview] Message-ID: <bug-108553-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108553 Bug ID: 108553 Summary: GM2 ICEs on mistyped command line options Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: modula2 Assignee: gaius at gcc dot gnu.org Reporter: rguenth at gcc dot gnu.org Target Milestone: --- When mistyping -Wreturn-type as -Wereturn-type the compiler ICEs because we segfault in #5 0x0000000000c19cfd in gm2_langhook_init_options (decoded_options_count=7, decoded_options=0x429a190) at /home/rguenther/src/trunk/gcc/m2/gm2-lang.cc:296 296 fprintf(stderr, "%s : %s\n", opt, (arg ? arg : "")); (gdb) l 291 /* FALLTHROUGH */ 292 default: 293 if (code >= N_OPTS) 294 { 295 // FIXME remove debug. 296 fprintf(stderr, "%s : %s\n", opt, (arg ? arg : "")); 297 break; 298 } 299 /* Do not pass Modula-2 args to the preprocessor, any that we care 300 about here should already have been handled above. */ (gdb) p opt $2 = 0x6874616d5f656661 <error: Cannot access memory at address 0x6874616d5f656661> Note code is OPT_SPECIAL_unknown here.
next reply other threads:[~2023-01-26 8:29 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-26 8:29 rguenth at gcc dot gnu.org [this message] 2023-01-26 8:32 ` [Bug modula2/108553] " rguenth at gcc dot gnu.org 2023-01-26 8:38 ` iains at gcc dot gnu.org 2023-01-26 9:10 ` iains at gcc dot gnu.org 2023-01-26 9:46 ` marxin at gcc dot gnu.org 2023-01-26 12:47 ` rguenth at gcc dot gnu.org 2023-01-26 16:30 ` cvs-commit at gcc dot gnu.org 2023-01-27 7:44 ` rguenth at gcc dot gnu.org 2023-01-27 8:45 ` iains 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-108553-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).