Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(6)

Issue 4591066: [google] Enhance Annotalysis to support cloned functions/methods (Closed)

Can't Edit
Can't Publish+Mail
Start Review
Created:
12 years, 10 months ago by Le-Chun Wu
Modified:
12 years, 10 months ago
CC:
Ollie Wild, delesley, gcc-patches_gcc.gnu.org
Visibility:
Public.

Description

Fix submitted to google/main at r175062.

Patch Set 1 #

Patch Set 2 : [google] Enhance Annotalysis to support cloned functions/methods #

Patch Set 3 : [google] Enhance Annotalysis to support cloned functions/methods #

Total comments: 4
Unified diffs Side-by-side diffs Delta from patch set Stats (+69 lines, -10 lines) Patch
A gcc/testsuite/g++.dg/thread-ann/thread_annot_lock-78.C View 1 chunk +28 lines, -0 lines 0 comments Download
M gcc/tree-threadsafe-analyze.c View 1 2 5 chunks +41 lines, -10 lines 4 comments Download

Messages

Total messages: 5
Le-Chun Wu
Enhance Annotalysis to support cloned functions/methods (especially created by IPA-SRA). The patch basically does the ...
12 years, 10 months ago (2011-06-10 18:17:34 UTC) #1
Le-Chun Wu
Just identified a bug in my previous patch after running the compiler on google code ...
12 years, 10 months ago (2011-06-10 23:56:09 UTC) #2
Diego Novillo
OK with some minor nits. Diego. http://codereview.appspot.com/4591066/diff/3001/gcc/tree-threadsafe-analyze.c File gcc/tree-threadsafe-analyze.c (right): http://codereview.appspot.com/4591066/diff/3001/gcc/tree-threadsafe-analyze.c#newcode1159 gcc/tree-threadsafe-analyze.c:1159: gcc_assert (false); >+ ...
12 years, 10 months ago (2011-06-11 17:52:51 UTC) #3
Le-Chun Wu
http://codereview.appspot.com/4591066/diff/3001/gcc/tree-threadsafe-analyze.c File gcc/tree-threadsafe-analyze.c (right): http://codereview.appspot.com/4591066/diff/3001/gcc/tree-threadsafe-analyze.c#newcode1159 gcc/tree-threadsafe-analyze.c:1159: gcc_assert (false); On 2011/06/11 17:52:51, Diego Novillo wrote: > ...
12 years, 10 months ago (2011-06-13 19:44:35 UTC) #4
Diego Novillo
12 years, 10 months ago (2011-06-13 19:54:03 UTC) #5
On Mon, Jun 13, 2011 at 12:44,  <lcwu@google.com> wrote:

>> could
>>  2149      be optimized away.  */
>>  2150   if (TREE_CODE (TREE_TYPE (DECL_ORIGIN (fdecl))) == METHOD_TYPE
>>  2151       && gimple_call_num_args(call) > 0)
>
>> Wouldn't it be easier to make fdecl == DECL_ORIGIN (fdecl) earlier in
>
> the
>>
>> function?
>
>> It's OK either way, though.
>
> Yes, my original fix was to make fdecl = DECL_ORIGINAL (fdecl). But I
> later changed it to this way because I wanted to tolerate the case where
> the base object (i.e. "this" pointer) is an object instead of a pointer
> only when fdecl is a clone. (i.e. I don't want to arbitrarily relax it.)
> That's why I kept fdecl intact.

Ah, makes sense.  Thanks.


Diego.
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b