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++/115522] [13/14/15 Regression] std::to_array no longer works for struct which is trivial but not default constructible Date: Wed, 19 Jun 2024 16:39:34 +0000 [thread overview] Message-ID: <bug-115522-4-41kISsYo8M@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115522-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115522 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://gcc.gnu.org/piperma | |il/gcc-patches/2024-June/65 | |5146.html Keywords| |patch --- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> --- Patch posted: https://gcc.gnu.org/pipermail/gcc-patches/2024-June/655146.html
next prev parent reply other threads:[~2024-06-19 16:39 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-17 12:13 [Bug libstdc++/115522] New: " daniel.klauer at gin dot de 2024-06-17 15:11 ` [Bug libstdc++/115522] [13/14/15 Regression] " pinskia at gcc dot gnu.org 2024-06-17 15:15 ` pinskia at gcc dot gnu.org 2024-06-17 16:17 ` redi at gcc dot gnu.org 2024-06-17 19:03 ` redi at gcc dot gnu.org 2024-06-18 12:14 ` redi at gcc dot gnu.org 2024-06-18 12:47 ` redi at gcc dot gnu.org 2024-06-19 16:39 ` redi at gcc dot gnu.org [this message] 2024-06-20 2:31 ` de34 at live dot cn 2024-06-21 9:15 ` cvs-commit at gcc dot gnu.org 2024-07-12 10:19 ` [Bug libstdc++/115522] [13/14 " cvs-commit at gcc dot gnu.org 2024-07-12 10:21 ` redi at gcc dot gnu.org 2024-07-12 10:21 ` redi at gcc dot gnu.org 2024-07-12 11:11 ` cvs-commit at gcc dot gnu.org 2024-07-12 11:12 ` redi at gcc dot gnu.org 2024-07-18 19:15 ` cvs-commit 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-115522-4-41kISsYo8M@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).