From: Andreas Schwab <schwab@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: kbuild test robot <lkp@intel.com>,
Stafford Horne <shorne@gmail.com>,
"kbuild-all\@01.org" <kbuild-all@01.org>,
Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
openrisc@lists.librecores.org,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] openrisc: Define __kernel_size_t to suppress compiler warnings
Date: Tue, 20 Dec 2016 23:44:43 +0100 [thread overview]
Message-ID: <871sx28bl0.fsf@linux-m68k.org> (raw)
In-Reply-To: <CAMuHMdUvXsiuHWuyiriyU5Y3ZJqRT2js++nXTwOd=WCdqArCTw@mail.gmail.com> (Geert Uytterhoeven's message of "Tue, 20 Dec 2016 21:45:56 +0100")
On Dez 20 2016, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> When I saw this patch, I was already a bit skeptical about it, but I noticed
> other architectures (e.g. avr32) are doing the same, so I didn't reply.
>
> In my experience, "format '%zu' expects argument of type 'size_t', but
> argument 3 has type 'unsigned int'" happens when using a compiler that
> was not configured to use the correct type (should be unsigned long) for
> size_t. Typically this happens when using a compiler not configured for
> a Linux target.
32-bit targets typically use unsigned int for size_t. It is part of the
ABI, so all compilers must agree. Since or32 is a out-of-tree port, and
gcc defaults to unsigned long for size_t, mismatches can happen if
people are using incomplete patches.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@linux-m68k.org>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH] openrisc: Define __kernel_size_t to suppress compiler warnings
Date: Tue, 20 Dec 2016 23:44:43 +0100 [thread overview]
Message-ID: <871sx28bl0.fsf@linux-m68k.org> (raw)
In-Reply-To: <CAMuHMdUvXsiuHWuyiriyU5Y3ZJqRT2js++nXTwOd=WCdqArCTw@mail.gmail.com> (Geert Uytterhoeven's message of "Tue, 20 Dec 2016 21:45:56 +0100")
On Dez 20 2016, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> When I saw this patch, I was already a bit skeptical about it, but I noticed
> other architectures (e.g. avr32) are doing the same, so I didn't reply.
>
> In my experience, "format '%zu' expects argument of type 'size_t', but
> argument 3 has type 'unsigned int'" happens when using a compiler that
> was not configured to use the correct type (should be unsigned long) for
> size_t. Typically this happens when using a compiler not configured for
> a Linux target.
32-bit targets typically use unsigned int for size_t. It is part of the
ABI, so all compilers must agree. Since or32 is a out-of-tree port, and
gcc defaults to unsigned long for size_t, mismatches can happen if
people are using incomplete patches.
Andreas.
--
Andreas Schwab, schwab at linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2016-12-20 22:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 13:59 [PATCH] openrisc: Define __kernel_size_t to suppress compiler warnings Stafford Horne
2016-12-20 13:59 ` [OpenRISC] " Stafford Horne
2016-12-20 20:22 ` kbuild test robot
2016-12-20 20:22 ` [OpenRISC] " kbuild test robot
2016-12-20 20:45 ` Geert Uytterhoeven
2016-12-20 20:45 ` [OpenRISC] " Geert Uytterhoeven
2016-12-20 22:44 ` Andreas Schwab [this message]
2016-12-20 22:44 ` Andreas Schwab
2016-12-20 23:02 ` Stafford Horne
2016-12-20 23:02 ` [OpenRISC] " Stafford Horne
2016-12-21 7:05 ` Geert Uytterhoeven
2016-12-21 7:05 ` [OpenRISC] " Geert Uytterhoeven
2016-12-21 4:06 ` kbuild test robot
2016-12-21 4:06 ` [OpenRISC] " kbuild test robot
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=871sx28bl0.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=openrisc@lists.librecores.org \
--cc=shorne@gmail.com \
--cc=stefan.kristiansson@saunalahti.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.