Incidencia #44611

Optimize some heavy MAX() and MIN() uses

Abrir Fecha: 2022-05-15 15:02 Última actualización: 2022-06-26 20:22

Informador:
Propietario:
Tipo:
Estado:
Open [Owner assigned]
Componente:
Hito:
Prioridad:
5 - Medium
Gravedad:
5 - Medium
Resolución:
Accepted
Fichero:
3

Details

We have some MAX() and MIN() uses where one of the parameters is relatively heavy to evaluate AND such that the compiler cannot optimize away the need to do the full evaluation twice (a function call of which compiler does not know that it will return the same value both times, and has no side-effects)

Move such heavy evaluations outside the macros, to do them only once.

Ticket History (3/6 Histories)

2022-05-15 15:02 Updated by: cazfi
  • New Ticket "Optimize some heavy MAX() and MIN() uses" created
2022-05-29 06:46 Updated by: cazfi
  • Hito Update from (Ninguno) to 3.0.3
2022-06-26 20:22 Updated by: cazfi
  • Propietario Update from (Ninguno) to cazfi
  • Resolución Update from Ninguno to Accepted
Comentario

For master I went through all MAX() and MIN() uses for candidates to change. For older branches I just ported those same changes, not checking if there would be additional candidates in them - except for porting gtk3.22-client changes to older gtk-clients supported only in older branches.

Editar

You are not logged in. I you are not logged in, your comment will be treated as an anonymous post. » Entrar