Summary
Review places where Xeneva defines standard macros or types that may already be provided by the compiler or standard headers.
The goal is to rely on compiler-provided definitions where appropriate while retaining project-specific fallback definitions where they are genuinely required for freestanding builds or platform compatibility.
Initial Scope
- Review
SIZE_MAX usage across GCC and MSVC.
- Verify behavior in freestanding bootloader and kernel builds.
- Confirm include paths for both toolchains.
- Keep project-specific fallback definitions only where they are required.
- Avoid changing behavior without validation on all supported toolchains.
Motivation
During GCC compatibility work, we observed that GCC already provides SIZE_MAX through its standard headers. The current implementation intentionally keeps a fallback for compatibility, but a broader review would help identify where compiler-provided definitions can be used safely and where project-defined fallbacks are still necessary.
This is a cleanup task and is intentionally kept separate from the ongoing GCC porting PRs to avoid mixing functional changes with portability improvements.
Related
This cleanup task originated during the review of PR #66 while discussing SIZE_MAX compatibility across GCC and MSVC toolchains.
The goal is to evaluate standard compiler-provided definitions and retain project-specific fallbacks only where they are actually required after verification.
Summary
Review places where Xeneva defines standard macros or types that may already be provided by the compiler or standard headers.
The goal is to rely on compiler-provided definitions where appropriate while retaining project-specific fallback definitions where they are genuinely required for freestanding builds or platform compatibility.
Initial Scope
SIZE_MAXusage across GCC and MSVC.Motivation
During GCC compatibility work, we observed that GCC already provides
SIZE_MAXthrough its standard headers. The current implementation intentionally keeps a fallback for compatibility, but a broader review would help identify where compiler-provided definitions can be used safely and where project-defined fallbacks are still necessary.This is a cleanup task and is intentionally kept separate from the ongoing GCC porting PRs to avoid mixing functional changes with portability improvements.
Related
This cleanup task originated during the review of PR #66 while discussing
SIZE_MAXcompatibility across GCC and MSVC toolchains.The goal is to evaluate standard compiler-provided definitions and retain project-specific fallbacks only where they are actually required after verification.