rust/tests/run-make/target-cpu-native/Makefile

include ../tools.mk

# only-linux
# only-x86_64
#
# I *really* don't want to deal with a cross-platform way to compare file sizes,
# tests in `make` sort of are awful

all: $(TMPDIR)/out.log
	# Make sure no warnings about "unknown CPU `native`" were emitted
	if [ "$$(wc -c $(TMPDIR)/out.log | cut -d' ' -f 1)" = "0" ]; then \
	  echo no warnings generated; \
	else \
	  exit 1; \
	fi


$(TMPDIR)/out.log:
	$(RUSTC) foo.rs -C target-cpu=native 2>&1 | tee $(TMPDIR)/out.log
	$(call RUN,foo)
Diagnose missing includes in run-make tests 2022-08-22 19:00:00 -05:00			`include ../tools.mk`
Add support for target-cpu=native 2015-03-09 19:46:45 -05:00
use ignore directives for run-make tests This makes the tests easier to read, and makes it possible to tell which tests aren't being run on the host platform. Fixes #56704. 2019-01-06 15:27:57 -06:00			`# only-linux`
			`# only-x86_64`
			`#`
Fix warnings about the `native` target-cpu This fixes a regression from #53031 where specifying `-C target-cpu=native` is printing a lot of warnings from LLVM about `native` being an unknown CPU. It turns out that `native` is indeed an unknown CPU and we have to perform a mapping to an actual CPU name, but this mapping is only performed in one location rather than all locations we inform LLVM about the target CPU. This commit centralizes the mapping of `native` to LLVM's value of the native CPU, ensuring that all locations we inform LLVM about the `target-cpu` it's never `native`. Closes #53322 2018-08-23 13:03:22 -05:00			`# I really don't want to deal with a cross-platform way to compare file sizes,`
			# tests in `make` sort of are awful
use ignore directives for run-make tests This makes the tests easier to read, and makes it possible to tell which tests aren't being run on the host platform. Fixes #56704. 2019-01-06 15:27:57 -06:00
Fix warnings about the `native` target-cpu This fixes a regression from #53031 where specifying `-C target-cpu=native` is printing a lot of warnings from LLVM about `native` being an unknown CPU. It turns out that `native` is indeed an unknown CPU and we have to perform a mapping to an actual CPU name, but this mapping is only performed in one location rather than all locations we inform LLVM about the target CPU. This commit centralizes the mapping of `native` to LLVM's value of the native CPU, ensuring that all locations we inform LLVM about the `target-cpu` it's never `native`. Closes #53322 2018-08-23 13:03:22 -05:00			`all: $(TMPDIR)/out.log`
			# Make sure no warnings about "unknown CPU `native`" were emitted
			`if [ "$$(wc -c $(TMPDIR)/out.log \| cut -d' ' -f 1)" = "0" ]; then \`
			`echo no warnings generated; \`
			`else \`
			`exit 1; \`
			`fi`


			`$(TMPDIR)/out.log:`
			`$(RUSTC) foo.rs -C target-cpu=native 2>&1 \| tee $(TMPDIR)/out.log`
Add support for target-cpu=native 2015-03-09 19:46:45 -05:00			`$(call RUN,foo)`