rust/tests/run-make/incr-prev-body-beyond-eof/Makefile

# ignore-none no-std is not supported
# ignore-nvptx64-nvidia-cuda FIXME: can't find crate for `std`

include ../tools.mk

# Tests that we don't ICE during incremental compilation after modifying a
# function span such that its previous end line exceeds the number of lines
# in the new file, but its start line/column and length remain the same.

SRC=$(TMPDIR)/src
INCR=$(TMPDIR)/incr

all:
	mkdir $(SRC)
	mkdir $(INCR)
	cp a.rs $(SRC)/main.rs
	$(RUSTC) -C incremental=$(INCR) $(SRC)/main.rs --target $(TARGET)
	cp b.rs $(SRC)/main.rs
	$(RUSTC) -C incremental=$(INCR) $(SRC)/main.rs --target $(TARGET)
test: run-make: flag tests which won't work in no-std environments 2021-03-15 13:00:14 -05:00			`# ignore-none no-std is not supported`
test: run-make: skip tests on unsupported platforms The tests issue-36710 and incr-prev-body-beyond-eof were changed in a previous commit so that the correct target was passed to rustc (previously rustc was building for the host not for the specific target). Since that change it turns out that these platforms never worked (they only appeared to work because rustc was actually building for the host architecture). The wasm architectures fall over trying to build the C++ file in issue-36710. They look for clang (which isn't installed in the test-various docker container). If clang is installed, they can't find a wasm c++ standard library to link to. nvtptx64-nvidia-cuda fails in rustc saying it can't find std. The rust platforms support page says that std is supported on cuda so this is surprising. dist-i586-gnu-i586-i686-musl can't find the C++ compiler. There is only a musl-gcc and no musl-g++ in /musl-i586/bin/. The Docker image probably needs tweaking. 2021-03-16 13:22:21 -05:00			# ignore-nvptx64-nvidia-cuda FIXME: can't find crate for `std`
test: run-make: flag tests which won't work in no-std environments 2021-03-15 13:00:14 -05:00
move `tools.mk` to run-make apparently I missed some tests in the last commit. Rather than having dozens of tests use the long version, use the short version in `run-make` and the long version in `run-make-fulldeps` (which is now only three tests) 2023-03-30 07:58:50 -05:00			`include ../tools.mk`
incr-comp: add ignore-32bit directive to incr-prev-body-beyond-eof test Co-authored-by: Jonas Schievink <jonasschievink@gmail.com> 2020-11-08 22:31:05 -06:00
incr-comp: hash span end line/column Hash both the length and the end location (line/column) of a span. If we hash only the length, for example, then two otherwise equal spans with different end locations will have the same hash. This can cause a problem during incremental compilation wherein a previous result for a query that depends on the end location of a span will be incorrectly reused when the end location of the span it depends on has changed. A similar analysis applies if some query depends specifically on the length of the span, but we only hash the end location. So hash both. Fix #46744, fix #59954, fix #63161, fix #73640, fix #73967, fix #74890, fix #75900 2020-09-01 23:50:07 -05:00			`# Tests that we don't ICE during incremental compilation after modifying a`
			`# function span such that its previous end line exceeds the number of lines`
			`# in the new file, but its start line/column and length remain the same.`

			`SRC=$(TMPDIR)/src`
			`INCR=$(TMPDIR)/incr`

			`all:`
			`mkdir $(SRC)`
			`mkdir $(INCR)`
			`cp a.rs $(SRC)/main.rs`
run-make: Specify --target to rustc Resolves #78911 The target's linker was used but rustc wasn't told to build for that target (instead defaulting to the host). This led to the host instead of the target getting tested and to the linker getting inappropriate arguments. 2021-01-09 16:54:21 -06:00			`$(RUSTC) -C incremental=$(INCR) $(SRC)/main.rs --target $(TARGET)`
incr-comp: hash span end line/column Hash both the length and the end location (line/column) of a span. If we hash only the length, for example, then two otherwise equal spans with different end locations will have the same hash. This can cause a problem during incremental compilation wherein a previous result for a query that depends on the end location of a span will be incorrectly reused when the end location of the span it depends on has changed. A similar analysis applies if some query depends specifically on the length of the span, but we only hash the end location. So hash both. Fix #46744, fix #59954, fix #63161, fix #73640, fix #73967, fix #74890, fix #75900 2020-09-01 23:50:07 -05:00			`cp b.rs $(SRC)/main.rs`
run-make: Specify --target to rustc Resolves #78911 The target's linker was used but rustc wasn't told to build for that target (instead defaulting to the host). This led to the host instead of the target getting tested and to the linker getting inappropriate arguments. 2021-01-09 16:54:21 -06:00			`$(RUSTC) -C incremental=$(INCR) $(SRC)/main.rs --target $(TARGET)`