Re: [PATCH] c++: remove COMPOUND_EXPR_OVERLOADED flag

2021-12-13 Thread Jason Merrill via Gcc-patches
On 12/10/21 10:48, Patrick Palka wrote: This flag is never set because non-dependent COMPOUND_EXPRs are fully resolved into a CALL_EXPR at template definition time (in build_x_compound_expr) ever since r6-5772. Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK for trunk? OK.

Re: [PATCH] c++: remove COMPOUND_EXPR_OVERLOADED flag

2021-12-10 Thread Marek Polacek via Gcc-patches
On Fri, Dec 10, 2021 at 10:48:00AM -0500, Patrick Palka via Gcc-patches wrote: > This flag is never set because non-dependent COMPOUND_EXPRs are fully > resolved into a CALL_EXPR at template definition time (in > build_x_compound_expr) ever since r6-5772. > > Bootstrapped and regtested on x86_64-p

Re: [PATCH] c++: remove COMPOUND_EXPR_OVERLOADED flag

2021-12-10 Thread Patrick Palka via Gcc-patches
On Fri, Dec 10, 2021 at 10:48 AM Patrick Palka wrote: > > This flag is never set because non-dependent COMPOUND_EXPRs are fully Whoops, this should say, ... non-dependent COMPOUND_EXPRs that resolve to an overload are expressed as a CALL_EXPR at template definition time ... > resolved into a CAL

[PATCH] c++: remove COMPOUND_EXPR_OVERLOADED flag

2021-12-10 Thread Patrick Palka via Gcc-patches
This flag is never set because non-dependent COMPOUND_EXPRs are fully resolved into a CALL_EXPR at template definition time (in build_x_compound_expr) ever since r6-5772. Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK for trunk? gcc/cp/ChangeLog: * cp-tree.h (COMPOU