aboutsummaryrefslogtreecommitdiff
path: root/gcc/omp-simd-clone.c
diff options
context:
space:
mode:
authorMarek Polacek <polacek@redhat.com>2020-10-29 15:19:51 -0400
committerMarek Polacek <polacek@redhat.com>2020-11-03 10:09:53 -0500
commitc2856ceec2e7542fe9b0bf104afeeeeb57d6996d (patch)
tree028f74c4d0f6294d8f0d52ae0fed7a136fda09a9 /gcc/omp-simd-clone.c
parentf620e64a6f13371b95be5b17abba0acf15bf7cae (diff)
downloadgcc-c2856ceec2e7542fe9b0bf104afeeeeb57d6996d.zip
gcc-c2856ceec2e7542fe9b0bf104afeeeeb57d6996d.tar.gz
gcc-c2856ceec2e7542fe9b0bf104afeeeeb57d6996d.tar.bz2
c++: Tweaks for value_dependent_expression_p.
We may not call value_dependent_expression_p on expressions that are not potential constant expressions, otherwise value_d could crash, as I saw recently (in C++98). So beef up the checking in i_d_e_p. This revealed a curious issue: when we have __PRETTY_FUNCTION__ in a template function, we set its DECL_VALUE_EXPR to error_mark_node (cp_make_fname_decl), so potential_c_e returns false when it gets it, but value_dependent_expression_p handles it specially and says true. This broke lambda-generic-pretty1.C. So take care of that. And then also tweak uses_template_parms. gcc/cp/ChangeLog: * constexpr.c (potential_constant_expression_1): Treat __PRETTY_FUNCTION__ inside a template function as potentially-constant. * pt.c (uses_template_parms): Call instantiation_dependent_expression_p instead of value_dependent_expression_p. (instantiation_dependent_expression_p): Check potential_constant_expression before calling value_dependent_expression_p.
Diffstat (limited to 'gcc/omp-simd-clone.c')
0 files changed, 0 insertions, 0 deletions