Skip to content

Fixed the FreeRTOS layer build with GCC 14 by matching the name type - #815

Merged
fdesbiens merged 1 commit into
eclipse-threadx:devfrom
fdesbiens:fix/freertos-task-name-const
Oct 22, 2026
Merged

fdesbiens merged 1 commit into
eclipse-threadx:devfrom
fdesbiens:fix/freertos-task-name-const

Conversation

@fdesbiens

Copy link
Copy Markdown
Contributor

pcTaskGetName() held the name tx_thread_info_get() returns in a const char *, but the service takes TX_NAME_CONST CHAR **, which is CHAR ** unless TX_ENABLE_CONST_NAMES is set. GCC 13 reports the mismatch as a warning; GCC 14 makes incompatible pointer types an error, so the FreeRTOS compatibility layer did not compile with it.

The local now uses TX_NAME_CONST CHAR *, so it follows the service's declaration in both configurations. The returned pointer is unchanged.

FreeRTOS regression 3/3 with GCC 14.2 and with GCC 13.3, zero warnings with each (one warning on dev with GCC 13), and 3/3 with zero warnings under GCC 14 with TX_ENABLE_CONST_NAMES.

pcTaskGetName() held the name tx_thread_info_get() returns in a const char *, but the
service takes TX_NAME_CONST CHAR **, which is CHAR ** unless TX_ENABLE_CONST_NAMES is
set. GCC 13 reports the mismatch as a warning; GCC 14 makes incompatible pointer types
an error, so the FreeRTOS compatibility layer did not compile with it.

The local now uses TX_NAME_CONST CHAR *, so it follows the service's declaration in
both configurations. The returned pointer is unchanged.

FreeRTOS regression 3/3 with GCC 14.2 and with GCC 13.3, zero warnings with each (one
warning on dev with GCC 13), and 3/3 with zero warnings under GCC 14 with
TX_ENABLE_CONST_NAMES.

Assisted-by: Claude Code (Opus 5.5) <noreply@anthropic.com>
@fdesbiens
fdesbiens merged commit 3a77bc3 into eclipse-threadx:dev Oct 22, 2026
23 of 24 checks passed
@fdesbiens
fdesbiens deleted the fix/freertos-task-name-const branch October 22, 2026 14:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant