public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109666] [13/14 Regression] Segmentation fault with std::array using gcc 13 Date: Fri, 28 Apr 2023 14:21:55 +0000 [thread overview] Message-ID: <bug-109666-4-OLxCYrGh5Q@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109666-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109666 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpolacek at gcc dot gnu.org --- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Another test: #include <array> template <typename T, std::size_t n> struct Point { private: T value_[n]{}; }; struct Edge { Point<float, 3> start{}; Point<float, 3> end{}; }; template <typename T, std::size_t n> class StaticVector { public: static StaticVector create() { StaticVector output; return output; } private: std::array<T, n> data{}; }; class Polygon { public: using Edges = StaticVector<Edge, 3>; Edges edges() const { auto edges = Edges::create(); return edges; } }; void foo() { Polygon polygon{}; auto const edges = polygon.edges(); }
next prev parent reply other threads:[~2023-04-28 14:21 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-28 11:41 [Bug c++/109666] New: " john.viklund at effnet dot com 2023-04-28 12:18 ` [Bug c++/109666] [13/14 Regression] " redi at gcc dot gnu.org 2023-04-28 12:22 ` redi at gcc dot gnu.org 2023-04-28 14:20 ` mpolacek at gcc dot gnu.org 2023-04-28 14:21 ` mpolacek at gcc dot gnu.org [this message] 2023-05-01 14:25 ` [Bug c++/109666] [13/14 Regression] Segmentation fault with std::array using gcc 13 since r13-6788 jason at gcc dot gnu.org 2023-05-01 20:55 ` cvs-commit at gcc dot gnu.org 2023-05-02 7:19 ` carlosgalvezp at gmail dot com 2023-05-02 20:25 ` cvs-commit at gcc dot gnu.org 2023-05-03 17:11 ` jason at gcc dot gnu.org 2023-05-04 14:30 ` [Bug c++/109666] [12 Regression] Segmentation fault with std::array jason at gcc dot gnu.org 2023-05-04 14:48 ` cvs-commit at gcc dot gnu.org 2023-05-04 20:04 ` pinskia at gcc dot gnu.org 2023-05-08 12:27 ` rguenth at gcc dot gnu.org 2023-05-08 12:44 ` rguenth at gcc dot gnu.org 2023-05-09 11:30 ` marxin at gcc dot gnu.org 2023-08-11 21:21 ` cvs-commit at gcc dot gnu.org 2023-09-11 22:11 ` 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-109666-4-OLxCYrGh5Q@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).