This sounds very similar to the immintrin.h etc headers that Intel provides, which IMO are great. We don't have to implement everything as a builtin in the compiler. We can insulate ourselves with a header layer.
GCC's __builtins aren't standard, so having a real document seems like a step forward. -- from a peanut gallery somewhere On Wed, Jun 25, 2014 at 2:44 PM, Saleem Abdulrasool <[email protected]> wrote: > Im sure that Im missing some context here. I am not sure what using this > wrapper header to map the intrinsics to a __builtin_ form really gains. It > adds an additional header that needs to be maintained, and requires that > users include this header for the intrinsics. > > At the very least, similar approaches to this on the Windows side have > proven to be less than ideal. > > Having some additional context around why this is preferable would be nice. > > http://reviews.llvm.org/D4296 > > > > _______________________________________________ > cfe-commits mailing list > [email protected] > http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits >
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
