public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/104605] _GLIBCXX_USE_C99_STDINT_TR1 macro is not defined for canadian cross freestanding C++ toolchain
Date: Tue, 04 Oct 2022 14:30:35 +0000	[thread overview]
Message-ID: <bug-104605-4-PuBcpge8Ek@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104605-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #16 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Oops, I put the wrong PR number on this commit:

https://gcc.gnu.org/g:7cdab65f3d770345903023f357b6ca96bc85a002

commit r13-3059-g7cdab65f3d770345903023f357b6ca96bc85a002
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Mon Oct 3 21:49:27 2022 +0100

    libstdc++: Make <cstdint> work freestanding [PR107134]

    When gcc/config.gcc defines use_gcc_stdin=wrap, GCC's <stdint.h> tries
    to use libc's <stdint.h> unless -ffreestanding is used.

    When libstdc++ is configured --disable-hosted-libstdcxx we want
    <cstdint> to work even without -ffreestanding being given. This is a
    kluge to make it include GCC's <stdint-gcc.h> directly even without
    -ffreestanding.

    libstdc++-v3/ChangeLog:

            PR libstdc++/107134
            * include/c_global/cstdint [!_GLIBCXX_HOSTED]: Include
            <stdint-gcc.h> directly.

This should be fixed now, please check.

I think we still want Arsen's patch in comment 10 for correctness, but this
makes libstdc++ cope without it.

  parent reply	other threads:[~2022-10-04 14:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-19  8:32 [Bug libstdc++/104605] New: " unlvsur at live dot com
2022-02-19  8:33 ` [Bug libstdc++/104605] " unlvsur at live dot com
2022-02-19  8:41 ` unlvsur at live dot com
2022-02-19 19:43 ` unlvsur at live dot com
2022-05-11 20:26 ` unlvsur at live dot com
2022-10-03 17:16 ` redi at gcc dot gnu.org
2022-10-03 17:19 ` redi at gcc dot gnu.org
2022-10-03 17:34 ` redi at gcc dot gnu.org
2022-10-03 18:29 ` unlvsur at live dot com
2022-10-03 19:37 ` redi at gcc dot gnu.org
2022-10-03 20:14 ` arsen at aarsen dot me
2022-10-03 20:22 ` unlvsur at live dot com
2022-10-03 20:54 ` redi at gcc dot gnu.org
2022-10-03 20:56 ` redi at gcc dot gnu.org
2022-10-03 20:57 ` redi at gcc dot gnu.org
2022-10-03 20:58 ` unlvsur at live dot com
2022-10-04 14:30 ` redi at gcc dot gnu.org [this message]
2023-05-12 10:43 ` redi at gcc dot gnu.org
2023-05-21 20:04 ` unlvsur at live dot com
2023-05-22  9:03 ` redi at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-104605-4-PuBcpge8Ek@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).