699946ae61
- The macro __BIGGEST_ALIGNMENT__ is gcc-specific. If it is not defined we'll just assume 16. This is correct for at least the common cases and LLVM does not provide an equivalent macro. - When linking U-Boot we're passing -T to the linker, and while gcc will just pass this along with LLVM we need to be specific. Cc: Simon Glass <sjg@chromium.org> Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org>
24 lines
670 B
C
24 lines
670 B
C
/*
|
|
* Copyright (c) 2011 The Chromium OS Authors.
|
|
*
|
|
* SPDX-License-Identifier: GPL-2.0+
|
|
*/
|
|
|
|
#ifndef __SANDBOX_CACHE_H__
|
|
#define __SANDBOX_CACHE_H__
|
|
|
|
/*
|
|
* For native compilation of the sandbox we should still align
|
|
* the contents of stack buffers to something reasonable. The
|
|
* GCC macro __BIGGEST_ALIGNMENT__ is defined to be the maximum
|
|
* required alignment for any basic type. This seems reasonable.
|
|
* This is however GCC specific so if we don't have that available
|
|
* assume that 16 is large enough.
|
|
*/
|
|
#ifdef __BIGGEST_ALIGNMENT__
|
|
#define ARCH_DMA_MINALIGN __BIGGEST_ALIGNMENT__
|
|
#else
|
|
#define ARCH_DMA_MINALIGN 16
|
|
#endif
|
|
|
|
#endif /* __SANDBOX_CACHE_H__ */
|