public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/108553] GM2 ICEs on mistyped command line options Date: Thu, 26 Jan 2023 09:10:51 +0000 [thread overview] Message-ID: <bug-108553-4-dWugK98f6T@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108553-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108553 --- Comment #3 from Iain Sandoe <iains at gcc dot gnu.org> --- I'm trying to reproduce this - in the meantime does the obvious fix solve the problem for you? diff --cc gcc/m2/gm2-lang.cc index 4d9cae205a7,4d9cae205a7..a30e626620c --- a/gcc/m2/gm2-lang.cc +++ b/gcc/m2/gm2-lang.cc @@@ -290,12 -290,12 +290,9 @@@ gm2_langhook_init_options (unsigned in M2Options_SetVerbose (value); /* FALLTHROUGH */ default: ++ /* We handled input files above. */ if (code >= N_OPTS) -- { -- // FIXME remove debug. -- fprintf(stderr, "%s : %s\n", opt, (arg ? arg : "")); -- break; -- } ++ break; /* Do not pass Modula-2 args to the preprocessor, any that we care about here should already have been handled above. */ if (option->flags & CL_ModulaX2)
next prev parent reply other threads:[~2023-01-26 9:10 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-26 8:29 [Bug modula2/108553] New: " rguenth at gcc dot gnu.org 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 [this message] 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-dWugK98f6T@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).