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/108743] [objective-c, NeXT runtime] -fconstant-cfstrings not supported
Date: Sun, 17 Mar 2024 03:27:40 +0000	[thread overview]
Message-ID: <bug-108743-4-2HImRxbhvo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108743-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Iain D Sandoe
<iains@gcc.gnu.org>:

https://gcc.gnu.org/g:87152f50a89deb5044145a80fa2ed705f4913f98

commit r11-11283-g87152f50a89deb5044145a80fa2ed705f4913f98
Author: Iain Sandoe <iain@sandoe.co.uk>
Date:   Sun Jul 2 14:18:04 2023 +0100

    Darwin, Objective-C: Support -fconstant-cfstrings [PR108743].

    This support the -fconstant-cfstrings option as used by clang (and
    expect by some build scripts) as an alias to the target-specific
    -mconstant-cfstrings.

    The documentation is also updated to reflect that the 'f' option is
    only available on Darwin, and to add the 'm' option to the Darwin
    section of the invocation text.

    Signed-off-by: Iain Sandoe <iain@sandoe.co.uk>

            PR target/108743

    gcc/ChangeLog:

            * config/darwin.opt: Add fconstant-cfstrings alias to
            mconstant-cfstrings.
            * doc/invoke.texi: Amend invocation descriptions to reflect
            that the fconstant-cfstrings is a target-option alias and to
            add the missing mconstant-cfstrings option description to the
            Darwin section.

    (cherry picked from commit cdd4b3c0f0f428678c24de74b1f626628450799c)

  parent reply	other threads:[~2024-03-17  3:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09 16:37 [Bug objc/108743] New: " ossman at cendio dot se
2023-02-09 16:39 ` [Bug objc/108743] " pinskia at gcc dot gnu.org
2023-02-09 16:43 ` ossman at cendio dot se
2023-02-09 16:45 ` pinskia at gcc dot gnu.org
2023-02-10  8:08 ` ossman at cendio dot se
2023-02-10  8:09 ` ossman at cendio dot se
2023-02-10  9:23 ` jakub at gcc dot gnu.org
2023-02-10 15:50 ` pinskia at gcc dot gnu.org
2023-02-12 16:48 ` iains at gcc dot gnu.org
2023-07-02 13:28 ` [Bug target/108743] [objective-c, NeXT runtime] " iains at gcc dot gnu.org
2023-07-02 14:21 ` cvs-commit at gcc dot gnu.org
2023-07-03 14:24 ` cvs-commit at gcc dot gnu.org
2023-08-05  3:54 ` egallager at gcc dot gnu.org
2024-03-17  3:23 ` cvs-commit at gcc dot gnu.org
2024-03-17  3:27 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-17  3:29 ` 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-108743-4-2HImRxbhvo@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).