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 c/8081] ICE with variably sized types returned from nested functions Date: Wed, 11 Jan 2012 15:58:00 -0000 [thread overview] Message-ID: <bug-8081-4-pAr1dbfkKN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-8081-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8081 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|ice-on-valid-code |accepts-invalid, | |ice-on-invalid-code Component|middle-end |c Summary|ICE with variably sized |ICE with variably sized |types and nested functions |types returned from nested | |functions Known to fail| |4.7.0 --- Comment #23 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-01-11 15:57:03 UTC --- In PR21374 it was decided to reject the testcase which makes this a C frontend issue. Testcase that still ICEs on the trunk even when optimizing: int main (int argc, char **argv) { int size = 10; typedef struct { char val[size]; } block; block b; block __attribute__((noinline)) retframe_block () { return *(block *) &b; } b=retframe_block (); return 0; } as alternative to rejecting this case we can lower returning variable-size types during un-nesting to explicit passing of a return slot and using memcpy, making the nested function return nothing.
next prev parent reply other threads:[~2012-01-11 15:58 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-8081-4@http.gcc.gnu.org/bugzilla/> 2012-01-11 15:56 ` [Bug middle-end/8081] ICE with variably sized types and " rguenth at gcc dot gnu.org 2012-01-11 15:58 ` rguenth at gcc dot gnu.org [this message] 2012-01-12 10:23 ` [Bug c/8081] ICE with variably sized types returned from " rguenth at gcc dot gnu.org 2012-01-13 8:55 ` ebotcazou at gcc dot gnu.org 2012-01-13 9:28 ` rguenther at suse dot de 2012-01-13 10:19 ` rguenth at gcc dot gnu.org 2012-01-13 11:37 ` ebotcazou at gcc dot gnu.org 2012-01-13 11:54 ` rguenth at gcc dot gnu.org 2012-01-13 12:08 ` rguenth at gcc dot gnu.org 2012-01-13 12:10 ` rguenth 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-8081-4-pAr1dbfkKN@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).