From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: Richard Guenther <rguenther@suse.de>, gcc-patches@gcc.gnu.org
Subject: Re: PR middle-end/44813 (ICE in Mozilla build in ptr_deref_may_alias_decl_p)
Date: Sun, 16 Jan 2011 20:09:00 -0000 [thread overview]
Message-ID: <AANLkTinFkLsim+hGpWAffosdoiaKZEXM=YOCkesMr7G6@mail.gmail.com> (raw)
In-Reply-To: <20100705161839.GA14621@atrey.karlin.mff.cuni.cz>
On Mon, Jul 5, 2010 at 9:18 AM, Jan Hubicka <hubicka@ucw.cz> wrote:
> Hi,
> here is updated patch, with Richard's reduced testcase that solves some furhter
> problems.
> In particular adding the tester down that ipa-split produce new SSA name
> for return value and sets as definining statement the call (that is wrong
> for DECL_BY_REFERENCE)> I also cleaned up the code a bit there.
> Also ipa-ssa-ccp considers RESULT_DECL as undefined that leads to misoptimization
> after fixing the first problem on libstdc++ vector testcase.
>
> Bootstrapped/regtested x86_64-linux, OK?
>
> * tree-ssa-uninit.c (ssa_undefined_value_p): Result decl is defined
> for functions passed by reference.
> * tree.c (needs_to_live_in_memory): RESULT_DECL don't need to live
> in memory when passed by reference.
> * tree-ssa-ccp.c (get_default_value): Only VAR_DECL is undefined at
> beggining.
> * ipa-split.c (split_function): Cleanup way return value is passed;
> handle SSA DECL_BY_REFERENCE retvals.
> * tree-ssa.c (verify_def): Verify that RESULT_DECL is read only when
> DECL_BY_REFERENCE is set.
> * tree-inline.c (remap_gimple_stmt): Handle SSA DECL_BY_REFERENCE
> returns.
> * tree-ssa-structalias.c (get_constraint_for_ssa_var, get_fi_for_callee,
> find_what_p_points_to): Handle RESULT_DECL.
>
This caused:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47313
--
H.J.
prev parent reply other threads:[~2011-01-16 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-04 22:42 Jan Hubicka
2010-07-05 9:43 ` Richard Guenther
2010-07-05 10:28 ` Jan Hubicka
2010-07-05 16:18 ` Jan Hubicka
2010-07-06 9:20 ` Richard Guenther
2011-01-16 20:09 ` H.J. Lu [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='AANLkTinFkLsim+hGpWAffosdoiaKZEXM=YOCkesMr7G6@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=rguenther@suse.de \
/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: link
Be 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).