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 libstdc++/103755] {has,use}_facet() and iostream constructor performance Date: Fri, 11 Nov 2022 21:55:55 +0000 [thread overview] Message-ID: <bug-103755-4-YdcCmWczYD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103755-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103755 --- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> --- As I said in Bug 107632 comment 2: I'm kinda tempted to just disable the new optimization on these targets, the handling of compat facets for different float ABIs is impossible to get right.
next prev parent reply other threads:[~2022-11-11 21:55 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-17 3:49 [Bug libstdc++/103755] New: " dprokoptsev at gmail dot com 2021-12-17 10:31 ` [Bug libstdc++/103755] " redi at gcc dot gnu.org 2021-12-17 17:22 ` redi at gcc dot gnu.org 2021-12-17 17:52 ` redi at gcc dot gnu.org 2021-12-17 21:05 ` redi at gcc dot gnu.org 2021-12-19 3:41 ` dprokoptsev at gmail dot com 2021-12-19 3:44 ` dprokoptsev at gmail dot com 2021-12-19 13:04 ` redi at gcc dot gnu.org 2022-02-03 17:06 ` redi at gcc dot gnu.org 2022-09-23 12:57 ` redi at gcc dot gnu.org 2022-11-11 5:29 ` cvs-commit at gcc dot gnu.org 2022-11-11 13:27 ` redi at gcc dot gnu.org 2022-11-11 21:54 ` seurer at gcc dot gnu.org 2022-11-11 21:55 ` redi at gcc dot gnu.org [this message] 2022-11-11 22:39 ` redi at gcc dot gnu.org 2022-11-12 1:30 ` cvs-commit at gcc dot gnu.org 2022-11-12 2:00 ` redi at gcc dot gnu.org 2023-01-06 12:12 ` redi at gcc dot gnu.org 2023-01-11 14:07 ` redi at gcc dot gnu.org 2023-04-21 15:01 ` cvs-commit at gcc dot gnu.org 2023-04-21 15:06 ` 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-103755-4-YdcCmWczYD@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).