public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/101326] std::optional returns forced through stack Date: Mon, 05 Jul 2021 17:07:46 +0000 [thread overview] Message-ID: <bug-101326-4-vTyhWqzc4b@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101326-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101326 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2021-07-05 Severity|normal |enhancement Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Take: struct g { unsigned long b; }; struct a { struct g g1; unsigned char c; }; static inline void h(struct g *a) { a->b = 0; } static inline void j(struct a *a) { h(&a->g1); a->c = 1; } struct a f(void) { struct a a; j(&a); return a; } ---- CUT ---- It works, I suspect in the case of std::optional, std::optional is marked as BLKmode rather than TImode as the struct is marked as "ADDRESSABLE".
next prev parent reply other threads:[~2021-07-05 17:07 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-05 16:37 [Bug c++/101326] New: " tnfchris at gcc dot gnu.org 2021-07-05 16:45 ` [Bug middle-end/101326] " tnfchris at gcc dot gnu.org 2021-07-05 17:07 ` pinskia at gcc dot gnu.org [this message] 2021-07-06 6:38 ` rguenth at gcc dot gnu.org 2021-07-06 7:40 ` pinskia at gcc dot gnu.org 2023-04-26 9:46 ` pinskia at gcc dot gnu.org 2023-07-12 21:35 ` pinskia 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-101326-4-vTyhWqzc4b@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).