public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/110798] [12 Regression] The reusult of sizeof operator followed with an 'unsigned typedef-ed generic integer' type is alway 4 bytes（except char）
Date: Tue, 25 Jul 2023 10:50:30 +0000 [thread overview]
Message-ID: <bug-110798-4-L1NnjkfKXg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110798-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110798
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|UNCONFIRMED |RESOLVED
Keywords|needs-bisection |
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> I almost positive this was fixed by r14-159-g03cebd304955a6 which was
> backported to GCC 13 branch r13-7277-ga713aa4f47ac1e (for 13.2.0) .
Yes, bisection confirms it. So this is a dup.
Aside: I'm not sure I'd call this a wrong-code bug. The testcase would be
simpler if it used static_assert instead of assert, which would make it
accepts-invalid / rejects-valid instead.
*** This bug has been marked as a duplicate of bug 108099 ***
next prev parent reply other threads:[~2023-07-25 10:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 6:49 [Bug c++/110798] New: " 13958014620 at 139 dot com
2023-07-25 6:59 ` [Bug c++/110798] [12/13 Regression] " pinskia at gcc dot gnu.org
2023-07-25 7:02 ` [Bug c++/110798] [12 " pinskia at gcc dot gnu.org
2023-07-25 7:14 ` 13958014620 at 139 dot com
2023-07-25 9:59 ` rguenth at gcc dot gnu.org
2023-07-25 10:39 ` redi at gcc dot gnu.org
2023-07-25 10:50 ` redi at gcc dot gnu.org [this message]
2023-07-26 5:11 ` 13958014620 at 139 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-110798-4-L1NnjkfKXg@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).