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++/94929] [8 Regression] GCC 8 chokes on std::max in alignas Date: Sun, 03 May 2020 08:49:47 +0000 [thread overview] Message-ID: <bug-94929-4-GveaYmlnfz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94929-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94929 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail| |6.4.0, 7.5.0, 8.4.0 CC| |polacek at redhat dot com Ever confirmed|0 |1 Keywords| |rejects-valid Status|RESOLVED |NEW Known to work| |10.0, 11.0, 5.5.0, 9.2.0 Last reconfirmed| |2020-05-03 Resolution|DUPLICATE |--- --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- Hmm, although this was fixed for gcc 9.2 by the patch for PR 90736 it seems to be a different root cause. This compiled with GCC 5 but not 6, 7 or 8: template<typename T> constexpr const T& max(const T& a, const T& b) { return a < b ? b : a; } struct One {}; struct Two {}; struct Foo { alignas(max(alignof(One), alignof(Two))) char value; }; This regressed with r230365, "Merge C++ delayed folding branch." Marek, looks like backporting r272219 would fix this.
next prev parent reply other threads:[~2020-05-03 8:49 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-02 22:34 [Bug c++/94929] New: " soap at gentoo dot org 2020-05-03 8:44 ` [Bug c++/94929] [8 Regression] " redi at gcc dot gnu.org 2020-05-03 8:49 ` redi at gcc dot gnu.org [this message] 2020-05-04 6:43 ` rguenth at gcc dot gnu.org 2020-05-04 15:12 ` mpolacek at gcc dot gnu.org 2020-05-04 17:28 ` mpolacek at gcc dot gnu.org 2020-05-04 17:28 ` soap at gentoo dot org 2020-05-04 17:37 ` mpolacek 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-94929-4-GveaYmlnfz@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).