From: Ramana Radhakrishnan <ramana.gcc@googlemail.com>
To: Akshat Garg <xkspr7@gmail.com>
Cc: Paul McKenney <paulmck@linux.ibm.com>,
gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: Doubts regarding the _Dependent_ptr keyword
Date: Tue, 02 Jul 2019 11:01:00 -0000 [thread overview]
Message-ID: <CAJA7tRZn535y_+-HkGX4MBh4PKtZ11PX9RQ+xA-Z10Pk5PXZWA@mail.gmail.com> (raw)
In-Reply-To: <CAMEQ7YyKmBSdyTxsZsw-nnKdfp7P7Pi2Pz6fZ2Fbsk5XApp4yA@mail.gmail.com>
>>
>> It's worth figuring out what passes are doing this - however the worry
>> I have is that every pass now needs to be handling this case with
>> respect to pointer attributes. Is there some place that you are
>> storing said information and what is the transitive nature of
>> assignments with these attributes ?
>>
>> regards
>> Ramana
>
> I don't understand what information to store, can you explain? I was thinking of putting some code inside the pass, which breaks the dependency chains, which will avoid this type of conversions when it finds out that the pointer is _Dependent_ptr qualified otherwise don't do anything. Can you let me know what I am missing on?
>
That the pointer has an attribute that it's a dependent pointer . How
do you expect the later passes to detect it has a dependent_ptr
attribute attached to it ?
> In transitive nature, are you talking about the dependent pointer being assigned to some non-dependent pointer and after further assigned to some other pointer?
Yes. What's the expected behaviour as per the document ?
Ramana
>>
>>
>> > Does this sounds like a workable plan for ? Let me know your thoughts. If this sounds good then, we can do this for all the optimizations that may kill the dependencies at somepoint.
>> >
>> > -Akshat
next prev parent reply other threads:[~2019-07-02 11:01 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMEQ7Yw5mV+zoDV-kmOnWoy4+_CiDeUyJmipkkrTGhxninp3Hw@mail.gmail.com>
[not found] ` <20190617023256.GJ26519@linux.ibm.com>
[not found] ` <CAMEQ7Yxp-o+4dPd_o=eaPYqpV1n7KfqMS_Un1U1n9-ut_HK_uw@mail.gmail.com>
[not found] ` <20190618211927.GY26519@linux.ibm.com>
[not found] ` <CAJA7tRYJPaFuvR+bC40kGdKOLVTHEFnD1SkBqF6oUcpv-bLMbw@mail.gmail.com>
[not found] ` <CAMEQ7YyN72aMAEsuKW4GQua_Vyi8Wd6F6BKcTo8dS_JcLm2TvQ@mail.gmail.com>
[not found] ` <CAMEQ7YxT4mwNvgr_iqxKAJE=yeuOmhcNkHL1ET-84hwv9uMwdQ@mail.gmail.com>
[not found] ` <CAJA7tRZVhVtabJLgWJ3BK3HhR2pf+X0fiG+sF=y2Y=PkWg8eTQ@mail.gmail.com>
[not found] ` <CAMEQ7YyLp0YymRiYD4O_1A=YswbbDBh0gQz9kGtw4t8mfvU4Jg@mail.gmail.com>
[not found] ` <20190619164145.GJ26519@linux.ibm.com>
[not found] ` <20190620140600.GA15142@linux.ibm.com>
[not found] ` <CAMEQ7Yx=dg0TWcXKA8eZk=RCN+az116Y9whKGQSB3fRVZwbvQw@mail.gmail.com>
[not found] ` <CAJA7tRbj6eoOj_fr+Nnm1rS=kdc0jPxkb77AoPCFrJEaaPsCSA@mail.gmail.com>
2019-06-25 16:20 ` Akshat Garg
2019-07-02 0:29 ` Akshat Garg
2019-07-02 0:59 ` Paul E. McKenney
2019-07-02 1:42 ` nick
2019-07-02 15:36 ` Jason Merrill
2019-07-02 17:53 ` Richard Biener
2019-07-03 15:09 ` Paul E. McKenney
2019-07-02 19:37 ` Akshat Garg
2019-07-17 10:54 ` Akshat Garg
2019-07-22 0:27 ` Akshat Garg
2019-07-22 8:41 ` Richard Biener
2019-07-22 8:54 ` Akshat Garg
2019-07-22 9:46 ` Richard Biener
2019-07-23 20:11 ` Akshat Garg
2019-07-23 20:50 ` Akshat Garg
2019-07-02 10:22 ` Ramana Radhakrishnan
2019-07-02 10:39 ` Akshat Garg
2019-07-02 11:01 ` Ramana Radhakrishnan [this message]
2019-07-02 12:38 ` Paul E. McKenney
2019-07-02 13:16 ` Ramana Radhakrishnan
2019-07-02 15:09 ` Paul E. McKenney
2019-07-02 19:09 ` Akshat Garg
2019-07-03 15:16 ` Paul E. McKenney
2019-07-03 15:48 ` Richard Biener
2019-07-03 16:34 ` Paul E. McKenney
2019-07-04 11:00 ` Richard Biener
2019-07-04 17:40 ` Paul E. McKenney
2019-07-04 18:09 ` Jakub Jelinek
2019-07-04 23:08 ` Akshat Garg
2019-07-05 11:20 ` Richard Biener
2019-07-05 15:38 ` Akshat Garg
[not found] ` <20190705014806.GM26519@linux.ibm.com>
[not found] ` <CAMEQ7YyrjkGVhnLUCXMrbyicPkRZkpZvH_3KQ56cNh_6+Tr4iQ@mail.gmail.com>
[not found] ` <CAMEQ7YzOqU68kQN99g_zhwJUkNaJa9q_Dv9pue+4NFK4rYubFg@mail.gmail.com>
[not found] ` <20190707141928.GE26519@linux.ibm.com>
[not found] ` <CAMEQ7YyuzvN_OzU4oMJGaFMBpnQwkCt4=ZTo-AmSmvsr2dBOMw@mail.gmail.com>
2019-07-07 21:44 ` Akshat Garg
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=CAJA7tRZn535y_+-HkGX4MBh4PKtZ11PX9RQ+xA-Z10Pk5PXZWA@mail.gmail.com \
--to=ramana.gcc@googlemail.com \
--cc=gcc@gcc.gnu.org \
--cc=paulmck@linux.ibm.com \
--cc=xkspr7@gmail.com \
/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).