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]
Other format: [Raw text]

Re: [lto] PATCH: more CALL_EXPR-related changes


Sandra Loosemore <sandra@codesourcery.com> writes:

> If the
> size of the patches is the problem rather than their complexity, would
> it be better if I prepared and committed the patch for each file
> separately instead of bunching together each day's work?

Yes, I think that would be better.  Look at Kazu's messages.

These changes are in general obvious and trivial.  But we know that a
bootstrap and testsuite don't come close to complete code coverage of
gcc, so it's a good idea to have other eyes look at these patches to
make sure that a 1 didn't accidentally become a 0 or something like
that.  That's hard to do with such large patches.

Ian


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