Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update GCC to 14.2.rel1 #3061

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update GCC to 14.2.rel1 #3061

wants to merge 1 commit into from

Conversation

josesimoes
Copy link
Member

@josesimoes josesimoes commented Jan 3, 2025

Description

  • Update PS1, AZDO templates
  • Update dev containers and bump versions.

Motivation and Context

How Has This Been Tested?

Screenshots

Types of changes

  • Improvement (non-breaking change that improves a feature, code or algorithm)
  • Bug fix (non-breaking change which fixes an issue with code or algorithm)
  • New feature (non-breaking change which adds functionality to code)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Config and build (change in the configuration and build system, has no impact on code or features)
  • Dev Containers (changes related with Dev Containers, has no impact on code or features)
  • Dependencies/declarations (update dependencies or assembly declarations and changes associated, has no impact on code or features)
  • Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist

  • My code follows the code style of this project (only if there are changes in source code).
  • My changes require an update to the documentation (there are changes that require the docs website to be updated).
  • I have updated the documentation accordingly (the changes require an update on the docs in this repo).
  • I have read the CONTRIBUTING document.
  • I have tested everything locally and all new and existing tests passed (only if there are changes in source code).

Summary by CodeRabbit

  • Chores
    • Updated base development container images across multiple environments
    • Upgraded GCC toolchain from version 13.3.rel1 to 14.2.rel1
    • Updated Azure Pipelines templates and installation scripts to reflect new toolchain version

Copy link

coderabbitai bot commented Jan 3, 2025

Walkthrough

This pull request involves updating the development container Dockerfiles and related scripts across multiple projects. The changes primarily focus on upgrading the base images and the GCC toolchain version from 13.3.rel1 to 14.2.rel1. These updates span various development environments including All, AzureRTOS, ChibiOS, FreeRTOS-NXP, TI, and the associated Azure Pipelines template and installation script.

Changes

File Change Summary
.devcontainer/*/Dockerfile.* Base image versions updated across different projects (All: v2.55 → v2.56, AzureRTOS: v1.32 → v1.33, ChibiOS: v1.33 → v1.34, FreeRTOS-NXP: v1.05 → v1.06, TI: v1.26 → v1.27)
.devcontainer/*/Dockerfile.*.SRC GCC toolchain version updated from 13.3.rel1 to 14.2.rel1
azure-pipelines-templates/download-install-arm-gcc-toolchain.yml Updated default GCC ARM version and cache key
install-scripts/install-arm-gcc-toolchain.ps1 Updated default GCC version from 13.3.rel1 to 14.2.rel1

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
.devcontainer/All/Dockerfile.All.SRC (1)

12-12: Verify build system integration

The GCC toolchain update is properly integrated:

  1. Using HTTPS for secure downloads
  2. Downloading from the official ARM source
  3. Version is consistent across all container variants

Consider implementing version pinning through a central configuration to ensure consistency when updating toolchain versions in the future.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 10dfd61 and 7f95cfa.

📒 Files selected for processing (12)
  • .devcontainer/All/Dockerfile.All (1 hunks)
  • .devcontainer/All/Dockerfile.All.SRC (1 hunks)
  • .devcontainer/AzureRTOS/Dockerfile.AzureRTOS (1 hunks)
  • .devcontainer/AzureRTOS/Dockerfile.AzureRTOS.SRC (1 hunks)
  • .devcontainer/ChibiOS/Dockerfile.ChibiOS (1 hunks)
  • .devcontainer/ChibiOS/Dockerfile.ChibiOS.SRC (1 hunks)
  • .devcontainer/FreeRTOS-NXP/Dockerfile.FreeRTOS-NXP (1 hunks)
  • .devcontainer/FreeRTOS-NXP/Dockerfile.FreeRTOS-NXP.SRC (1 hunks)
  • .devcontainer/TI/Dockerfile.TI (1 hunks)
  • .devcontainer/TI/Dockerfile.TI.SRC (1 hunks)
  • azure-pipelines-templates/download-install-arm-gcc-toolchain.yml (1 hunks)
  • install-scripts/install-arm-gcc-toolchain.ps1 (3 hunks)
