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 present*, but certainly the eventual aim should be to move them. Before more macros are moved to files in libgcc/config I'd really rather the libgcc headers go in a separate libgcc_tm_file or similar, not included on the host and with the moved macros poisoned in the host system.h, to avoid the situation listed on that page of "RENAME_LIBRARY (in gcc/config/arm/symbian.h, otherwise moved to libgcc headers)" where a macro is only partly migrated to the libgcc headers but this partial state isn't obvious. This has the advantage of avoiding the ../../libgcc/config/ kludge in tm_file as well. -- Joseph S. Myers jos...@codesourcery.com
