After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 722811 - Compile time warning in trionan.c
Compile time warning in trionan.c
Status: RESOLVED OBSOLETE
Product: libxml2
Classification: Platform
Component: general
git master
Other Linux
: Normal major
: ---
Assigned To: Daniel Veillard
libxml QA maintainers
Depends on:
Blocks:
 
 
Reported: 2014-01-23 02:47 UTC by Gaurav
Modified: 2021-07-05 13:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Gaurav 2014-01-23 02:47:17 UTC 
Libxml Version : 2.9.1

Warning Message : 
=========================
trionan.c:218: warning: ‘trio_is_negative’ defined but not used
=========================


Problem :
=================================
217 TRIO_PRIVATE int
218 trio_is_negative
219 TRIO_ARGS1((number),
220            double number)
221 {
===================================

This function is defined under flag : 
#if defined(USE_IEEE_754)

But, its usage :
=================================================
694 #  if defined(USE_IEEE_754)
695     *is_negative = trio_is_negative(number);
==================================================
It is under two more flags:
565 #if defined(fpclassify) && defined(signbit)   -->taking false
646 # if defined(TRIO_FPCLASSIFY)  -->Taking False
#  if defined(USE_IEEE_754)   -->Taking true
Comment 1 Nick Wellnhofer 2016-10-12 11:44:57 UTC 
I had a look at this, but it isn't trivial to fix. Whether these functions are used depends on a lot of macro magic in the Trio code. AFAICS, this has been addressed in newer version of Trio.
Comment 2 GNOME Infrastructure Team 2021-07-05 13:22:14 UTC 
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/libxml2/-/issues/

Thank you for your understanding and your help.