[buildrobot] microblaze-elf / microblaze-linux
Joseph S. Myers
joseph@codesourcery.com
Tue Nov 26 16:52:00 GMT 2013
On Tue, 26 Nov 2013, Jan-Benedict Glaw wrote:
> > The idea if config-list.mk is not to build every conceivable target
> > configuration, but to give a reasonable converage of the different
> > target architectures and OS/library configurations so that you can
> > effectively test a patch with unknown target-specific impact.
>
> Is it like that? My impression is/was that people collected a list of
> targets they somewhat care for. With around 200 configurations, among
> them some that are quite similar, adding another just adds 1/2%, which
> I'd call neglectible.
For example, the list should include at least one target for every target
header in GCC. So if there's a header specific to an (architecture, OS)
pair, a matching configuration should be included.
--
Joseph S. Myers
joseph@codesourcery.com
More information about the Gcc
mailing list