This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Commit: BFIN: Fix use of VEC_last macro in bfin.c
On Fri, 17 Aug 2012, Diego Novillo wrote:
> On 12-08-17 03:10 , nick clifton wrote:
> > Hi Diego,
> > > Thanks Nick. I made the wrong fix here, sorry about that. I will be
> > > making more changes to VEC_ shortly. What's a good way for me to test
> > > them?
> >
> > All I was doing was building a variety of targets, just to make sure
> > that a local, generic patch of my own did not break anything. If you
> > have the disk space then you could try doing the same yourself.
>
> This is great. Thanks! Often the problem I have is that I don't know what
> target triplets to use. We do not have a cheat sheet handy.
The cheat sheet for testing lots of targets (testing that cc1 etc. build)
is contrib/config-list.mk. The targets there are supposed to cover all
significant variations in what target headers are used; even if people
have added target variations without always adding to the list, it's a
pretty good approximation. Note that when using this file you need to
have a recent trunk build in your PATH so that --enable-werror-always
works properly.
The baseline state is not generally 100% clean; see bug 47093 for a
meta-bug whose dependencies track known issues (some of those dependencies
may of course be out of date - that is, issues that have been fixed). It
would certainly be good to get things down to a clean state and have an
autobuilder reporting regressions building any supported target. (Of
course greater levels of testing are possible, e.g. building binutils and
seeing if libgcc builds, but getting cc1 building cleanly would be a good
first step.)
--
Joseph S. Myers
joseph@codesourcery.com