New warning (or at least I only noticed it now)

[Pavel Sanda]

On Tue, Nov 22, 2022 at 07:49:02AM +0100, Jean-Marc Lasgouttes wrote:
> Le 22 novembre 2022 03:04:39 GMT+01:00, Pavel Sanda <sanda at lyx.org> a écrit :
> >Nice, so now we know the culprit. The question is whether we want 
> >to get rid of reference on the left side or fix the temps on the right.
> 
> So what is the issue that the warning detect? I still don't get it.

My interpretation is that gcc is nervous about the temporary created via
getFont which is then propagated to the bottom via chain of refs and it's
not possible for it to decide whether returned value is independent of
that temp.

Note that I'm not claiming that there is some *real* issue (I did not find any),
it's just that we need to shut up that warning.

Another option would be to create MWE and send it to gcc bugzilla,
but I do not have gcc 13 to deliver it.

Pavel