This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: What is Happening with g++.dg/opt/alias1.C?
- To: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Subject: Re: What is Happening with g++.dg/opt/alias1.C?
- From: Jason Merrill <jason_merrill at redhat dot com>
- Date: 08 Aug 2001 14:34:43 +0100
- Cc: gcc-patches at gcc dot gnu dot org
- References: <10108081336.AA22535@vlsi1.ultra.nyu.edu>
>>>>> "Richard" == Richard Kenner <kenner@vlsi1.ultra.nyu.edu> writes:
> I never add entries to the testsuite ChangeLog for new tests; it seems
> pointless. I asked Mark for his thoughts on the subject, and he concurs.
> I disagree. The ChangeLog entry shows who added the test case and
> when. Yes, we can get this from CVS logs, but that's true for *all* the
> information in ChangeLog.
I believe it is different; the main ChangeLog shows the development of a
system. Changes in one part of the compiler often affect other parts, so
it makes sense to have a centralised log. You can search the ChangeLog for
interesting keywords, which you can't conveniently by searching all the
different CVS logs.
Testcases, on the other hand, are completely independent of one another, so
the only useful information is that which is available from CVS. The CVS
logs are usually more helpful, really; when I (and others) add a testcase I
check it in with a log entry indicating the patch which it is testing,
which you wouldn't get from the ChangeLog.
Jason