Extend noinline to gcc >= 12 to fix -Werror=maybe-uninitialized false positives in gcc 15

[christophebedard]

Description

A build failure can be reproduced with colcon's --mixin coverage-gcc (or -DCMAKE_C_FLAGS='--coverage' -DCMAKE_CXX_FLAGS='--coverage') on Ubuntu 26.04, which has gcc 15.2.0 by default.

Relates to eProsima/Fast-DDS#5277. It seems like this false positive issue keeps popping up in more recent versions of gcc, since (I believe) that issue/bug report is newer than gcc 12. It definitely fixes my issue reported at eProsima/Fast-DDS#5277 (comment).

@Mergifyio backport 2.2.x

Contributor Checklist

• Commit messages follow the project guidelines.
• The code follows the style guidelines of this project.
• N/A: Tests that thoroughly check the new feature have been added/Regression tests checking the bug and its fix have been added; the added tests pass locally
• N/A: Any new/modified methods have been properly documented using Doxygen.
• Changes are backport compatible: they do NOT break ABI nor change library core behavior.
• Changes are API compatible.
• N/A: New feature has been added to the versions.md file (if applicable).
• Applicable backports have been included in the description.

Reviewer Checklist

• The PR has a milestone assigned.
• The title and description correctly express the PR's purpose.
• Check contributor checklist is correct.
• Check CI results: changes do not issue any warning.
• Check CI results: CI pass and failing tests are unrelated with the changes.

[MiguelCompany]

@Mergifyio backport 2.2.x

[mergify]

backport 2.2.x

✅ Backports have been created

Details

• #312 Extend noinline to gcc >= 12 to fix -Werror=maybe-uninitialized false positives in gcc 15 (backport #311) has been created for branch 2.2.x