From: Mike Stump <mikestump@comcast.net>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: Joseph Myers <joseph@codesourcery.com>, gcc-patches@gcc.gnu.org
Subject: Re: [patch 2/6] scalar-storage-order merge: C front-end
Date: Wed, 28 Oct 2015 23:36:00 -0000 [thread overview]
Message-ID: <397D9865-1C80-47D9-9F35-65BBD7D0B71C@comcast.net> (raw)
In-Reply-To: <3373064.npvgOm9vCi@polaris>
On Oct 28, 2015, at 3:04 PM, Eric Botcazou <ebotcazou@adacore.com> wrote:
>> Why is -fsso-struct= listed only for C and C++, not ObjC and ObjC++?
>
> Because it was not tested with the latter 2 languages at all and may require
> specific adjustments in the respective front-ends to work.
It won’t. Fixing the language line for the options and a make to ensure it still builds for you is enough testing.
>> Almost all C options should be supported for ObjC and almost all C++
>> options should be supported for ObjC++ (and the existing cases that aren't
>> in c.opt generally look dubious).
>
> Sorry, I have zero experience with ObjC and objC++, let alone their front-end.
None is needed. One merely copies the string as found on other options for your new options, and you’re done. Indeed, the default should be to always include the objective languages unless one goes out of their way to exclude them.
next prev parent reply other threads:[~2015-10-28 23:19 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 10:57 [patch 0/6] scalar-storage-order merge (2) Eric Botcazou
2015-10-06 11:01 ` [patch 1/6] scalar-storage-order merge: Ada front-end Eric Botcazou
2015-10-12 22:23 ` Jeff Law
2015-10-06 11:02 ` [patch 2/6] scalar-storage-order merge: C front-end Eric Botcazou
2015-10-13 11:32 ` Jeff Law
2015-10-19 8:50 ` Eric Botcazou
2015-10-28 16:48 ` Joseph Myers
2015-10-28 17:32 ` Jeff Law
2015-10-28 22:34 ` Eric Botcazou
2015-10-28 23:36 ` Mike Stump [this message]
2015-10-29 0:23 ` Joseph Myers
2015-10-30 8:59 ` Eric Botcazou
2015-10-30 14:50 ` Mike Stump
2015-10-06 11:03 ` [patch 3/6] scalar-storage-order merge: C++ front-end Eric Botcazou
2015-10-12 22:27 ` Jeff Law
2015-10-06 11:05 ` [patch 4/6] scalar-storage-order merge: bulk Eric Botcazou
2015-10-13 16:07 ` Jeff Law
2015-10-20 16:35 ` Eric Botcazou
2015-10-06 11:06 ` [patch 5/6] scalar-storage-order merge: rest Eric Botcazou
2015-10-06 11:09 ` Eric Botcazou
2015-10-13 16:44 ` Jeff Law
2015-10-06 11:08 ` [patch 6/6] scalar-storage-order merge: testsuite Eric Botcazou
2015-10-12 22:26 ` Jeff Law
2015-10-09 11:33 ` [patch 0/6] scalar-storage-order merge (2) Bernd Schmidt
2015-10-13 17:33 ` Eric Botcazou
2015-10-14 15:25 ` Trevor Saunders
2015-10-14 15:33 ` Jeff Law
2015-11-08 18:30 ` Eric Botcazou
-- strict thread matches above, loose matches on Subject: below --
2015-06-16 8:46 [patch 0/6] scalar-storage-order merge Eric Botcazou
2015-06-16 8:56 ` [patch 2/6] scalar-storage-order merge: C front-end Eric Botcazou
2015-06-16 9:07 ` Ramana Radhakrishnan
2015-06-16 9:11 ` Andrew Pinski
2015-06-18 19:16 ` Eric Botcazou
2015-06-16 11:39 ` Richard Sandiford
2015-06-18 19:17 ` Eric Botcazou
2015-06-16 21:25 ` Joseph Myers
2015-06-19 9:36 ` Eric Botcazou
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=397D9865-1C80-47D9-9F35-65BBD7D0B71C@comcast.net \
--to=mikestump@comcast.net \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
/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).