================ @@ -0,0 +1,62 @@ +//===-- Definition of macros from endian.h --------------------------------===// +// +// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions. +// See https://llvm.org/LICENSE.txt for license information. +// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception +// +//===----------------------------------------------------------------------===// + +#ifndef __CLANG_ENDIAN_H +#define __CLANG_ENDIAN_H + +// If the system has an endian.h, let's use that instead. +#if __STDC_HOSTED__ && __has_include_next(<endian.h>) ---------------- AaronBallman wrote:
I realize my question was phrased stupidly, sorry for the confusion! Thank you for prodding me to ask it better. What is the justification for not including from the platform when in freestanding specifically? e.g., if the platform provides an `endian.h` header in a freestanding environment, wouldn't we want that definition for the target instead of our own (in general) for the same reasons we prefer the platform in a hosted environment? (Perhaps I'm asking for something stupid, maybe this situation doesn't come up?) https://github.com/llvm/llvm-project/pull/186032 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
