public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug d/102765] [11 Regression] GDC11 stopped inlining library functions and lambdas used by a binary search one-liner code Date: Thu, 21 Apr 2022 07:50:35 +0000 [thread overview] Message-ID: <bug-102765-4-iDdCWhXqDT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102765-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102765 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|11.3 |11.4 --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- GCC 11.3 is being released, retargeting bugs to GCC 11.4.
next prev parent reply other threads:[~2022-04-21 7:50 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-15 6:54 [Bug d/102765] New: " siarhei.siamashka at gmail dot com 2021-11-05 13:33 ` [Bug d/102765] " rguenth at gcc dot gnu.org 2021-11-05 13:47 ` ibuclaw at gdcproject dot org 2021-12-09 2:33 ` siarhei.siamashka at gmail dot com 2022-02-01 3:47 ` siarhei.siamashka at gmail dot com 2022-04-21 7:50 ` rguenth at gcc dot gnu.org [this message] 2022-08-09 19:27 ` ibuclaw at gdcproject dot org 2022-10-13 5:45 ` ibuclaw at gdcproject dot org 2023-05-29 10:05 ` jakub 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-102765-4-iDdCWhXqDT@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).