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: Mon, 03 Oct 2022 20:54:46 +0000 [thread overview] Message-ID: <bug-104605-4-rSFV38hpmG@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 #12 from Jonathan Wakely <redi at gcc dot gnu.org> --- Please stop mixing separate issues together in bug reports. If you want that change, file a separate bug report asking for it.
next prev parent reply other threads:[~2022-10-03 20:54 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 [this message] 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 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-rSFV38hpmG@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: linkBe 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).