public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/30265] Compound literal can cause invalid gimple Date: Sat, 21 Apr 2007 21:47:00 -0000 [thread overview] Message-ID: <20070421214745.29698.qmail@sourceware.org> (raw) In-Reply-To: <bug-30265-6528@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from pinskia at gcc dot gnu dot org 2007-04-21 22:47 ------- Subject: Bug 30265 Author: pinskia Date: Sat Apr 21 22:47:35 2007 New Revision: 124024 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=124024 Log: 2007-04-21 Andrew Pinski <andrew_pinski@playstation.sony.com> PR C/30265 * c-gimplifier.c (gimplify_compound_literal_expr): Mark the decl as addressable if the compound literal was marked as addressable. Mark the decl as a gimple register if it is a complex or vector decl and does not live in memory. 2007-04-21 Andrew Pinski <andrew_pinski@playstation.sony.com> PR C/30265 * gcc.c-torture/compile/compound-literal-2.c: New testcase. * gcc.c-torture/compile/compound-literal-3.c: New testcase. Added: trunk/gcc/testsuite/gcc.c-torture/compile/compound-literal-2.c trunk/gcc/testsuite/gcc.c-torture/compile/compound-literal-3.c Modified: trunk/gcc/ChangeLog trunk/gcc/c-gimplify.c trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30265
prev parent reply other threads:[~2007-04-21 21:47 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-12-20 5:07 [Bug c/30265] New: " pinskia at gcc dot gnu dot org 2006-12-20 5:08 ` [Bug c/30265] " pinskia at gcc dot gnu dot org 2007-04-21 21:47 ` pinskia at gcc dot gnu dot org 2007-04-21 21:47 ` pinskia at gcc dot gnu dot org [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=20070421214745.29698.qmail@sourceware.org \ --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).