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++/97729] [11 Regression] Link failure due to basic_stringbuf and others when building DLL on MinGW Date: Mon, 09 Nov 2020 14:29:05 +0000 [thread overview] Message-ID: <bug-97729-4-cgSvLkKq0T@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97729-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97729 --- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:0af3930a497e022597a08fa1bcef5e453bfa636f commit r11-4839-g0af3930a497e022597a08fa1bcef5e453bfa636f Author: Jonathan Wakely <jwakely@redhat.com> Date: Mon Nov 9 10:16:07 2020 +0000 libstdc++: Use 'inline' consistently in std::exception_ptr [PR 97729] With PR c++/67453 fixed we can rely on the 'used' attribute to emit inline constructors and destructors in libsupc++/eh_ptr.cc. This means we don't need to suppress the 'inline' keyword on them in that file, and don't need to force 'always_inline' on them in other files. libstdc++-v3/ChangeLog: PR libstdc++/97729 * libsupc++/exception_ptr.h (exception_ptr::exception_ptr()) (exception_ptr::exception_ptr(const exception_ptr&)) (exception_ptr::~exception_ptr()): Remove 'always_inline' attributes. Use 'inline' unconditionally.
prev parent reply other threads:[~2020-11-09 14:29 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-05 12:51 [Bug libstdc++/97729] New: " markus.boeck02 at gmail dot com 2020-11-05 13:48 ` [Bug libstdc++/97729] " redi at gcc dot gnu.org 2020-11-05 13:49 ` [Bug libstdc++/97729] [11 Regression] " redi at gcc dot gnu.org 2020-11-05 14:00 ` markus.boeck02 at gmail dot com 2020-11-05 14:05 ` redi at gcc dot gnu.org 2020-11-05 14:20 ` markus.boeck02 at gmail dot com 2020-11-05 14:37 ` redi at gcc dot gnu.org 2020-11-05 18:01 ` cvs-commit at gcc dot gnu.org 2020-11-05 18:01 ` cvs-commit at gcc dot gnu.org 2020-11-05 18:05 ` redi at gcc dot gnu.org 2020-11-05 18:05 ` redi at gcc dot gnu.org 2020-11-05 19:22 ` markus.boeck02 at gmail dot com 2020-11-05 19:32 ` redi at gcc dot gnu.org 2020-11-09 14:29 ` cvs-commit at gcc dot gnu.org [this message]
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-97729-4-cgSvLkKq0T@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).