public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/59711] ICE in force_constant_size, at gimplify.c:619 with variably-modified return type Date: Wed, 08 Jan 2014 12:11:00 -0000 [thread overview] Message-ID: <bug-59711-4-T3S98fM1nT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59711-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59711 --- Comment #5 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- > I believe this isn't fixable with the GIMPLE IL as-is - without lowering > to the fact that g () returns by storing to a return slot. Not sure why > 3.4 ICEd (2.95.2 also ICEs btw ...). Because historically you cannot create temporaries with variable size in GCC. > Well, maybe we can fix it if we allow creating of a variable-size temporary > during gimplification. That is, the gimple code needs to look like > > tem = WITH_SIZE_EXPR <g (), sizeof (S)>; > return tem.a[0]; > > which of course then has the issue that we can't have WITH_SIZE_EXPR around > calls. Thus really the only way is to lower the return slot fact early. > > g (&tem); > return tem.a[0]; Of course this situation occurs very frequently in Ada and we explicitly create the temporary in gigi.
next prev parent reply other threads:[~2014-01-08 12:11 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-07 15:08 [Bug middle-end/59711] New: ICE in force_constant_size, at gimplify.c:619 (nested function and variably-modified type) fweimer at redhat dot com 2014-01-07 15:15 ` [Bug middle-end/59711] " fweimer at redhat dot com 2014-01-07 15:24 ` [Bug middle-end/59711] ICE in force_constant_size, at gimplify.c:619 with variably-modified return type mpolacek at gcc dot gnu.org 2014-01-07 22:37 ` ebotcazou at gcc dot gnu.org 2014-01-08 11:59 ` rguenth at gcc dot gnu.org 2014-01-08 12:11 ` ebotcazou at gcc dot gnu.org [this message] 2014-01-08 12:14 ` fweimer at redhat dot com 2014-01-08 14:53 ` rguenth at gcc dot gnu.org 2021-11-29 2:38 ` 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-59711-4-T3S98fM1nT@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).