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 objc/108743] -fconstant-cfstrings not supported
Date: Sun, 12 Feb 2023 16:48:52 +0000 [thread overview]
Message-ID: <bug-108743-4-sZTWDglQR1@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 #8 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #7)
> Hmm,
> https://inbox.sourceware.org/gcc-patches/B4F496F4-F31D-41D2-8942-
> 1F0AEFBD7BBF@sandoe-acoustics.co.uk/
>
> Seems didn't get installed even though it was approved ...
these things happen, I guess we can make it a darwin-specific driver option (as
Jakub says, the 'm' version is technically correct, but we have to accommodate
compatibility sometimes).
There is at least one other platform that I think it s using the NeXT library
(it is open sourced), so maybe it is an appropriate option for that platform
too.
next prev parent reply other threads:[~2023-02-12 16:48 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 [this message]
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-sZTWDglQR1@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).