NetBSD/tests/usr.bin/xlint/lint1/msg_113.c

/*	$NetBSD: msg_113.c,v 1.3 2022/06/16 16:58:36 rillig Exp $	*/
# 3 "msg_113.c"

// Test for message: cannot take address of register %s [113]

/* ARGSUSED */
void
example(register int arg)
{
	/* expect+1: error: cannot take address of register arg [113] */
	return &arg;
}
tests/lint: make expectation lines in the tests more detailed This commit migrates msg_100 until msg_199. 2022-06-16 19:58:35 +03:00			`/* $NetBSD: msg_113.c,v 1.3 2022/06/16 16:58:36 rillig Exp $ */`
lint: add a test for each message produced by lint1 Having a test for each message ensures that upcoming refactorings don't break the basic functionality. Adding the tests will also discover previously unknown bugs in lint. The tests ensure that every lint message can actually be triggered, and they demonstrate how to do so. Having a separate file for each test leaves enough space for documenting historical anecdotes, rationale or edge cases, keeping them away from the source code. The interesting details of this commit are in Makefile and t_integration.sh. All other files are just auto-generated. When running the tests as part of ATF, they are packed together as a single test case. Conceptually, it would have been better to have each test as a separate test case, but ATF quickly becomes very slow as soon as a test program defines too many test cases, and 50 is already too many. The time complexity is O(n^2), not O(n) as one would expect. It's the same problem as in tests/usr.bin/make, which has over 300 test cases as well. 2021-01-02 13:22:42 +03:00			`# 3 "msg_113.c"`

			`// Test for message: cannot take address of register %s [113]`

tests/lint: make expectation lines in the tests more detailed This commit migrates msg_100 until msg_199. 2022-06-16 19:58:35 +03:00			`/* ARGSUSED */`
			`void`
			`example(register int arg)`
			`{`
			`/* expect+1: error: cannot take address of register arg [113] */`
			`return &arg;`
			`}`