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++/103387] powerpc64le: segmentation fault on std::cout with ieee128 long double variable Date: Fri, 21 Apr 2023 15:01:29 +0000 [thread overview] Message-ID: <bug-103387-4-XKFIzfxai7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103387-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103387 --- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:8caf5805ad76125b84430b8653003f4776489d46 commit r12-9462-g8caf5805ad76125b84430b8653003f4776489d46 Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Apr 20 21:02:22 2023 +0100 libstdc++: Optimize std::try_facet and std::use_facet [PR103755] The std::try_facet and std::use_facet functions were optimized in r13-3888-gb3ac43a3c05744 to avoid redundant checking for all facets that are required to always be present in every locale. This performs a simpler version of the optimization that only applies to std::ctype<char>, std::num_get<char>, std::num_put<char>, and the wchar_t specializations of those facets. Those are the facets that are cached by std::basic_ios, which means they're used on construction for every iostream object. This smaller change is suitable for the gcc-12 branch, and mitigates the performance loss for powerpc64le-linux on the gcc-12 branch caused by r12-9454-g24cf9f4c6f45f7 for PR 103387. It also greatly improves the performance of constructing iostreams objects, for all targets. libstdc++-v3/ChangeLog: PR libstdc++/103755 * include/bits/locale_classes.tcc (try_facet, use_facet): Do not check array index or dynamic type when accessing required specializations of std::ctype, std::num_get, or std::num_put. * testsuite/22_locale/ctype/is/string/89728_neg.cc: Adjust expected errors.
next prev parent reply other threads:[~2023-04-21 15:01 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-23 17:22 [Bug libstdc++/103387] New: " maxiwell at gmail dot com 2021-11-23 18:32 ` [Bug libstdc++/103387] " meissner at gcc dot gnu.org 2021-11-23 21:21 ` redi at gcc dot gnu.org 2021-11-24 22:37 ` tuliom at ascii dot art.br 2022-05-06 8:31 ` jakub at gcc dot gnu.org 2023-03-23 19:01 ` bergner at gcc dot gnu.org 2023-03-28 9:16 ` redi at gcc dot gnu.org 2023-03-28 14:54 ` redi at gcc dot gnu.org 2023-03-28 15:00 ` redi at gcc dot gnu.org 2023-03-28 16:48 ` redi at gcc dot gnu.org 2023-03-28 23:18 ` cvs-commit at gcc dot gnu.org 2023-03-28 23:19 ` redi at gcc dot gnu.org 2023-04-20 13:57 ` cvs-commit at gcc dot gnu.org 2023-04-20 16:38 ` redi at gcc dot gnu.org 2023-04-21 15:01 ` cvs-commit at gcc dot gnu.org [this message] 2023-04-21 15:03 ` 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-103387-4-XKFIzfxai7@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).