[libc-commits] [libc] [libc] Enable bare-metal hermetic tests on Arm (PR #207361)

[Volodymyr Turanskyy via libc-commits]

================
@@ -0,0 +1,162 @@
+/*===----------------------------------------------------------------------===*
+ *
+ * Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
+ * See https://llvm.org/LICENSE.txt for license information.
+ * SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
+ *
+ *===----------------------------------------------------------------------===*
+ *
+ * \file
+ * Bare-metal LLVM libc test linker script.
+ *
+ *===----------------------------------------------------------------------===*/
+
+ASSERT(DEFINED(__boot_flash), "__boot_flash must be defined");
+ASSERT(DEFINED(__boot_flash_size), "__boot_flash_size must be defined");
+ASSERT(DEFINED(__flash), "__flash must be defined");
+ASSERT(DEFINED(__flash_size), "__flash_size must be defined");
+ASSERT(DEFINED(__ram), "__ram must be defined");
+ASSERT(DEFINED(__ram_size), "__ram_size must be defined");
----------------
voltur01 wrote:

We want to be able to use this for testing different versions of the architecture which requires different boards to be emulated, each board has its own memory layout. Quickly grepping ATfE current JSON configurations I can see, for example, this set of different RAM settings:
```
            "RAM_ADDRESS": "0x1000000",
            "RAM_ADDRESS": "0x21000000",
            "RAM_ADDRESS": "0x21600000",
            "RAM_ADDRESS": "0x41000000",
            "RAM_ADDRESS": "0x60600000",
            "RAM_ADDRESS": "0x61000000",
            "RAM_ADDRESS": "0x80600000",
            "RAM_ADDRESS": "0x81000000",
```
Actually, even the two sample configurations I used in the buildbot example https://github.com/llvm/llvm-zorg/pull/878 use different board with different memory layouts.

https://github.com/llvm/llvm-project/pull/207361