Incidencia #42033

FC_VALUE_AFTER_EXIT() resulting in "unknown"

Abrir Fecha: 2021-04-20 09:46 Última actualización: 2021-04-23 03:50

Informador:
Propietario:
(Ninguno)
Tipo:
Estado:
Open
Componente:
Hito:
Prioridad:
5 - Medium
Gravedad:
5 - Medium
Resolución:
Ninguno
Fichero:
Ninguno

Details

FC_VALUE_AFTER_EXIT() usually results in "unknown" instead of "no". That's not very serious as "unknown" is handled as "no", and it's getting "yes" when it should.

Ticket History (3/5 Histories)

2021-04-20 09:46 Updated by: cazfi
  • New Ticket "FC_VALUE_AFTER_EXIT() resulting in "unknown"" created
2021-04-21 22:46 Updated by: cazfi
Comentario

These are the errors that cause it to fail even when it's not failing for the reason tested:

conftest.c:182:5: error: no previous prototype for 'func' -Werror=missing-prototypes
182 | int func(void)
| ~
conftest.c: In function 'main': conftest.c:187:1: error: old-style function definition -Werror=old-style-definition
187 | main ()
| ~
cc1: all warnings being treated as errors
2021-04-23 03:11 Updated by: cazfi
Comentario

Going to split missing-prototype part to a new ticket. It's the part that affects all branches. Once it's fixed, there should be no issue for S2_6 or S3_0.

old-style-definition warnings are enabled only in S3_1 and later.

2021-04-23 03:45 Updated by: cazfi
Comentario

Reply To cazfi

Going to split missing-prototype part to a new ticket.

-> #42058

2021-04-23 03:50 Updated by: cazfi

Attachment File List

No attachments

Editar

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