public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102452] Structs with flexible array members are not optimized on stack
Date: Thu, 23 Sep 2021 07:21:18 +0000 [thread overview]
Message-ID: <bug-102452-4-JawJdHSl1o@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102452-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102452
--- Comment #6 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 23 Sep 2021, pinskia at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102452
>
> Andrew Pinski <pinskia at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Severity|normal |enhancement
> Component|ipa |tree-optimization
>
> --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> Oh it is just esra (and SRA) rejecting the struct:
> Rejected (3268): zero structure field size: ret
>
> Rejected (3311): zero structure field size: ret
> Rejected (3309): zero structure field size: D.3309
>
> I had read the dump order incorrectly and such.
Yeah - not sure why exactly it execuses itself for !DECL_SIZE fields,
but well. Something to improve. (just ignore those fields)
prev parent reply other threads:[~2021-09-23 7:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 13:22 [Bug c/102452] New: " peter at peterzhu dot ca
2021-09-22 17:49 ` [Bug ipa/102452] " pinskia at gcc dot gnu.org
2021-09-23 6:42 ` rguenth at gcc dot gnu.org
2021-09-23 6:57 ` pinskia at gcc dot gnu.org
2021-09-23 7:05 ` [Bug tree-optimization/102452] " pinskia at gcc dot gnu.org
2021-09-23 7:16 ` rguenther at suse dot de
2021-09-23 7:21 ` rguenther at suse dot de [this message]
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-102452-4-JawJdHSl1o@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: link
Be 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).