http://clang.llvm.org/get_started.html
Missing instructions to checkout llvm/projects/libcxxabi (now needed).
Howard
signature.asc
Description: Message signed with OpenPGP
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/
Very close! Comment below:
On Jan 1, 2017, at 5:04 PM, Saleem Abdulrasool via cfe-commits
wrote:
>
> Author: compnerd
> Date: Sun Jan 1 16:04:38 2017
> New Revision: 290806
>
> URL: http://llvm.org/viewvc/llvm-project?rev=290806&view=rev
> Log:
> chrono: address post commit comments from How
On Jan 1, 2017, at 3:20 PM, Saleem Abdulrasool via cfe-commits
wrote:
>
> Author: compnerd
> Date: Sun Jan 1 14:20:41 2017
> New Revision: 290803
>
> URL: http://llvm.org/viewvc/llvm-project?rev=290803&view=rev
> Log:
> chrono: implement a Windows version of system_clock::now
>
> system_clock
howard.hinnant added a comment.
Look good to me.
http://reviews.llvm.org/D21396
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
howard.hinnant added a comment.
Can't call `std::abs` as it isn't `constexpr`. You'll have to roll your own.
http://reviews.llvm.org/D21343
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-c
howard.hinnant added a comment.
I created a top-level `gcd` which did nothing but make everything unsigned and
do the abs once, and then called a `__gcd` specialized for unsigned and only
one kind of unsigned, and got measurably faster results (about 10%).
template
constexpr
std::enable_i
howard.hinnant added a comment.
A quiet nan is the right tool. A signaling nan is nothing more than a
40-year-old design flaw. A quiet nan is "sticky" in that if you try to compute
with it, the result is quiet nan. But you can assign a valid number to
something containing a quiet nan. So if
howard.hinnant added a subscriber: howard.hinnant.
howard.hinnant added a comment.
When in doubt, I find initializing to nan a safe thing to do. Either the code
is correct, or the nan will find the bug.
http://reviews.llvm.org/D19623
___
cfe-commi
On Feb 9, 2016, at 7:46 PM, Duncan P. N. Exon Smith
wrote:
>
>
>> On 2016-Feb-09, at 16:40, Howard Hinnant wrote:
>>
>> On Feb 9, 2016, at 7:17 PM, Duncan P. N. Exon Smith via cfe-commits
>> wrote:
>>>
>>> Any other ideas for improving the failure mode?
>>
>> Here’s a suggestion:
>>
>> h
On Feb 9, 2016, at 7:17 PM, Duncan P. N. Exon Smith via cfe-commits
wrote:
>
> Any other ideas for improving the failure mode?
Here’s a suggestion:
https://github.com/llvm-mirror/libcxx/blob/master/include/vector#L1658
Make this easy to activate.
Howard
_
On Jan 8, 2016, at 7:50 PM, Duncan P. N. Exon Smith
wrote:
>
> [re-send to lists.llvm.org]
> [necromancy]
>
> This is causing some strangeness for users of libc++ headers that
> ship dylibs and build with -fno-rtti and -fvisibility=hidden.
>
> Strangely, -fno-rtti does *not* imply -fno-excepti
That would destroy the timing information, but no one seems to be paying
attention to that anyway. I recommend just picking smaller buffer sizes. But
11 is too small. Small enough to pass on your embedded platform, but not in
the range of a typical alignof(max_align_t).
Howard
On Dec 16, 20
On Dec 15, 2015, at 5:30 PM, Jonathan Roelofs wrote:
>
>
> Could these large padding things be related to the fact that the test is used
> as a performance check for the implementation? That being said, I have no
> idea who is paying attention to the numbers that come out of this test (if
> a
Fwiw, if you ever here me gripe about the C++ committee’s poor record of
messing around in the C headers with detrimental effects, this is what I’m
referring to. Yes, the C++ signatures are superior. No, this wasn’t a good
thing to do. The C++ committee should not try to change or delete stuf
14 matches
Mail list logo
