From: Kenneth Adam Miller <kennethadammiller@gmail.com>
To: QEMU Developers <qemu-devel@nongnu.org>
Subject: Error in accel/tcg?
Date: Mon, 19 Jul 2021 18:18:53 -0400 [thread overview]
Message-ID: <CAK7rcp8VU3DM3CTmM3upO9NxUBum3MLA3pLNk+yiNMuMqwKMDA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
Hello,
I get the following error:
<long cmd here> -c ../accel/tcg/cputlb.c
../qemu/accel/tcg/cputlb.c: In function 'tlb_flush_page_by_mmuidx':
../qemu/accel/tcg/cputlb.c:602:23: error: comparison is always true due to
limited range of data type [-Werror=type-limits]
} else if (idxmap < TARGET_PAGE_SIZE) {
I don't know why that suddenly shows up. The variable idxmap is a uint16_t
and I haven't changed that at all. Also, the TARGET_PAGE_SIZE is indicated
set by cscope/global tags in a specific header, and there's no reason to
believe that the value it takes happens to be larger than a uint16_t, so I
suppose that the static tags are lacking where the compiler evaluation
would indicate correctly.
In other parts of the code, I think somehow the meson build system is
triggering errors for warnings, so things like uninitialized variables that
have their address passed so that a called function can edit them are
making. But I didn't specifically turn on any of these warnings to error
settings. So my other thought is, perhaps because a version of gcc has some
implicit initialization for variables declared without initialization. I
checked that and resolved those. But I've been stumped for a while on the
idxmap problem.
[-- Attachment #2: Type: text/html, Size: 1348 bytes --]
next reply other threads:[~2021-07-19 22:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 22:18 Kenneth Adam Miller [this message]
2021-07-20 9:06 ` Error in accel/tcg? Peter Maydell
2021-07-20 15:06 ` Peter Maydell
2021-07-20 15:07 ` Peter Maydell
2021-07-20 15:13 ` Kenneth Adam Miller
2021-07-20 15:21 ` Peter Maydell
2021-07-20 15:06 ` Kenneth Adam Miller
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=CAK7rcp8VU3DM3CTmM3upO9NxUBum3MLA3pLNk+yiNMuMqwKMDA@mail.gmail.com \
--to=kennethadammiller@gmail.com \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).