This is the mail archive of the gcc@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: ACATS


    The point of using the vendor branch is to have *both* the original form
    (on the vendor branch) and the GCC version (on the mainline) in CVS - and
    when a new version is imported onto the vendor branch, CVS should be able
    to help with a lot of the work of merging onto the mainline.  The CVS
    experts here can probably provide step-by-step instructions for doing this
    and indications of the pitfalls.

I think there's a disconnect here.

The issue is that the *format*, not the *content*, of the two branches
is fundamentally different.  The ACATS cvs contains one file per test
while the GCC ACATS cvs would contain one file per *compilation unit*
and there are often multiple such per test.


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