public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/56227] Bootstrap failure on MinGW building ggc-page.c
Date: Sat, 09 Feb 2013 08:18:00 -0000 [thread overview]
Message-ID: <bug-56227-4-Jo21V9CD3Q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56227-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56227
--- Comment #17 from Uros Bizjak <ubizjak at gmail dot com> 2013-02-09 08:17:41 UTC ---
(In reply to comment #16)
> I didn't notice that my backport to 4.7 caused:
>
> ../../gcc-svn/branches/gcc-4_7-branch/gcc/lto/lto.c:1060:68: warning: format
> ‘%wx’ expects argument of type ‘unsigned int’, but argument 2 has type ‘long
> unsigned int’ [-Wformat]
>
> However, "%wx" _is_ correct in this case, and it works for 4.8 without
> problems.
>
> Joseph, is there some additional magic that has to be added in lto/lto.c for
> %wx to pass the check?
To answer my own question - we have this typedef in output.h:
/* This is a magic identifier which allows GCC to figure out the type
of HOST_WIDE_INT for %wd specifier checks. You must issue this
typedef before using the __asm_fprintf__ format attribute. */
typedef HOST_WIDE_INT __gcc_host_wide_int__;
I am testing following additional patch:
--cut here--
Index: lto.c
===================================================================
--- lto.c (revision 195911)
+++ lto.c (working copy)
@@ -25,6 +25,7 @@
#include "toplev.h"
#include "tree.h"
#include "tree-flow.h"
+#include "output.h"
#include "diagnostic-core.h"
#include "tm.h"
#include "cgraph.h"
--cut here--
next prev parent reply other threads:[~2013-02-09 8:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 16:35 [Bug bootstrap/56227] New: " craig.powers at gmail dot com
2013-02-06 16:55 ` [Bug bootstrap/56227] " ubizjak at gmail dot com
2013-02-06 18:44 ` craig.powers at gmail dot com
2013-02-06 18:51 ` craig.powers at gmail dot com
2013-02-06 18:55 ` craig.powers at gmail dot com
2013-02-06 19:03 ` craig.powers at gmail dot com
2013-02-06 19:41 ` ubizjak at gmail dot com
2013-02-06 20:20 ` craig.powers at gmail dot com
2013-02-07 1:49 ` joseph at codesourcery dot com
2013-02-07 10:06 ` ubizjak at gmail dot com
2013-02-07 10:08 ` ubizjak at gmail dot com
2013-02-07 10:16 ` ktietz at gcc dot gnu.org
2013-02-07 13:00 ` ubizjak at gmail dot com
2013-02-07 18:03 ` uros at gcc dot gnu.org
2013-02-07 19:19 ` uros at gcc dot gnu.org
2013-02-07 19:21 ` ubizjak at gmail dot com
2013-02-09 8:02 ` ubizjak at gmail dot com
2013-02-09 8:18 ` ubizjak at gmail dot com [this message]
2013-02-09 9:48 ` ubizjak at gmail dot com
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-56227-4-Jo21V9CD3Q@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).