mirrors/espressif--esp-idf
1
0
Fork 0
Code Issues Pull Requests Actions 1 Deployments Models Agent Notes Packages Projects Releases Wiki Activity

chore: import upstream snapshot with attribution

Browse Source
This commit is contained in:
wehub-resource-sync
2026-07-13 13:04:25 +08:00
commit 548b49ebc0
20937 changed files with 5455372 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tools/test_apps/system/init_array/README.md
+20
View File
@@ -0,0 +1,20 @@
| Supported Targets | ESP32 | ESP32-C2 | ESP32-C3 | ESP32-C5 | ESP32-C6 | ESP32-C61 | ESP32-H2 | ESP32-H21 | ESP32-H4 | ESP32-P4 | ESP32-S2 | ESP32-S3 | ESP32-S31 | Linux |
| ----------------- | ----- | -------- | -------- | -------- | -------- | --------- | -------- | --------- | -------- | -------- | -------- | -------- | --------- | ----- |
# Historical note
Initially, ESP-IDF used the `do_global_ctors()` function to run global constructors.
This was done to accommodate Xtensa targets that emit `.ctors.*` sections, which are ordered in descending order.
For RISC-V, compilation used `.init_array.*` sections, which are designed to have ascending order.
Priority constructors in `.init_array.*` sections were correctly processed in ascending order.
However, non-priority `.init_array` section was processed in descending order (as it was done for Xtensa `.ctors`).
Starting with ESP-IDF v6.0, the implementation switched to the standard LibC behavior (`__libc_init_array()`),
which processes both priority and non-priority constructors in ascending order.
To achieve this, a breaking changes were introduced:
- Xtensa `.ctors.*` entries converted to `.init_array.*` format (ascending), to be passed to `__libc_init_array()`.
- Processing order of non-priority `.init_array` and `.ctors` sections was changed from descending to ascending.
This test ensures that the initialization order is correct and consistent between ESP-IDF and Linux targets.