This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: [RFA:] Mention simtest-howto.html in contribute.html


On Mon, 5 Nov 2001, Gerald Pfeifer wrote:
> On Sat, 3 Nov 2001, Hans-Peter Nilsson wrote:
> > --- 86,94 ----
> >   <dd>
> >   A list of targets where the patch survived a bootstrap of GCC.  A
> >   bootstrap on at least one host is required for any non-trivial change.  A
> > ! full GCC testsuite run is also required.  It is recommended that
> > ! you also <a href="simtest-howto.html">use one or more simulators</a> to
> > ! increase your test coverage.  With your patch, provide a
> >   list of hosts where the GCC testsuite was run, including an analysis
> >   of any regressions.  Documentation changes do not require a bootstrap,
> >   but must pass <code>make info</code> and <code>make dvi</code>.
>
> I'd just say "(You can also use one or more simulators to... coverage)",
> because I feel that actually recommonding them is a bit too much for most
> patches.

Thanks.  Right, people reading contribute.html don't usually
rewrite half of gcc, so for the occasional <-10-lines-patch it
would sound a bit too tough.  I installed with that change: s/It
is recommended that you/You can/.

I really think generic "middle-end" changes should be tested on
as many distinctive targets as can be found, rather than just
one or two.  It can be automated to a large extent and
simulators help with that, so I do recommend it there.  End of
rantlet.

brgds, H-P


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]