Displaying 7 results from an estimated 7 matches for "n3276".
Did you mean:
3276
2013 Jan 13
2
[LLVMdev] Using C++'11 language features in LLVM itself
...capabilities by themselves.
>
>
> -- Matthieu.
>
>
> PS: thanks to Stephen Kelly for showing me how to use gmane to barge in.
>
> [1]: http://wiki.apache.org/stdcxx/C%2B%2B0xCompilerSupport
>
> [2]: "decltype v1.0 (n2343)" is subsided by "decltype v1.1 (n3276)" which drops
> the completeness requirement of return types; unfortunately it seems no known
> version of gcc implements v1.1.
>
> [3]: "r-value v2.1 (n2844 + core issue 1138)" is subsided by "r-value v3.0
> (n3053)" but I could not understand the gist of th...
2013 Jan 13
0
[LLVMdev] Using C++'11 language features in LLVM itself
...heck the Apache page summing up the compiler
capabilities by themselves.
-- Matthieu.
PS: thanks to Stephen Kelly for showing me how to use gmane to barge in.
[1]: http://wiki.apache.org/stdcxx/C%2B%2B0xCompilerSupport
[2]: "decltype v1.0 (n2343)" is subsided by "decltype v1.1 (n3276)" which drops
the completeness requirement of return types; unfortunately it seems no known
version of gcc implements v1.1.
[3]: "r-value v2.1 (n2844 + core issue 1138)" is subsided by "r-value v3.0
(n3053)" but I could not understand the gist of the differences; furthermo...
2013 Jan 13
0
[LLVMdev] Using C++'11 language features in LLVM itself
...t;>
>> -- Matthieu.
>>
>>
>> PS: thanks to Stephen Kelly for showing me how to use gmane to barge in.
>>
>> [1]: http://wiki.apache.org/stdcxx/C%2B%2B0xCompilerSupport
>>
>> [2]: "decltype v1.0 (n2343)" is subsided by "decltype v1.1 (n3276)" which drops
>> the completeness requirement of return types; unfortunately it seems no known
>> version of gcc implements v1.1.
>>
>> [3]: "r-value v2.1 (n2844 + core issue 1138)" is subsided by "r-value v3.0
>> (n3053)" but I could not under...
2013 Jan 11
4
[LLVMdev] Using C++'11 language features in LLVM itself
On Fri, Jan 11, 2013 at 11:32 AM, Sebastian Redl
<sebastian.redl at getdesigned.at> wrote:
>
> On 11.01.2013, at 20:08, Eli Bendersky wrote:
>
>>>> I suppose this tradeoff can be evaluated by looking at the delta
>>>> between 4.5 and 4.6 which is actually supported by MSVC 2010 and Clang
>>>> 3.1
>>>
>>> Makes perfect sense to
2013 Jan 13
0
[LLVMdev] Using C++'11 language features in LLVM itself
...2.0 [3]
- static_assert
- built-in type traits
The only issue I can see is that a number of people emitted the idea that
gcc 4.5 might be too advanced for a number of platforms (including RedHat
for example).
-- Matthieu
[1]: "decltype v1.0 (n2343)" is subsided by "decltype v1.1 (n3276)" which
drops the completeness requirement of return types; unfortunately it seems
no released version of gcc implements v1.1.
[2]: "lambda v1.0 (n2658)" is subsided by "lambda v1.1 (n2927)", not sure
of the exact impact of the changes.
[3]: "r-value v2.0 (n2844)&quo...
2013 Jan 13
5
[LLVMdev] Using C++'11 language features in LLVM itself
On Sun, Jan 13, 2013 at 10:26 AM, Tim Northover <t.p.northover at gmail.com> wrote:
>> Good points David, I don't feel qualified to evaluate the differences
>> between those versions though... Perhaps Richard or Doug could comment here?
>
> Unless I'm misreading the buildbots, we don't actually have anything
> trying to build with MSVC. Have we considered how
2013 Jan 13
2
[LLVMdev] Using C++'11 language features in LLVM itself
...gt;>
> >>
> >> PS: thanks to Stephen Kelly for showing me how to use gmane to barge in.
> >>
> >> [1]: http://wiki.apache.org/stdcxx/C%2B%2B0xCompilerSupport
> >>
> >> [2]: "decltype v1.0 (n2343)" is subsided by "decltype v1.1 (n3276)"
> which drops
> >> the completeness requirement of return types; unfortunately it seems no
> known
> >> version of gcc implements v1.1.
> >>
> >> [3]: "r-value v2.1 (n2844 + core issue 1138)" is subsided by "r-value
> v3.0
> >...