[Bug c/112699] New: Should limits.h in freestanding environment be self-contained?

[Bug c/112699] New: Should limits.h in freestanding environment be self-contained?

[xry111 at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112699

            Bug ID: 112699
           Summary: Should limits.h in freestanding environment be
                    self-contained?
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: xry111 at gcc dot gnu.org
  Target Milestone: ---

Currently limits.h always includes the libc limits.h if it's available at build
time.  Should it be self-contained instead like stdint.h with -ffreestanding?

[Bug c/112699] Should limits.h in freestanding environment be self-contained?

[amonakov at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112699

Alexander Monakov <amonakov at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |amonakov at gcc dot gnu.org

--- Comment #1 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
Can you clarify which file you mean? gcc/ginclude does not have a limits.h.

I assume you are not talking about the fixinclude'd limits.h?

[Bug c/112699] Should limits.h in freestanding environment be self-contained?

[amonakov at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112699

--- Comment #2 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
Sorry, even though GCC's limits.h is installed under include-fixed, it is
generated separately, not by the generic fixincludes mechanism. I was confused.

[Bug c/112699] Should limits.h in freestanding environment be self-contained?

[xry111 at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112699

--- Comment #3 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to Alexander Monakov from comment #1)
> Can you clarify which file you mean? gcc/ginclude does not have a limits.h.
> 
> I assume you are not talking about the fixinclude'd limits.h?

No, I mean the limits.h in $(dirname $(gcc -print-libgcc-file-name)).  It
currently contains these lines to include libc limits.h:

#ifndef _LIBC_LIMITS_H_
/* Use "..." so that we find syslimits.h only in this same directory.  */
#include "syslimits.h"
#endif

(if libc limits.h is fixinclude'd, it will be saved to syslimits.h; otherwise
syslimits.h will just contain "#include_next <limits.h>".)

And I'm asking if

#ifndef _LIBC_LIMITS_H_ && !__STDC_HOSTED__
/* Use "..." so that we find syslimits.h only in this same directory.  */
#include "syslimits.h"
#endif

would be better?