public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/51491] ccp when converting from alloca should add a CLOBBER to right before __builtin_stack_restore Date: Mon, 12 Dec 2011 13:14:00 -0000 [thread overview] Message-ID: <bug-51491-4-AGcmt0L4hQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51491-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51491 vries at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenther at suse dot de, | |vries at gcc dot gnu.org --- Comment #2 from vries at gcc dot gnu.org 2011-12-12 13:12:16 UTC --- I ran: ... $ ./install/bin/mips64el-linux-gnu-gcc $src -O3 -g -march=octeon -fdump-tree-all -msoft-float ... for: - src/gcc-mainline/gcc/testsuite/gcc.c-torture/execute/20040811-1.c - src/gcc-mainline/gcc/testsuite/gcc.c-torture/execute/vla-dealloc-1.c. In both cases an alloca_with_align is generated during gimplify from a vla, which still exists at expand, and ccp leaves the alloca_with_align alone. So I'm not sure what I should fix in ccp.
next prev parent reply other threads:[~2011-12-12 13:12 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-10 0:47 [Bug tree-optimization/51491] New: " pinskia at gcc dot gnu.org 2011-12-12 10:38 ` [Bug tree-optimization/51491] " rguenth at gcc dot gnu.org 2011-12-12 13:14 ` vries at gcc dot gnu.org [this message] 2011-12-12 20:14 ` pinskia at gcc dot gnu.org 2011-12-12 21:33 ` vries at gcc dot gnu.org 2011-12-12 21:43 ` vries at gcc dot gnu.org 2011-12-12 22:24 ` jakub at gcc dot gnu.org 2011-12-13 15:02 ` vries at gcc dot gnu.org 2011-12-17 11:41 ` vries at gcc dot gnu.org 2011-12-17 11:43 ` vries at gcc dot gnu.org 2011-12-17 12:50 ` vries 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-51491-4-AGcmt0L4hQ@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).