public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fragabr at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/54659] [4.8 Regression] Bootstrap with --disable-nls broken under Windows Date: Sun, 08 Sep 2013 00:55:00 -0000 [thread overview] Message-ID: <bug-54659-4-VrIHNL2Xf3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54659-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54659 Dâniel Fraga <fragabr at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fragabr at gmail dot com --- Comment #30 from Dâniel Fraga <fragabr at gmail dot com> --- (In reply to Diego Novillo from comment #29) > Fixed in gcc-4_8-branch at rev 198708 and trunk at rev 198711. Diego, I'm using gcc 4.8.2 20130905 snapshot and it's generating libstdc++ with those symbols: nm /usr/local/lib64/libstdc++.so.6.0.18|grep libintl U libintl_bindtextdomain U libintl_gettext U libintl_textdomain And I get the same problem reported in this bug. It started with gcc 4.8.0 and until now my workaround was to add "LDFLAGS=-lintl" when I compile some software. So I'm afraid this bug still exist or it was reintroduced at some point. Is there any test I can do for you? Thank you. >From gcc-bugs-return-429236-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Sep 08 01:59:57 2013 Return-Path: <gcc-bugs-return-429236-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 13157 invoked by alias); 8 Sep 2013 01:59:56 -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 11597 invoked by uid 48); 8 Sep 2013 01:59:50 -0000 From: "kariya_mitsuru at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/58358] New: search_n has a Complexxity violation for random access iterator Date: Sun, 08 Sep 2013 01:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 4.8.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: kariya_mitsuru at hotmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter Message-ID: <bug-58358-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-09/txt/msg00476.txt.bz2 Content-length: 798 http://gcc.gnu.org/bugzilla/show_bug.cgi?idX358 Bug ID: 58358 Summary: search_n has a Complexxity violation for random access iterator Product: gcc Version: 4.8.1 Status: UNCONFIRMED Severity: minor Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: kariya_mitsuru at hotmail dot com Following code should print less than or equal to 11, but it prints 20. #include <algorithm> #include <vector> #include <iostream> int main() { std::vector<int> a{2, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1}; int count = 0; std::search_n(a.begin(), a.end(), 10, 1, [&count](int t, int u){ ++count; return t == u; }); std::cout << count << std::endl; }
prev parent reply other threads:[~2013-09-08 0:55 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-21 16:54 [Bug bootstrap/54659] New: " burnus at gcc dot gnu.org 2012-09-21 16:55 ` [Bug bootstrap/54659] " burnus at gcc dot gnu.org 2012-10-26 10:36 ` burnus at gcc dot gnu.org 2012-10-26 12:05 ` rguenther at suse dot de 2012-10-26 12:35 ` dnovillo at google dot com 2012-10-26 12:36 ` rguenther at suse dot de 2012-12-02 5:51 ` nightstrike at gmail dot com 2012-12-06 16:46 ` rguenth at gcc dot gnu.org 2012-12-11 14:15 ` nightstrike at gmail dot com 2012-12-21 11:36 ` rguenth at gcc dot gnu.org 2012-12-21 11:42 ` rguenth at gcc dot gnu.org 2012-12-21 11:58 ` ebotcazou at gcc dot gnu.org 2012-12-21 14:33 ` rguenth at gcc dot gnu.org 2012-12-21 14:35 ` rguenth at gcc dot gnu.org 2012-12-21 16:00 ` ian at gcc dot gnu.org 2013-01-02 14:40 ` rguenth at gcc dot gnu.org 2013-03-25 18:30 ` josuegomes at gmail dot com 2013-03-25 21:53 ` roland at gnu dot org 2013-03-26 8:52 ` rguenth at gcc dot gnu.org 2013-03-26 10:48 ` dnovillo at gcc dot gnu.org 2013-03-26 22:03 ` roland at gnu dot org 2013-03-27 2:47 ` pinskia at gcc dot gnu.org 2013-04-29 9:25 ` jakub at gcc dot gnu.org 2013-04-29 16:46 ` dnovillo at google dot com 2013-05-07 15:08 ` dnovillo at gcc dot gnu.org 2013-05-07 16:55 ` dnovillo at gcc dot gnu.org 2013-05-07 16:56 ` dnovillo at gcc dot gnu.org 2013-05-07 17:07 ` roland at gnu dot org 2013-05-07 17:10 ` dnovillo at google dot com 2013-05-08 10:07 ` rguenther at suse dot de 2013-05-08 13:23 ` dnovillo at google dot com 2013-05-08 13:43 ` dnovillo at gcc dot gnu.org 2013-09-08 0:55 ` fragabr at gmail dot com [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-54659-4-VrIHNL2Xf3@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).