public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88101] Implement P0528R3, C++20 cmpxchg and padding bits
Date: Fri, 27 Nov 2020 10:25:34 +0000 [thread overview]
Message-ID: <bug-88101-4-nL5BIPwL9k@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-88101-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88101
--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:bf0a63a1f47525d1c466dbb84616dcb72010affa
commit r11-5490-gbf0a63a1f47525d1c466dbb84616dcb72010affa
Author: Jakub Jelinek <jakub@redhat.com>
Date: Fri Nov 27 11:23:45 2020 +0100
gimple-fold: Fix another __builtin_clear_padding ICE
When playing with __builtin_bit_cast, I have noticed
__builtin_clear_padding
ICE on the G class below. The artificial field with D type has offset 0
and size 8 bytes, but the following artificial field with E type has offset
0 and size 0, so it triggers the asserts that we don't move current
position
backwards. Fixed by ignoring is_empty_type (TREE_TYPE (field)) fields, all
of their bits are padding which is what is added when skipping over to next
field anyway.
2020-11-27 Jakub Jelinek <jakub@redhat.com>
PR libstdc++/88101
* gimple-fold.c (clear_padding_type): Ignore fields with
is_empty_type
types.
* g++.dg/torture/builtin-clear-padding-3.C: New test.
next prev parent reply other threads:[~2020-11-27 10:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-88101-4@http.gcc.gnu.org/bugzilla/>
2020-09-15 20:03 ` rodgertq at gcc dot gnu.org
2020-11-15 17:30 ` jakub at gcc dot gnu.org
2020-11-15 18:56 ` jakub at gcc dot gnu.org
2020-11-16 9:37 ` jakub at gcc dot gnu.org
2020-11-16 11:05 ` jakub at gcc dot gnu.org
2020-11-20 11:31 ` cvs-commit at gcc dot gnu.org
2020-11-27 10:25 ` cvs-commit at gcc dot gnu.org [this message]
2021-02-02 19:45 ` mpolacek at gcc dot gnu.org
2021-02-02 19:48 ` jakub at gcc dot gnu.org
2022-09-07 12:22 ` redi at gcc dot gnu.org
2022-09-08 18:37 ` redi 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-88101-4-nL5BIPwL9k@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).