Re: Completing toplevel libgcc move

2011-05-26 Thread Rainer Orth
"Joseph S. Myers" writes: > On Thu, 26 May 2011, Rainer Orth wrote: > >> But doesn't this mean that e.g. MD_UNWIND_SUPPORT can only be moved to >> libgcc/config for all targets together? How can you poison the macro >> when a single target using it is left behind in gcc/config? > > Nothing about

Re: Completing toplevel libgcc move (Was: Re: [SPARC] Hookize PRINT_OPERAND, PRINT_OPERAND_ADDRESS and PRINT_OPERAND_PUNCT_VALID_P)

2011-05-26 Thread Joseph S. Myers
On Thu, 26 May 2011, Rainer Orth wrote: > But doesn't this mean that e.g. MD_UNWIND_SUPPORT can only be moved to > libgcc/config for all targets together? How can you poison the macro > when a single target using it is left behind in gcc/config? Nothing about the libgcc_tm.h implementation stops

Completing toplevel libgcc move (Was: Re: [SPARC] Hookize PRINT_OPERAND, PRINT_OPERAND_ADDRESS and PRINT_OPERAND_PUNCT_VALID_P)

2011-05-26 Thread Rainer Orth
"Joseph S. Myers" writes: > On Wed, 4 May 2011, Rainer Orth wrote: > >> Your expansion of the wiki page on toplevel libgcc migration is >> certainly welcome: I hadn't seen before that *-unwind.h files and >> related macros can be moved over as well. > > I've no idea whether they can be moved *at