On Thu, Jun 30, 2016 at 01:41:00PM -0700, Richard Smith wrote:
> On Thu, Jun 30, 2016 at 2:02 AM, David Chisnall > wrote:
>
> > On 29 Jun 2016, at 23:07, Richard Smith via cfe-dev <
> > cfe-...@lists.llvm.org> wrote:
> > >
> > > Yes, those are real problems, but it's not reasonable for us to keep
It doesn't break anything for us and in general the proposal make sense to
me.
Yours,
Andrey
=
Software Engineer
Intel Compiler Team
On Wed, Jun 29, 2016 at 10:09 PM, Richard Smith via cfe-commits <
cfe-commits@lists.llvm.org> wrote:
> Hi all!
>
> I'd like to establish a policy for Clang's
On Thu, Jun 30, 2016 at 2:02 AM, David Chisnall wrote:
> On 29 Jun 2016, at 23:07, Richard Smith via cfe-dev <
> cfe-...@lists.llvm.org> wrote:
> >
> > Yes, those are real problems, but it's not reasonable for us to keep the
> default at C++98/03 forever. GCC has already taken the plunge here, so
On 29 Jun 2016, at 23:07, Richard Smith via cfe-dev
wrote:
>
> Yes, those are real problems, but it's not reasonable for us to keep the
> default at C++98/03 forever. GCC has already taken the plunge here, so a lot
> of open-source code that doesn't work in C++11 onwards already explicitly
>
mary
libraries that Clang should care about, so we'll probably continue having our
own target-specific default anyway.
--paulr
From: Ristow, Warren
Sent: Wednesday, June 29, 2016 6:07 PM
To: Sean Silva; Richard Smith
Cc: cfe-commits; Clang Dev; Robinson, Paul
Subject: RE: RFC: Default language
y case basis.
-Warren Ristow
From: Sean Silva [mailto:chisophu...@gmail.com]
Sent: Wednesday, June 29, 2016 1:35 PM
To: Richard Smith
Cc: cfe-commits; Clang Dev; Ristow, Warren; Robinson, Paul
Subject: Re: RFC: Default language standard mode policy
On Wed, Jun 29, 2016 at 1:34 PM, Sean Silv
On Wed, Jun 29, 2016 at 03:07:33PM -0700, Richard Smith wrote:
> On Wed, Jun 29, 2016 at 2:48 PM, Joerg Sonnenberger via cfe-commits <
> cfe-commits@lists.llvm.org> wrote:
>
> > On Wed, Jun 29, 2016 at 12:09:37PM -0700, Richard Smith via cfe-dev wrote:
> > > Hi all!
> > >
> > > I'd like to establi
On Wed, Jun 29, 2016 at 2:48 PM, Joerg Sonnenberger via cfe-commits <
cfe-commits@lists.llvm.org> wrote:
> On Wed, Jun 29, 2016 at 12:09:37PM -0700, Richard Smith via cfe-dev wrote:
> > Hi all!
> >
> > I'd like to establish a policy for Clang's default language standard (if
> > none is specified w
- Original Message -
> From: "Hal Finkel via cfe-dev"
> To: "Richard Smith"
> Cc: "Clang Dev" , "cfe-commits"
>
> Sent: Wednesday, June 29, 2016 4:17:18 PM
> Subject: Re: [cfe-dev] RFC: Default language standard mode policy
On Wed, Jun 29, 2016 at 12:09:37PM -0700, Richard Smith via cfe-dev wrote:
> Hi all!
>
> I'd like to establish a policy for Clang's default language standard (if
> none is specified with -std), as follows:
>
> Clang defaults to the most recent published standard for the selected
> language that
- Original Message -
> From: "Richard Smith"
> To: "Hal Finkel"
> Cc: "Clang Dev" , "cfe-commits"
>
> Sent: Wednesday, June 29, 2016 3:01:46 PM
> Subject: Re: [cfe-dev] RFC: Default language standard mode policy
> On
On Wed, Jun 29, 2016 at 1:34 PM, Sean Silva wrote:
>
>
> On Wed, Jun 29, 2016 at 12:51 PM, Richard Smith
> wrote:
>
>> On Wed, Jun 29, 2016 at 12:30 PM, Sean Silva
>> wrote:
>>
>>>
>>>
>>> On Wed, Jun 29, 2016 at 12:09 PM, Richard Smith via cfe-commits <
>>> cfe-commits@lists.llvm.org> wrote:
>
On Wed, Jun 29, 2016 at 12:51 PM, Richard Smith
wrote:
> On Wed, Jun 29, 2016 at 12:30 PM, Sean Silva
> wrote:
>
>>
>>
>> On Wed, Jun 29, 2016 at 12:09 PM, Richard Smith via cfe-commits <
>> cfe-commits@lists.llvm.org> wrote:
>>
>>> Hi all!
>>>
>>> I'd like to establish a policy for Clang's defa
t; *Sent: *Wednesday, June 29, 2016 2:09:37 PM
> *Subject: *RFC: Default language standard mode policy
>
> Hi all!
>
> I'd like to establish a policy for Clang's default language standard (if
> none is specified with -std), as follows:
>
> Clang defaults to
- Original Message -
> From: "Richard Smith via cfe-commits"
> To: "cfe-commits" , "Clang Dev"
>
> Sent: Wednesday, June 29, 2016 2:09:37 PM
> Subject: RFC: Default language standard mode policy
> Hi all!
> I'd like to establ
On Wed, Jun 29, 2016 at 12:47 PM Nico Weber via cfe-commits <
cfe-commits@lists.llvm.org> wrote:
> On Wed, Jun 29, 2016 at 3:25 PM, Richard Smith
> wrote:
>
>> Note that at this point I'd like to mainly focus on what our policy
>> should be;
>>
>
> Fair enough. I don't have a strong opinion on th
On Wed, Jun 29, 2016 at 12:30 PM, Sean Silva wrote:
>
>
> On Wed, Jun 29, 2016 at 12:09 PM, Richard Smith via cfe-commits <
> cfe-commits@lists.llvm.org> wrote:
>
>> Hi all!
>>
>> I'd like to establish a policy for Clang's default language standard (if
>> none is specified with -std), as follows:
On Wed, Jun 29, 2016 at 3:25 PM, Richard Smith
wrote:
> On Wed, Jun 29, 2016 at 12:14 PM, Nico Weber wrote:
>
>> For clang-cl, we should follow cl's model of selecting a standard. Before
>> C++17, this was "use newest language the compiler knows about" (keyed off
>> -fmsc-version; clang-cl detec
On Wed, Jun 29, 2016 at 12:09 PM, Richard Smith via cfe-commits <
cfe-commits@lists.llvm.org> wrote:
> Hi all!
>
> I'd like to establish a policy for Clang's default language standard (if
> none is specified with -std), as follows:
>
> Clang defaults to the most recent published standard for the
On Wed, Jun 29, 2016 at 12:14 PM, Nico Weber wrote:
> For clang-cl, we should follow cl's model of selecting a standard. Before
> C++17, this was "use newest language the compiler knows about" (keyed off
> -fmsc-version; clang-cl detects the system msvc version by default if
> that's not passed i
For clang-cl, we should follow cl's model of selecting a standard. Before
C++17, this was "use newest language the compiler knows about" (keyed off
-fmsc-version; clang-cl detects the system msvc version by default if
that's not passed in). After C++17, there's an explicit language flag, and
we use
Hi all!
I'd like to establish a policy for Clang's default language standard (if
none is specified with -std), as follows:
Clang defaults to the most recent published standard for the selected
language that it fully implements.
The practical impact of this is that clang++ will default to C++14
22 matches
Mail list logo
