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/108555] New: gm2_langhook_option_lang_mask causes all (unappropriate) C language options to be recognized
Date: Thu, 26 Jan 2023 09:46:27 +0000	[thread overview]
Message-ID: <bug-108555-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108555

            Bug ID: 108555
           Summary: gm2_langhook_option_lang_mask causes all
                    (unappropriate) C language options to be recognized
           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: ---

137     static unsigned int
138     gm2_langhook_option_lang_mask (void)
139     {
140       /* We need to process some driver options and pass through some C
141          ones to build our preprocessing lines.  */
142       return CL_ModulaX2 | CL_C | CL_DRIVER;
143     }

we shouldn't add CL_C here but instead replicate the needed ones in
m2/lang.opt like other frontends do.  This for example causes
-Wreturn-type to be accepted and in the end causes PR108551

See fortran/lang.opt which for example has

I 
Fortran Joined Separate
; Documented in C

             reply	other threads:[~2023-01-26  9:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26  9:46 rguenth at gcc dot gnu.org [this message]
2023-01-26  9:51 ` [Bug modula2/108555] " rguenth at gcc dot gnu.org
2023-01-26 10:19 ` iains at gcc dot gnu.org
2023-01-26 12:26 ` rguenth at gcc dot gnu.org
2023-01-26 13:10 ` iains at gcc dot gnu.org
2023-01-26 16:38 ` iains at gcc dot gnu.org
2023-01-26 20:30 ` iains at gcc dot gnu.org
2023-01-27  8:48 ` cvs-commit at gcc dot gnu.org
2023-01-27 10:07 ` rguenth 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-108555-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).