c++: Avoid confusing 'nested' name
authorNathan Sidwell <nathan@acm.org>
Wed, 16 Sep 2020 15:05:26 +0000 (08:05 -0700)
committerNathan Sidwell <nathan@acm.org>
Wed, 16 Sep 2020 15:10:44 +0000 (08:10 -0700)
commit7d1be939e0fbc5ce63ba17db3d20ccc39ac17527
treee05d7d804829bfdbc5f724c1f1f64a466dc107d4
parent91347c3bbf788ede4af89f46206991c47fa8aceb
c++: Avoid confusing 'nested' name

instantiate_body has a local var call 'nested', which indicates that
this instantiation was caused during the body of some function -- not
necessarily its containing scope.  That's confusing, let's just use
'current_function_decl' directly.  Then we can also simplify the
push_to_top_level logic, which /does/ indicate whether this is an
actual nested function.  (C++ does not have nested functions, but OMP
ODRs fall into that category.  A follow up patch will use that more
usual meaning of 'nested' wrt to functions.)

gcc/cp/
* pt.c (instantiate_body): Remove 'nested' var, simplify
push_to_top logic.
gcc/cp/pt.c