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 rtl-optimization/54870] [4.8 regression] gfortran.dg/array_constructor_4.f90 FAILs Date: Tue, 16 Oct 2012 22:49:00 -0000 [thread overview] Message-ID: <bug-54870-4-44fkWBfzdJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54870-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54870 --- Comment #4 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-10-16 22:49:13 UTC --- Author: ebotcazou Date: Tue Oct 16 22:49:07 2012 New Revision: 192517 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=192517 Log: PR rtl-optimization/54870 * tree.h (TREE_ADDRESSABLE): Document special usage on SSA_NAME. * cfgexpand.c (update_alias_info_with_stack_vars ): Set it on the SSA_NAME pointer that points to a partition if there is at least one variable with it set in the partition. * dse.c (local_variable_can_escape): New predicate. (can_escape): Call it. * gimplify.c (mark_addressable): If this is a partitioned decl, also mark the SSA_NAME pointer that points to a partition. Modified: trunk/gcc/cfgexpand.c trunk/gcc/dse.c trunk/gcc/gimplify.c trunk/gcc/tree.h
next prev parent reply other threads:[~2012-10-16 22:49 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-09 9:29 [Bug fortran/54870] New: " ro at gcc dot gnu.org 2012-10-09 9:30 ` [Bug fortran/54870] " ro at gcc dot gnu.org 2012-10-12 8:39 ` ro at gcc dot gnu.org 2012-10-13 21:33 ` [Bug fortran/54870] [4.8 regression] " ebotcazou at gcc dot gnu.org 2012-10-13 22:06 ` ebotcazou at gcc dot gnu.org 2012-10-16 22:49 ` ebotcazou at gcc dot gnu.org [this message] 2012-10-16 23:18 ` [Bug rtl-optimization/54870] " ebotcazou at gcc dot gnu.org 2012-10-16 23:19 ` ebotcazou 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-54870-4-44fkWBfzdJ@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).