public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/52732] New: __builtin_bswapXX doesn't work with printf format
Date: Mon, 26 Mar 2012 22:14:00 -0000	[thread overview]
Message-ID: <bug-52732-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52732

             Bug #: 52732
           Summary: __builtin_bswapXX doesn't work with printf format
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: hjl.tools@gmail.com


Somehow, GCC gets very confused:

[hjl@gnu-6 gcc]$ cat /tmp/f.c
#include <stdio.h>

void
foo (int x, long y)
{
  printf ("%u\n", __builtin_bswap32 (x));
  printf ("%u\n", x);
  printf ("%lu\n", __builtin_bswap64 (x));
  printf ("%lu\n", y);
}
[hjl@gnu-6 gcc]$ ./xgcc -B./ -Wall -c /tmp/f.c
/tmp/f.c: In function ‘foo’:
/tmp/f.c:6:3: warning: format ‘%u’ expects argument of type ‘unsigned int’, but
argument 2 has type ‘unsigned int’ [-Wformat]
/tmp/f.c:8:3: warning: format ‘%lu’ expects argument of type ‘long unsigned
int’, but argument 2 has type ‘long unsigned int’ [-Wformat]
[hjl@gnu-6 gcc]$


             reply	other threads:[~2012-03-26 22:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-26 22:14 hjl.tools at gmail dot com [this message]
2012-03-26 23:47 ` [Bug c/52732] " joseph at codesourcery dot com
2012-03-27  7:45 ` rguenth at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-52732-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).