public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105355] -msmall-data-limit= unexpectedly accepts a separate argument
Date: Wed, 11 May 2022 06:56:31 +0000	[thread overview]
Message-ID: <bug-105355-4-irlEBnjGS8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105355-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Liska <marxin@gcc.gnu.org>:

https://gcc.gnu.org/g:9e1e962eac8d2a28fcd648a0f5c8eb0022abd8e4

commit r13-282-g9e1e962eac8d2a28fcd648a0f5c8eb0022abd8e4
Author: Martin Liska <mliska@suse.cz>
Date:   Tue Apr 26 11:41:09 2022 +0200

    opts: do not allow Separate+Joined ending with =

    Do not allow strange option format:
    -msmall-data-limit= 11.

    For -output-pch we need to use Separate syntax as lang spec
    rules automatically append a space.

            PR target/105355

    gcc/ChangeLog:

            * config/riscv/riscv.opt: Remove Separate from
            -msmall-data-limit=.
            * optc-gen.awk: Report error for the described situation.
            * gcc.cc: Use Separate syntax.
            * opts.cc (gen_command_line_string): Change option name.

    gcc/c-family/ChangeLog:

            * c-opts.cc (c_common_handle_option): Change option name.
            * c.opt: Remove Joined and use Separate option.

    gcc/cp/ChangeLog:

            * lang-specs.h: Use Separate syntax.

    gcc/objc/ChangeLog:

            * lang-specs.h: Use Separate syntax.

    gcc/objcp/ChangeLog:

            * lang-specs.h: Use Separate syntax.

  parent reply	other threads:[~2022-05-11  6:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-22 23:20 [Bug driver/105355] New: " izbyshev at ispras dot ru
2022-04-26  9:31 ` [Bug target/105355] " marxin at gcc dot gnu.org
2022-04-26  9:35 ` marxin at gcc dot gnu.org
2022-04-26  9:39 ` marxin at gcc dot gnu.org
2022-04-26 10:06 ` izbyshev at ispras dot ru
2022-05-11  6:56 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-11  6:57 ` marxin at gcc dot gnu.org
2022-05-11 15:46 ` palmer 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-105355-4-irlEBnjGS8@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).