This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Thu, Nov 22, 2012 at 02:28:18PM +0100, Paolo Carlini wrote:I think that the Valgrind complain is benign and, by the way, I just run the testsuite with current code + trivial_p initialized to true with no regressions. In detail what is happening is that, as you say, in the special case of deleted_p true and lambdas, we return from synthesized_method_walk and trivial_p is still uninitialized. Then we have:On 11/22/2012 01:06 PM, Markus Trippelsdorf wrote:The fix is trivial. I would appreciate if someone could commit this.I agree it qualifies as obvious and I mean to commit the patch on your behalf before the end of the day if nobody objects. To be super-safe, I guess I will also run the testsuite with the current code and trivial_p initialized to true at the beginning of the function.I think trivial_p used to be uninitialized only for deleted_p functions, not sure if those are considered trivial or not (and whether it matters)...
if (!trivial_p && type_has_trivial_fn (type, kind)) type_set_nontrivial_flag (type, kind);
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |