This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] PR opt/6627: New target macro MINIMUM_FUNCTION_BOUNDARY

On Sun, Sep 29, 2002 at 12:51:55PM -0600, Roger Sayle wrote:
> The problem is that TARGET_PTRMEMFUNC_VBIT_LOCATION is defined
> in terms of FUNCTION_BOUNDARY [line 472 of defaults.h].

Yes, but that's ifndef.  One would force the ABI one 
desired in the target header.

> Infact this is the only other use of FUNCTION_BOUNDARY in CVS,
> so this would contradict your claim that this is used in
> optimizations.

Untrue.

builtins.c:211:     align = FUNCTION_BOUNDARY;
c-common.c:3061:        value = size_int (FUNCTION_BOUNDARY / BITS_PER_UNIT);
tree.c:1277:      return FUNCTION_BOUNDARY;


r~
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]