public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/96192] tree-inline.c(copy_decl_for_dup_finish) should preserve decl alignment in copy Date: Tue, 14 Jul 2020 07:04:53 +0000 [thread overview] Message-ID: <bug-96192-4-fLmDF3Kauc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96192-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96192 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2020-07-14 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Hmm, but there's no local variable to copy here? Are you refering to the result decl from b we materialize in c? This would be the same case as for example switch conversion adding a 'long long' variable, so the issue would be more wide-spread as you think - for example IPA SRA might choose to pass an aggregate by its components thus with an aggregate with two long long members you should see similar issues.
next prev parent reply other threads:[~2020-07-14 7:04 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-14 5:22 [Bug middle-end/96192] New: " skpgkp2 at gmail dot com 2020-07-14 7:04 ` rguenth at gcc dot gnu.org [this message] 2020-07-14 12:49 ` [Bug middle-end/96192] " hjl.tools at gmail dot com 2020-07-14 15:01 ` skpgkp2 at gmail dot com 2020-07-22 6:26 ` skpgkp2 at gmail dot com 2020-07-24 21:19 ` cvs-commit at gcc dot gnu.org 2020-07-24 21:20 ` hjl.tools at gmail dot com
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-96192-4-fLmDF3Kauc@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).