public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107846] error: result of '8000 << 8' requires 22 bits to represent, but 'short int' only has 16 bits
Date: Wed, 23 Nov 2022 19:02:00 +0000 [thread overview]
Message-ID: <bug-107846-4-VoBgfL1WFW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107846-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107846
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to David Faust from comment #1)
> I think this is a bug in the test itself (or with these macros from libbpf).
No I think there might be a bug in GCC though I have to double check.
cc1: error: result of '8000 << 8' requires 22 bits to represent, but 'short
int' only has 16 bits [-Werror=shift-overflow=]
((__u16)(8000) << 8)
Hmm, we should have prompted that to int and not warned about it ...
next prev parent reply other threads:[~2022-11-23 19:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 17:45 [Bug target/107846] New: " james.hilliard1 at gmail dot com
2022-11-23 18:26 ` [Bug target/107846] " david.faust at oracle dot com
2022-11-23 19:02 ` pinskia at gcc dot gnu.org [this message]
2022-11-23 19:09 ` [Bug c/107846] [13 Regression] " pinskia at gcc dot gnu.org
2022-11-23 19:12 ` pinskia at gcc dot gnu.org
2022-11-23 19:20 ` jakub at gcc dot gnu.org
2022-11-29 15:26 ` jakub at gcc dot gnu.org
2022-11-29 18:57 ` james.hilliard1 at gmail dot com
2022-11-29 18:59 ` jakub at gcc dot gnu.org
2022-11-29 19:00 ` pinskia at gcc dot gnu.org
2022-11-29 19:06 ` james.hilliard1 at gmail dot com
2023-03-04 9:15 ` cvs-commit at gcc dot gnu.org
2023-03-04 9:24 ` 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=bug-107846-4-VoBgfL1WFW@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).