public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88115] Incorrect result from alignof in templates, if also using __alignof__.
Date: Mon, 01 Feb 2021 14:16:18 +0000 [thread overview]
Message-ID: <bug-88115-4-xw0EnVOHdO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-88115-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88115
Patrick Palka <ppalka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |ppalka at gcc dot gnu.org
CC| |ppalka at gcc dot gnu.org
--- Comment #11 from Patrick Palka <ppalka at gcc dot gnu.org> ---
(In reply to James Y Knight from comment #10)
> Seeing as GCC is now in Stage 4 before the next release, I'd like to ping
> this bug.
>
> Should the priority be upgraded? I think fixing this so that GCC doesn't use
> 'v111__alignof__' should be considered a release-blocker: either the
> mangling change should be reverted to the previous behavior, or fixed.
Yes, thanks for the ping. I'll work on a patch for GCC 11 to follow suit, so
that Clang and GCC do the same thing.
>
> FWIW, the change to clang has been committed, and is planned to be in the
> upcoming Clang 12 release
> (https://reviews.llvm.org/rG9c7aeaebb3ac1b94200b59b111742cb6b8f090c2)
next prev parent reply other threads:[~2021-02-01 14:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-88115-4@http.gcc.gnu.org/bugzilla/>
2020-10-05 9:22 ` redi at gcc dot gnu.org
2020-10-07 14:52 ` cvs-commit at gcc dot gnu.org
2020-10-08 23:32 ` cvs-commit at gcc dot gnu.org
2020-11-11 20:11 ` cvs-commit at gcc dot gnu.org
2020-11-11 20:11 ` cvs-commit at gcc dot gnu.org
2020-11-13 14:23 ` cvs-commit at gcc dot gnu.org
2020-11-15 3:26 ` foom at fuhm dot net
2020-11-17 1:23 ` foom at fuhm dot net
2020-11-17 14:14 ` redi at gcc dot gnu.org
2021-01-07 23:13 ` foom at fuhm dot net
2021-01-29 17:57 ` foom at fuhm dot net
2021-02-01 14:16 ` ppalka at gcc dot gnu.org [this message]
2021-03-31 2:58 ` cvs-commit at gcc dot gnu.org
2021-04-21 12:08 ` cvs-commit at gcc dot gnu.org
2021-04-21 12:10 ` ppalka 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-88115-4-xw0EnVOHdO@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).