On Wed, Jun 17, 2026 at 08:53:01AM -0400, Patrick Palka wrote: > On Tue, 16 Jun 2026, Marek Polacek wrote: > > > On Fri, Jun 12, 2026 at 10:01:34PM +0800, Wang Jinghao wrote: > > > Bootstrapped/regtested on x86_64-pc-linux-gnu. > > > > > > -- >8 -- > > > eval_is_explicit_object_parameter() determines whether a parameter is > > > an explicit object parameter by checking whether the passed-in tree > > > node is the first parameter in its parameter chain. As described in > > > the comment for maybe_update_funtion_parm(), if the sequence is > > > > s/funtion/function/ > > > > > declaration -> reflection -> definition, the old PARM_DECL will be > > > compared against the new PARM_DECL, causing the check to produce an > > > incorrect result. > > > Calling maybe_update_function_parm() before the comparison updates > > > the old reflection to the new PARM_DECL in the chain, thereby > > > avoiding this error. > > > > Thanks, this patch looks good to me (though I can't approve it). > > Patch is OK then. Marek, wanna push it?
Pushed (https://gcc.gnu.org/r17-1626), thanks. Marek
