[llvm-dev] Do we still need the self move protection in APInt's move assignment operator? (original) (raw)
陳韋任 via llvm-dev llvm-dev at lists.llvm.org
Sun Apr 2 15:10:01 PDT 2017
- Previous message: [llvm-dev] Do we still need the self move protection in APInt's move assignment operator?
- Next message: [llvm-dev] Do we still need the self move protection in APInt's move assignment operator?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I think so. Besides, recommended VS version is VS 2015 [1], the bug should be long gone.
[1] http://llvm.org/docs/GettingStarted.html#host-c-toolchain-both-compiler-and-standard-library
Regards, chenwj
-- Wei-Ren Chen (陳韋任) Homepage: https://people.cs.nctu.edu.tw/~chenwj
2017-04-03 3:28 GMT+08:00 Craig Topper via llvm-dev <llvm-dev at lists.llvm.org>:
The comment says it was added due to a bug in MSVC 2013 implementation of stablesort. Newer versions of MSVC have fixed this bug in stablesort according to this webpage record https://connect.microsoft.com/VisualStudio/feedback/details/886652
Can we remove the check now? ~Craig
LLVM Developers mailing list llvm-dev at lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
- Previous message: [llvm-dev] Do we still need the self move protection in APInt's move assignment operator?
- Next message: [llvm-dev] Do we still need the self move protection in APInt's move assignment operator?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]