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/m
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
* gcc/testsuite/g++.dg/thread-ann/thread_annot_lock-78.C: New test.
* gcc/tree-threadsafe-anal
, Apr 22, 2011 at 1:08 PM, Le-Chun Wu wrote:
>
> 2011-04-22 Le-Chun Wu
>
> gcc/c-family/ChangeLog:
> * c-common.c (check_for_self_assign): New function.
> * c-common.h: New function declaration.
> * c.opt: New option.
>
> gcc/Chang
2011-04-22 Le-Chun Wu
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
