public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/37743] Bogus printf format warning with __builtin_bswap32. Date: Tue, 07 Oct 2008 13:24:00 -0000 [thread overview] Message-ID: <20081007132254.27573.qmail@sourceware.org> (raw) In-Reply-To: <bug-37743-2018@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from jakub at gcc dot gnu dot org 2008-10-07 13:22 ------- I think the warning is desirable, the code isn't portable to non-32bit int targets. Wonder if we just shouldn't give a TYPE_NAME to uint32_type_node and uint64_type_node (__builtin_uint32_t and __builtin_uint64_t or something similar), then c-format would print that instead and the warning would be clearer. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37743
next prev parent reply other threads:[~2008-10-07 13:24 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-06 8:12 [Bug c/37743] New: " suckfish at ihug dot co dot nz 2008-10-06 21:56 ` [Bug c/37743] " pinskia at gcc dot gnu dot org 2008-10-06 21:57 ` pinskia at gcc dot gnu dot org 2008-10-07 13:24 ` jakub at gcc dot gnu dot org [this message] 2009-03-31 20:40 ` jsm28 at gcc dot gnu dot org 2010-06-11 14:56 ` pinskia at gcc dot gnu dot org [not found] <bug-37743-4@http.gcc.gnu.org/bugzilla/> 2012-03-27 7:46 ` rguenth at gcc dot gnu.org 2012-05-01 20:46 ` jyasskin at gcc dot gnu.org 2012-05-01 20:47 ` jyasskin at gcc dot gnu.org 2013-12-01 1:10 ` hp at gcc dot gnu.org 2014-02-19 6:50 ` jakub at gcc dot gnu.org 2014-02-19 17:37 ` joseph at codesourcery dot com 2014-02-19 22:28 ` jakub at gcc dot gnu.org 2014-03-06 8:11 ` jakub 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=20081007132254.27573.qmail@sourceware.org \ --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: linkBe 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).