Re: Link more common objects consistently into host programs

2011-05-20 Thread Tom Tromey
> "Joseph" == Joseph S Myers writes: Joseph> 2011-05-20 Joseph Myers Joseph> * Make-lang.in ($(XGCJ)$(exeext)): Don't explicitly use intl.o and Joseph> version.o. Joseph> (JCFDUMP_OBJS): Remove errors.o, version.o and intl.o. Joseph> (JVGENMAIN_OBJS): Remov

Re: Link more common objects consistently into host programs

2011-05-20 Thread Rainer Orth
"Joseph S. Myers" writes: > I haven't tested building mips-tdump or mips-tfile with this patch, > but don't think it should cause any problems as the static linker > should just ignore the diagnostics objects for those programs. In > principle mips-tfile should use the common code instead of its

Re: Link more common objects consistently into host programs

2011-05-20 Thread Gabriel Dos Reis
On Fri, May 20, 2011 at 7:21 AM, Joseph S. Myers wrote: > There are an increasing number of common object files that get linked > into a range of programs GCC builds and installs for the host, > including but not limited to the core compilers and the drivers. the diagnostic part is OK.

Re: Link more common objects consistently into host programs

2011-05-20 Thread Paolo Bonzini
On 05/20/2011 02:21 PM, Joseph S. Myers wrote: 2011-05-20 Joseph Myers * Makefile.in (LIBDEPS): Add libcommon.a. (LIBS): Likewise. (GCC_OBJS): Remove diagnostic.o, pretty-print.o and input.o. (OBJS-common): Remove diagnostic.o, input.o, intl.o, pretty-pri

Link more common objects consistently into host programs

2011-05-20 Thread Joseph S. Myers
There are an increasing number of common object files that get linked into a range of programs GCC builds and installs for the host, including but not limited to the core compilers and the drivers. These have various ad hoc code listing them explicitly for each program using some of them, with the