[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #57270] [MXE Octave] Warnings during Octave co
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #57270] [MXE Octave] Warnings during Octave compilation |
Date: |
Thu, 21 Nov 2019 16:19:40 -0500 (EST) |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko |
Follow-up Comment #4, bug #57270 (project octave):
We shouldn't worry about the warnings in libgnu, that is not Octave code. If
you want you might report what you are seeing upstream with the gnulib
project.
The macro __MINGW_PRINTF_FORMAT is used in
build-aux/build-aux/mk-octave-config-h.sh and in oct-conf-post.in.h. It is
probably the latter instance that is causing the warning. The code is below.
It references a bug report and maybe there is some way to suppress the
warnings.
# if defined (__MINGW32__)
/* MinGW requires special handling due to different format specifiers
* on different platforms. The macro __MINGW_PRINTF_FORMAT maps to
* either gnu_printf or ms_printf depending on where we are compiling
* to avoid warnings on format specifiers that are legal.
* See: https://bugzilla.mozilla.org/show_bug.cgi?id=1331349 */
# define OCTAVE_FORMAT_PRINTF(stringIndex, firstToCheck) \
__attribute__ ((format (__MINGW_PRINTF_FORMAT, stringIndex,
firstToCheck)))
# define HAVE_OCTAVE_FORMAT_PRINTF_ATTR 1
# elif defined (__GNUC__)
/* The following attributes are used with gcc and clang compilers. */
# define OCTAVE_FORMAT_PRINTF(index, first) \
__attribute__ ((__format__(printf, index, first)))
# define HAVE_OCTAVE_FORMAT_PRINTF_ATTR 1
# else
# define OCTAVE_FORMAT_PRINTF(index, first)
/* # undef HAVE_OCTAVE_FORMAT_PRINTF_ATTR */
# endif
The warning in ls-hdf5.cc is not important. It just happens that 'char' on
the system you are using is mapped to int8 and so values above 127 are not
possible. But on other systems that map 'char' to 'uint8' this is possible so
the code needs to remain.
The warnings in sysdep.cc about comparing signed and unsigned integers is a
good find. I've attached a patch which should fix that.
The Qt warnings should be filed as a separate bug report.
So, the only thing I see remaining is the __MINGW_PRINTF_FORMAT warning.
(file #47919)
_______________________________________________________
Additional Item Attachment:
File name: 57270.patch Size:0 KB
<https://savannah.gnu.org/file/57270.patch?file_id=47919>
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?57270>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #57270] [MXE Octave] Warnings during Octave compilation, Guillaume, 2019/11/19
- [Octave-bug-tracker] [bug #57270] [MXE Octave] Warnings during Octave compilation, John Donoghue, 2019/11/19
- [Octave-bug-tracker] [bug #57270] [MXE Octave] Warnings during Octave compilation, John Donoghue, 2019/11/19
- [Octave-bug-tracker] [bug #57270] [MXE Octave] Warnings during Octave compilation, Guillaume, 2019/11/20
- [Octave-bug-tracker] [bug #57270] [MXE Octave] Warnings during Octave compilation,
Rik <=
- [Octave-bug-tracker] [bug #57270] [MXE Octave] Warnings during Octave compilation, Markus Mützel, 2019/11/22
- [Octave-bug-tracker] [bug #57270] [MXE Octave] Warnings during Octave compilation, Markus Mützel, 2019/11/22
- [Octave-bug-tracker] [bug #57270] [MXE Octave] Warnings during Octave compilation, Markus Mützel, 2019/11/23
- [Octave-bug-tracker] [bug #57270] [MXE Octave] Warnings during Octave compilation, Rik, 2019/11/23
- [Octave-bug-tracker] [bug #57270] [MXE Octave] Warnings during Octave compilation, Markus Mützel, 2019/11/23
- [Octave-bug-tracker] [bug #57270] [MXE Octave] Warnings during Octave compilation, Markus Mützel, 2019/11/24