public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug objc/108743] -fconstant-cfstrings not supported
Date: Thu, 09 Feb 2023 16:45:57 +0000	[thread overview]
Message-ID: <bug-108743-4-kdzhiaDYm0@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 #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Pierre Ossman from comment #2)
> Great news. And that is the same thing as clang's -fconstant-cfstrings?

yes

> 
> Unfortunately, I couldn't see -mconstant-cfstrings in gcc's documentation,
> but I may be looking in the wrong place.

and it is just missing.

Also are you trying to compile for darwin (Mac OS X) or some other target?
If some other target, then these options are not there.

  parent reply	other threads:[~2023-02-09 16:45 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 [this message]
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
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-kdzhiaDYm0@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).