https://sourceware.org/bugzilla/show_bug.cgi?id=31863
Nick Alcock changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://sourceware.org/bugzilla/show_bug.cgi?id=31863
--- Comment #6 from Sourceware Commits ---
The master branch has been updated by Nick Alcock :
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f86f9fd85999c7a483855793b3efe85da1d6eb74
commit f86f9fd85999c7a483855793b3efe85da1d6eb7
https://sourceware.org/bugzilla/show_bug.cgi?id=31863
--- Comment #5 from Nick Alcock ---
There is a caveat here: this has to be conditionalized further unless you want
to replace an ugly warning on one platform with an ugly warning with a
different compiler on all platforms, because clang doesn'
https://sourceware.org/bugzilla/show_bug.cgi?id=31863
Nick Alcock changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://sourceware.org/bugzilla/show_bug.cgi?id=31863
--- Comment #4 from Eli Zaretskii ---
(In reply to Nick Alcock from comment #3)
> Oh it hasn't -- I see the warnings on MinGW everywhere too. I was merely
> noting that this doesn't seem to align with the behaviour of the actual
> printf in th
https://sourceware.org/bugzilla/show_bug.cgi?id=31863
--- Comment #3 from Nick Alcock ---
Oh it hasn't -- I see the warnings on MinGW everywhere too. I was merely noting
that this doesn't seem to align with the behaviour of the actual printf in the
various libcs MinGW can use, which all seem to s
https://sourceware.org/bugzilla/show_bug.cgi?id=31863
--- Comment #2 from Eli Zaretskii ---
(In reply to Nick Alcock from comment #1)
> O. I wondered why this was happening!
>
> Will pull this fix in. Thank you very much! (The libcs MinGW can use all
> seem to support %z perfectly well, whic
https://sourceware.org/bugzilla/show_bug.cgi?id=31863
Eli Zaretskii changed:
What|Removed |Added
Target||MinGW
Host|
