[google] Enhance Annotalysis to support cloned functions/methods (issue4591066)

to a value parameter by IPA-SRA. Bootstrapped and passed GCC regression testsuite on x86_64-unknown-linux-gnu. OK for google/main? Le-chun 2011-06-10 Le-Chun Wu l...@google.com * gcc/testsuite/g++.dg/thread-ann/thread_annot_lock-78.C: New test. * gcc/tree-threadsafe-analyze.c

[google] Enhance Annotalysis to support cloned functions/methods (issue4591066)

Just identified a bug in my previous patch after running the compiler on google code base. Basically the difference from the previous patch is for the compiler to handle the case where the parameters of a cloned method are optimized away. Bootstrapped OK. Testing is still on-going. OK for

[google] Port self-assign warning to google/main branch (issue4442075)

2011-04-22 Le-Chun Wu l...@google.com gcc/c-family/ChangeLog: * c-common.c (check_for_self_assign): New function. * c-common.h: New function declaration. * c.opt: New option. gcc/ChangeLog: * c-parser.c (c_parser_declaration_or_fndef): Check for self-assign

Re: [google] Port self-assign warning to google/main branch (issue4442075)

, Apr 22, 2011 at 1:08 PM, Le-Chun Wu l...@google.com wrote: 2011-04-22  Le-Chun Wu  l...@google.com gcc/c-family/ChangeLog:        * c-common.c (check_for_self_assign): New function.        * c-common.h: New function declaration.        * c.opt: New option. gcc/ChangeLog:        * c

Re: Plugin API Comments (was Re: GCC Plug-in Framework ready to port)

, we can start with those too. Thanks. Le-chun On Thu, Feb 5, 2009 at 3:27 PM, Taras Glek tg...@mozilla.com wrote: Le-Chun Wu wrote: Hi Sean, It's great that you updated the wiki page with the latest and more detailed API design. We (at Google) also started to look at the GCC plugin

Re: Plugin API Comments (was Re: GCC Plug-in Framework ready to port)

/positioning interface that I described? (Again, I will send out our patch later so that people can get a better idea if my description is not clear enough.) Le-chun Wu On Mon, Feb 2, 2009 at 2:42 PM, Sean Callanan spy...@cs.sunysb.edu wrote: I updated the page http://gcc.gnu.org/wiki

Re: Thread safety annotations and analysis in GCC

Ken, Thanks a lot for your feedback. Somehow your email fell through the cracks and I didn't notice it until a colleague of mine reminded me. Sorry for my delay in replying. Here are my answers to your questions. All the examples seem to be C++ oriented; is it, in fact, a goal for the

Re: How to determine if a decl is a class member in GCC

] wrote: Le-Chun Wu wrote: Hi, I haven't heard anything back on my questions. Can any of C++ frontend maintainers please shed some light (or comment on my proposed patch)? Thanks a lot. Le-chun On Fri, Jul 18, 2008 at 10:22 AM, Le-Chun Wu [EMAIL PROTECTED] wrote: Hi, In my attribute

Re: How to determine if a decl is a class member in GCC

Hi, I haven't heard anything back on my questions. Can any of C++ frontend maintainers please shed some light (or comment on my proposed patch)? Thanks a lot. Le-chun On Fri, Jul 18, 2008 at 10:22 AM, Le-Chun Wu [EMAIL PROTECTED] wrote: Hi, In my attribute handlers that handle the new thread

How to determine if a decl is a class member in GCC

Hi, In my attribute handlers that handle the new thread-safety attributes (in c-common.c), I need to check if a decl is a class member. How do people do that? My original code was checking if a decl is a FIELD_DECL but that doesn't work for static members. I also tried to use DECL_CONTEXT but it

thread-annotations branch created

Hi, I have created the branch thread-annotations that contains the implementation of the thread safety annotations and analysis (described in http://docs.google.com/Doc?id=ddqtfwhb_0c49t6zgr). I have committed the initial implementation and a set of new test cases to the branch. I've also created

Re: Thread safety annotations and analysis in GCC

Tom, Thanks a lot for pointing us to the sparse annotations. We will take a look and see what its support looks like. Le-chun On Sun, Jun 15, 2008 at 2:43 PM, Tom Tromey [EMAIL PROTECTED] wrote: Le-Chun == Le-Chun Wu [EMAIL PROTECTED] writes: Le-Chun Here is the design doc for the proposed

testsuite location for adding new tests

Hi, As part of our thread safety annotation/analysis effort, we created about 17 new test cases that we would like to add to the gcc testsuite. Should we create a new sub-directory under testsuite/g++.dg (say, for example, g++.dg/thread-ann)? Or should we add them to an existing sub-dir, e.g.

Re: Thread safety annotations and analysis in GCC

] wrote: Le-Chun Wu [EMAIL PROTECTED] writes: Please let me know if you have any feedback/comments/questions on the proposed annotations and the GCC implementation. I was surprised that there was no consideration of C indirect function calls in your design document. e.g. I would have expect some

Thread safety annotations and analysis in GCC

will send out another email once the public branch is created. Thanks, Le-Chun Wu ts_annotations.patch.gz Description: GNU Zip compressed data