aboutsummaryrefslogtreecommitdiff
path: root/linux-headers/include
diff options
context:
space:
mode:
authorTsukasa OI <research_trasio@irq.a4lg.com>2025-08-22 01:49:26 +0000
committerChristoph Müllner <christophm30@gmail.com>2025-08-27 12:04:35 +0200
commit4f2083a0063cb03e6a675be44f90902e7ff69c68 (patch)
treec38543676f84e0ea020735396e0c463ae251b526 /linux-headers/include
parentb8ca156d2ab0038c6af4569c52f9ec30d95342f0 (diff)
downloadriscv-gnu-toolchain-4f2083a0063cb03e6a675be44f90902e7ff69c68.zip
riscv-gnu-toolchain-4f2083a0063cb03e6a675be44f90902e7ff69c68.tar.gz
riscv-gnu-toolchain-4f2083a0063cb03e6a675be44f90902e7ff69c68.tar.bz2
regression: Smart construction/configuration of TARGETS2025.08.28
It makes: 1. Default target list is easier to read and to reconfigure by splitting target bases and code models. 2. TARGETS is now configurable through external environment variable (not just as a make argument), which makes TARGETS consistent with RUNTESTFLAGS. Because `TARGETS = ...` is used inside the Makefile, we could configure targets to perform regression tests with `make report TARGETS='...'` but not `TARGETS='...' make report`. This semantics is inconsistent with e.g. RUNTESTFLAGS as shown in README.md. This commit now uses `?=` to respect environment variable TARGETS given from outside, making `TARGETS='...' make report` usable. Also, this commit changes how default target list is constructed. It splits target bases and code models and each is reconfigurable through make arguments (like `make report TARGET_CODE_MODELS=medlow`). Note that TARGET_BASES and TARGET_CODE_MODELS are chosen so that no submodules use those Make variables and are ignored when the variable `TARGETS` is explicitly configured.
Diffstat (limited to 'linux-headers/include')
0 files changed, 0 insertions, 0 deletions