diff options
| author | Patrick Palka <ppalka@redhat.com> | 2026-02-12 15:14:11 -0500 |
|---|---|---|
| committer | Patrick Palka <ppalka@redhat.com> | 2026-02-12 15:14:11 -0500 |
| commit | 26713009e1ecef4ed0fc87e21a61fe0d4c1fe344 (patch) | |
| tree | 471e8e081baef06970cdd95304cb6f00b387475b /libjava/classpath/gnu/java/security/util | |
| parent | 0d51ed19504bcaa540763423763bb97227ed6c1c (diff) | |
| download | gcc-26713009e1ecef4ed0fc87e21a61fe0d4c1fe344.zip gcc-26713009e1ecef4ed0fc87e21a61fe0d4c1fe344.tar.gz gcc-26713009e1ecef4ed0fc87e21a61fe0d4c1fe344.tar.bz2 | |
c++: adjust comment from previous commit r16-7487
The comment from r16-7487 is confused, the object argument of PMF
calls _must_ be sequenced first by [expr.call]/7 since syntactically
it appears in the postfix-expression: (a.*pmf)(...).
It's indirect calls to a (known) xobj memfn that don't need such
sequencing, since syntactically the object argument isn't in the
postfix-expression: (&A::f)(a, ...).
gcc/cp/ChangeLog:
* cp-gimplify.cc (cp_gimplify_expr) <case CALL_EXPR>: Adjust
r16-7487 comment.
Diffstat (limited to 'libjava/classpath/gnu/java/security/util')
0 files changed, 0 insertions, 0 deletions