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 c++/88115] Incorrect result from alignof in templates, if also using __alignof__. Date: Wed, 11 Nov 2020 20:11:49 +0000 [thread overview] Message-ID: <bug-88115-4-yZk0kfABlk@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 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>: https://gcc.gnu.org/g:b1c9b3c3408c1ec8043f9b9e1a148f84bb7f3b25 commit r11-4926-gb1c9b3c3408c1ec8043f9b9e1a148f84bb7f3b25 Author: Patrick Palka <ppalka@redhat.com> Date: Wed Nov 11 15:11:23 2020 -0500 c++: Change the mangling of __alignof__ [PR88115] This patch changes the mangling of __alignof__ to v111__alignof__, making its mangling distinct from that of alignof(type) and alignof(expr). How we mangle ALIGNOF_EXPR now depends on its ALIGNOF_EXPR_STD_P flag, which after the previous patch gets consistently set for alignof(type) as well as alignof(expr). gcc/c-family/ChangeLog: PR c++/88115 * c-opts.c (c_common_post_options): Update latest_abi_version. gcc/ChangeLog: PR c++/88115 * common.opt (-fabi-version): Document =15. * doc/invoke.texi (C++ Dialect Options): Likewise. gcc/cp/ChangeLog: PR c++/88115 * mangle.c (write_expression): Mangle __alignof_ differently from alignof when the ABI version is at least 15. libiberty/ChangeLog: PR c++/88115 * cp-demangle.c (d_print_comp_inner) <case DEMANGLE_COMPONENT_EXTENDED_OPERATOR>: Don't print the "operator " prefix for __alignof__. <case DEMANGLE_COMPONENT_UNARY>: Always print parens around the operand of __alignof__. * testsuite/demangle-expected: Test demangling for __alignof__. gcc/testsuite/ChangeLog: PR c++/88115 * g++.dg/abi/macro0.C: Adjust. * g++.dg/cpp0x/alignof7.C: New test. * g++.dg/cpp0x/alignof8.C: New test.
next prev parent reply other threads:[~2020-11-11 20:11 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 [this message] 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 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-yZk0kfABlk@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: linkBe 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).