✅ Files skipped from review due to trivial changes (5)
  • .devcontainer/All/Dockerfile.All
  • .devcontainer/ChibiOS/Dockerfile.ChibiOS
  • .devcontainer/TI/Dockerfile.TI
  • .devcontainer/FreeRTOS-NXP/Dockerfile.FreeRTOS-NXP
  • .devcontainer/AzureRTOS/Dockerfile.AzureRTOS
🔇 Additional comments (8)
install-scripts/install-arm-gcc-toolchain.ps1 (1)

15-15: Well-aligned toolchain version update.

Updating the default version to 14.2.rel1 aligns with the rest of the changes in this PR. Ensures consistent installations across environments.

azure-pipelines-templates/download-install-arm-gcc-toolchain.yml (2)

7-7: Default version bump is consistent.

Switching from 13.3.rel1 to 14.2.rel1 is a good improvement, ensuring the pipeline consistently uses the new GCC version.


14-14: Validate cache key correctness.

Updating the cache key to "gcc-14_2_rel1" is appropriate. Confirm that other scripts or workflows using the old cache key have been updated or deprecated.

.devcontainer/FreeRTOS-NXP/Dockerfile.FreeRTOS-NXP.SRC (1)

12-12: Toolchain version alignment.

The ARG version update to 14.2.rel1 here matches the rest of the PR. This keeps the FreeRTOS-NXP dev environment aligned with the new GCC toolchain release.

.devcontainer/TI/Dockerfile.TI.SRC (1)

12-12: Consistent TI toolchain update.

Upgrading the TI environment to 14.2.rel1 fosters consistency. Confirm that any TI-specific tooling remains compatible with the newer GCC release.

.devcontainer/ChibiOS/Dockerfile.ChibiOS.SRC (1)

12-12: Verify compatibility with GCC 14.2.rel1

The upgrade from GCC 13.3.rel1 to 14.2.rel1 represents a major version bump that could introduce breaking changes. Please ensure:

  1. The new version is compatible with the existing build system
  2. All compiler flags and options remain valid
  3. No regressions in the build process
✅ Verification successful

GCC 14.2.rel1 upgrade appears safe for ChibiOS build system

The analysis of the build system shows that:

  1. The toolchain configuration is version-agnostic and relies on standard GCC ARM compiler flags
  2. All compiler flags used are standard and well-established (-mthumb, -mcpu, -mfpu, etc.)
  3. The build system uses CMake's compiler test (CMAKE_TRY_COMPILE_TARGET_TYPE) to validate toolchain compatibility
  4. No version-specific GCC features or flags are being used
  5. The C/C++ standards are set to C17/C++17 which are well supported by GCC 14

The upgrade from GCC 13.3 to 14.2 should be compatible as the build system:

  • Uses standard ARM architecture flags
  • Doesn't rely on version-specific features
  • Implements proper toolchain validation
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for any GCC-specific compiler flags or options in the build system
rg -l "gcc|g\+\+|\-f|\-W|\-m" | grep -i "cmake\|makefile"

# Look for any GCC version checks or dependencies
rg -l "gcc.*version|gcc.*\d+\.\d+|toolchain.*version" | grep -i "cmake\|makefile"

Length of output: 2977


Script:

#!/bin/bash
# Check GCC-specific configurations in toolchain files
cat CMake/toolchain.arm-none-eabi.cmake

# Check GCC options in ChibiOS specific files
cat CMake/Modules/CHIBIOS_STM32F7xx_GCC_options.cmake
cat CMake/Modules/CHIBIOS_STM32F4xx_GCC_options.cmake

# Check if there are any version-specific compiler flags
rg -A 5 "CMAKE_C_COMPILER|CMAKE_CXX_COMPILER" CMake/toolchain.arm-none-eabi.cmake

Length of output: 9998

.devcontainer/AzureRTOS/Dockerfile.AzureRTOS.SRC (1)

12-12: Consistent toolchain version across configurations

The GCC version update to 14.2.rel1 aligns with other development container configurations, maintaining consistency across the build environment.

.devcontainer/All/Dockerfile.All.SRC (1)

Line range hint 13-17: Security considerations for toolchain downloads

The implementation follows security best practices:

  1. Uses HTTPS for downloading the toolchain
  2. Downloads directly from the official ARM source
  3. Performs cleanup of temporary files and documentation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants