libgcc c++ support bits moved
Mon Oct 9 15:21:00 GMT 2000
> Date: Mon, 9 Oct 2000 15:10:39 -0700
> From: Richard Henderson <email@example.com>
> On Tue, Oct 10, 2000 at 12:02:54AM +0200, Hans-Peter Nilsson wrote:
> > Targets that need to add multilibbed files to libgcc2 can
> > otherwise not compile those files with options other than for
> > the rest of libgcc2
> You'll have to give me an example. Why in the world would
> you multilib something, but then try to include files with
> different options than the multilib calls for?
I need to add files compiled with an extra option,
e.g. -mexpand-mul (yeah, it's sort of libgcc1, but libgcc1 does
not work for cross and it's only multilibbed for asm anyway).
The rest of libgcc2 must not be compiled with that flag.
So it's *added* options rather than *other* options.
Is there another (simpler) way?
More information about the Gcc-patches