public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/59508] std::find could use specialized container's find Date: Sun, 15 Dec 2013 18:34:00 -0000 [thread overview] Message-ID: <bug-59508-4-9Z8ArR0BqQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59508-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59508 --- Comment #3 from Daniel Krügler <daniel.kruegler at googlemail dot com> --- (In reply to Oleg Endo from comment #2) > Could you please elaborate? My response was referring to the generic code that you provided, because that would also be applied to user-provided specializations of library containers and there iterator types. So it would only be feasible for a special scenario where the library would tag its internal types and where it can proof that the actual predicate used is equivalent to the usage of the associative container's predicate. >From gcc-bugs-return-437648-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 15 18:39:19 2013 Return-Path: <gcc-bugs-return-437648-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 5410 invoked by alias); 15 Dec 2013 18:39:19 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 5373 invoked by uid 48); 15 Dec 2013 18:39:15 -0000 From: "octoploid at yandex dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/59469] [4.8/4.9 Regression] LLVM build failure with gcc LTO Date: Sun, 15 Dec 2013 18:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: ipa X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: lto X-Bugzilla-Severity: normal X-Bugzilla-Who: octoploid at yandex dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-59469-4-SelnKZ69dq@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59469-4@http.gcc.gnu.org/bugzilla/> References: <bug-59469-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-12/txt/msg01303.txt.bz2 Content-length: 492 http://gcc.gnu.org/bugzilla/show_bug.cgi?idY469 --- Comment #16 from Markus Trippelsdorf <octoploid at yandex dot com> --- (In reply to H.J. Lu from comment #14) > (In reply to H.J. Lu from comment #13) > > Can you try bfd linker, hjl/linux/release/2.24.51.0.2, from > > > > https://sourceware.org/git/?p=binutils-gdb.git;a=summary > > > > It has a modified LTO bfd linker. > > You need to build LLVM from scratch with my bfd linker. I've tried your bfd version, but it doesn't help.
next prev parent reply other threads:[~2013-12-15 18:34 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-14 13:25 [Bug libstdc++/59508] New: " olegendo at gcc dot gnu.org 2013-12-15 16:38 ` [Bug libstdc++/59508] " daniel.kruegler at googlemail dot com 2013-12-15 17:28 ` olegendo at gcc dot gnu.org 2013-12-15 18:34 ` daniel.kruegler at googlemail dot com [this message] 2013-12-15 19:48 ` olegendo at gcc dot gnu.org 2013-12-16 17:04 ` redi at gcc dot gnu.org 2013-12-16 17:45 ` olegendo at gcc dot gnu.org 2024-01-08 10:58 ` 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-59508-4-9Z8ArR0BqQ@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).