You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The multilib system added to clang by the previous commit doesn't do
anything unless a YAML configuration file is available at run time.
This commit adds one.
This makes the .cfg files optional, although they're still available
to be used if a user prefers. For example, these two commands have the
same effect of building a semihosting hello-world program for Armv7-M,
with and without a config file:
clang --config=armv7m_soft_nofp_semihost.cfg -T picolibc.ld hello.c
clang --target=arm-none-eabi -march=armv7-m -T picolibc.ld -lcrt0-semihost -lsemihost hello.c
The multilib.yaml is built by a CMake configure_file command, starting
from a template containing a static FlagMap section, and filling in
the Variants section to match the set of library variants actually
being built. Each library must now provide a set of multilib selection
flags along with the compile flags for the library itself.
Documentation for the YAML format can be found in
clang/docs/Multilib.rst, which is included in the previous commit's
patch update, or alternatively in https://reviews.llvm.org/D143587.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
11
11
- Support for locales and input/output streams
12
12
- Experimental support for Armv4T and Armv5TE architectures (#177)
13
13
- Support for building locally on Windows & macOS (#188)
14
+
- Experimental support for multilib, meaning that clang can now automatically select an appropriate set of libraries based on your compile flags, without needing either an explicit `--sysroot` option or a `--config` option. However, the config files are still present, and you can still use them instead.
0 commit comments