From: Jonathan Wakely <jwakely@redhat.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: Joseph Myers <joseph@codesourcery.com>,
gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org,
libstdc++@gcc.gnu.org
Subject: Re: Link with correct values-*.o files on Solaris (PR target/40411)
Date: Tue, 30 Jan 2018 15:05:00 -0000 [thread overview]
Message-ID: <20180130150445.GS3417@redhat.com> (raw)
In-Reply-To: <yddr2q7e6xr.fsf@CeBiTec.Uni-Bielefeld.DE>
On 30/01/18 15:51 +0100, Rainer Orth wrote:
>Hi Joseph,
>
>> On Tue, 30 Jan 2018, Rainer Orth wrote:
>>
>>> So it seems the following snippet
>>>
>>> #define STARTFILE_ARCH_SPEC \
>>> [...]
>>> %{std=c9*|std=iso9899\\:199409|std=c1*:values-Xc.o%s; :values-Xa.o%s} \
>>>
>>> seems like the right thing to do, as you said.
>>
>> That version would need updating when we add -std=c2x (once there's a C2x
>> working draft with features being added to it). If you use std=c* instead
>> of separate std=c9* and std=c1* you'd avoid needing such a change - but
>> then of course it would cover -std=c++* for C++.
>
>I know, that why I used the current form. Admittedly it's a maintenance
>problem (likely to be forgotten in the future). If we add in -ansi, we
>can just as well add -std=c++* (thus -std=c*), too.
>
>I guess that's the safest option overall, unless Jonathan has objections
>from a C++ standards perspective.
No objections from me, I'm happy either way.
next prev parent reply other threads:[~2018-01-30 15:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 9:59 Rainer Orth
2018-01-12 17:46 ` Joseph Myers
2018-01-30 14:03 ` Rainer Orth
2018-01-30 14:43 ` Joseph Myers
2018-01-30 14:51 ` Rainer Orth
2018-01-30 15:05 ` Jonathan Wakely [this message]
2018-01-30 21:21 ` Rainer Orth
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=20180130150445.GS3417@redhat.com \
--to=jwakely@redhat.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=libstdc++@gcc.gnu.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).