public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/5747] C99: Incorrect PRIu8 and PRIu16 in GNU <inttypes.h>
       [not found] <bug-5747-131@http.sourceware.org/bugzilla/>
@ 2014-07-02  7:33 ` fweimer at redhat dot com
  0 siblings, 0 replies; 3+ messages in thread
From: fweimer at redhat dot com @ 2014-07-02  7:33 UTC (permalink / raw)
  To: glibc-bugs

https://sourceware.org/bugzilla/show_bug.cgi?id=5747

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |security-

-- 
You are receiving this mail because:
You are on the CC list for the bug.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug libc/5747] C99: Incorrect PRIu8 and PRIu16 in GNU <inttypes.h>
  2008-02-07 20:28 [Bug libc/5747] New: " jeff dot sullivan at intel dot com
  2008-02-08  1:38 ` [Bug libc/5747] " drepper at redhat dot com
@ 2008-02-15 20:07 ` ebb9 at byu dot net
  1 sibling, 0 replies; 3+ messages in thread
From: ebb9 at byu dot net @ 2008-02-15 20:07 UTC (permalink / raw)
  To: glibc-bugs


------- Additional Comments From ebb9 at byu dot net  2008-02-15 20:07 -------
The compiler is technically right in warning, but the 'solution' proposed by the
OP is not correct.

When passed through ..., unsigned char promotes to 'int', not 'unsigned int'. 
Likewise for unsigned short, when int is larger than short.  If it were to
matter whether va_arg were handed 'int' vs. 'unsigned int', then PRIu8 and
PRIu16 should technically be "d" rather than "u" to match the type of the
argument promotion being used.  But for all practical implementations, 'int' and
'unsigned int' are the same width (or put another way, calling printf("%u",int)
works just fine on the platforms that glibc target).

In short, I agree with Ulrich's decision to not change the current code base.


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=5747

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug libc/5747] C99: Incorrect PRIu8 and PRIu16 in GNU <inttypes.h>
  2008-02-07 20:28 [Bug libc/5747] New: " jeff dot sullivan at intel dot com
@ 2008-02-08  1:38 ` drepper at redhat dot com
  2008-02-15 20:07 ` ebb9 at byu dot net
  1 sibling, 0 replies; 3+ messages in thread
From: drepper at redhat dot com @ 2008-02-08  1:38 UTC (permalink / raw)
  To: glibc-bugs


------- Additional Comments From drepper at redhat dot com  2008-02-08 01:38 -------
There is nothing wrong with the current definitions.  If your compiler issues
warnings this is your problem.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID
            Summary|C99: Incorrect PRIu8 and    |C99: Incorrect PRIu8 and
                   |PRIu16 in GNU <inttypes.h>  |PRIu16 in GNU <inttypes.h>


http://sourceware.org/bugzilla/show_bug.cgi?id=5747

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2014-07-02  7:33 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-5747-131@http.sourceware.org/bugzilla/>
2014-07-02  7:33 ` [Bug libc/5747] C99: Incorrect PRIu8 and PRIu16 in GNU <inttypes.h> fweimer at redhat dot com
2008-02-07 20:28 [Bug libc/5747] New: " jeff dot sullivan at intel dot com
2008-02-08  1:38 ` [Bug libc/5747] " drepper at redhat dot com
2008-02-15 20:07 ` ebb9 at byu dot net

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).