Re: *_ALIGN_MAX_SKIP macros

2010-10-19 Thread DJ Delorie
> This is OK if you add LABEL_ALIGN_MAX_SKIP, LOOP_ALIGN_MAX_SKIP, > LABEL_ALIGN_AFTER_BARRIER_MAX_SKIP, and JUMP_ALIGN_MAX_SKIP to the > > /* Old target macros that have moved to the target hooks structure. */ > > #pragma GCC poison list in system.h. Thanks, committed with that change.

Re: *_ALIGN_MAX_SKIP macros

2010-10-12 Thread Ian Lance Taylor
DJ Delorie writes: > * doc/tm.texi.in (TARGET_ASM_JUMP_ALIGN_MAX_SKIP): New. > (TARGET_ASM_LABEL_ALIGN_AFTER_BARRIER_MAX_SKIP): Change to hook. > (TARGET_ASM_LOOP_ALIGN_MAX_SKIP): Likewise. > (TARGET_ASM_LABEL_ALIGN_MAX_SKIP): Likewise. > > * targhooks.h (default_lab

Re: *_ALIGN_MAX_SKIP macros

2010-10-05 Thread DJ Delorie
> DJ Delorie writes: > > JUMP_ALIGN_MAX_SKIP > > LABEL_ALIGN_AFTER_BARRIER_MAX_SKIP > > LOOP_ALIGN_MAX_SKIP > > LABEL_ALIGN_MAX_SKIP > > > > None of these macros take any parameters, but for optimal performance > > on RX, it's key to match the max_skip with the size of the following > > opcod

Re: *_ALIGN_MAX_SKIP macros

2010-07-27 Thread Ian Lance Taylor
DJ Delorie writes: > JUMP_ALIGN_MAX_SKIP > LABEL_ALIGN_AFTER_BARRIER_MAX_SKIP > LOOP_ALIGN_MAX_SKIP > LABEL_ALIGN_MAX_SKIP > > None of these macros take any parameters, but for optimal performance > on RX, it's key to match the max_skip with the size of the following > opcode - there's a pena

*_ALIGN_MAX_SKIP macros

2010-07-27 Thread DJ Delorie
JUMP_ALIGN_MAX_SKIP LABEL_ALIGN_AFTER_BARRIER_MAX_SKIP LOOP_ALIGN_MAX_SKIP LABEL_ALIGN_MAX_SKIP None of these macros take any parameters, but for optimal performance on RX, it's key to match the max_skip with the size of the following opcode - there's a penalty only if you branch to an opcode