Searched refs:FUNCTION_BOUNDARY (Results 1 – 14 of 14) sorted by relevance
/dragonfly/contrib/gcc-8.0/gcc/ |
H A D | function.h | 557 ? MAX (FUNCTION_BOUNDARY, 2 * BITS_PER_UNIT) : FUNCTION_BOUNDARY)
|
H A D | defaults.h | 889 (FUNCTION_BOUNDARY >= 2 * BITS_PER_UNIT \ 1061 #define TRAMPOLINE_ALIGNMENT FUNCTION_ALIGNMENT (FUNCTION_BOUNDARY)
|
H A D | stor-layout.c | 2417 int_mode_for_size (FUNCTION_BOUNDARY, 0).else_blk ()); in layout_type() 2418 TYPE_SIZE (type) = bitsize_int (FUNCTION_BOUNDARY); in layout_type() 2419 TYPE_SIZE_UNIT (type) = size_int (FUNCTION_BOUNDARY / BITS_PER_UNIT); in layout_type()
|
H A D | tree-nested.c | 500 const unsigned align = FUNCTION_ALIGNMENT (FUNCTION_BOUNDARY); in get_descriptor_type()
|
H A D | tree.c | 1044 SET_DECL_ALIGN (t, FUNCTION_ALIGNMENT (FUNCTION_BOUNDARY)); in make_node()
|
/dragonfly/contrib/gcc-4.7/gcc/ |
H A D | defaults.h | 892 (FUNCTION_BOUNDARY >= 2 * BITS_PER_UNIT \ 1129 #define TRAMPOLINE_ALIGNMENT FUNCTION_BOUNDARY
|
H A D | stor-layout.c | 2146 SET_TYPE_MODE (type, mode_for_size (FUNCTION_BOUNDARY, MODE_INT, 0)); in layout_type() 2147 TYPE_SIZE (type) = bitsize_int (FUNCTION_BOUNDARY); in layout_type() 2148 TYPE_SIZE_UNIT (type) = size_int (FUNCTION_BOUNDARY / BITS_PER_UNIT); in layout_type()
|
H A D | tree.c | 875 DECL_ALIGN (t) = FUNCTION_BOUNDARY; in make_node_stat()
|
/dragonfly/contrib/gcc-4.7/gcc/config/i386/ |
H A D | i386.h | 747 #define FUNCTION_BOUNDARY 8 macro
|
/dragonfly/contrib/gcc-8.0/gcc/config/i386/ |
H A D | i386.h | 839 #define FUNCTION_BOUNDARY 8 macro
|
/dragonfly/contrib/gcc-8.0/gcc/c-family/ |
H A D | c-common.c | 3604 value = size_int (FUNCTION_BOUNDARY / BITS_PER_UNIT); in c_sizeof_or_alignof_type()
|
/dragonfly/contrib/gcc-4.7/gcc/c-family/ |
H A D | c-common.c | 4373 value = size_int (FUNCTION_BOUNDARY / BITS_PER_UNIT); in c_sizeof_or_alignof_type()
|
/dragonfly/contrib/gcc-4.7/gcc/doc/ |
H A D | tm.texi | 1005 @defmac FUNCTION_BOUNDARY 1794 this bit using the @code{FUNCTION_BOUNDARY} setting for your platform. 1795 However, some platforms such as ARM/Thumb have @code{FUNCTION_BOUNDARY} 1804 @code{FUNCTION_BOUNDARY}, GCC will automatically define this macro to
|
H A D | tm.texi.in | 989 @defmac FUNCTION_BOUNDARY 1772 this bit using the @code{FUNCTION_BOUNDARY} setting for your platform. 1773 However, some platforms such as ARM/Thumb have @code{FUNCTION_BOUNDARY} 1782 @code{FUNCTION_BOUNDARY}, GCC will automatically define this macro to
|