public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fdumont at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/58153] unordered_multimap::erase(iterator) is not constant-time when many entries have the same key
Date: Sat, 24 Aug 2013 16:30:00 -0000	[thread overview]
Message-ID: <bug-58153-4-y7HEW7g8zy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58153-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58153

--- Comment #3 from François Dumont <fdumont at gcc dot gnu.org> ---
This report entry made me wonder why iterators could not just be pointing to
the node just before the one containing the pointed to value. For instance
begin() iterator would contained the before_begin one. This is rather
consistent with the data structure as we are using some kind of forward_list
which only propose an O(1) erase_after method. In this case erase(iterator)
will work just like erase_after.

I am going to challenge this approach and will let you know if it has no
drawback.
>From gcc-bugs-return-428342-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Aug 24 18:10:25 2013
Return-Path: <gcc-bugs-return-428342-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21815 invoked by alias); 24 Aug 2013 18:10:25 -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 21801 invoked by uid 48); 24 Aug 2013 18:10:23 -0000
From: "tammy at Cadence dot COM" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/58208] deque<std::string> 32-bit "-O3" bug
Date: Sat, 24 Aug 2013 18:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.8.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tammy at Cadence 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:
Message-ID: <bug-58208-4-apTMmnTAsM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58208-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58208-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-08/txt/msg01266.txt.bz2
Content-length: 440

http://gcc.gnu.org/bugzilla/show_bug.cgi?idX208

--- Comment #4 from Tammy Hsu <tammy at Cadence dot COM> ---
Sorry, I forgot to mention that I need to set LD_LIBRARY_PATH to "." to run
import.
I build the gcc473 and gcc481 by using the same configuration and on the same
RHEL 5.5 system, however the gcc473 version works and gcc481 with -m32
crash....

May I know how you configure your gcc481 or if you have added any extra bug
fixes?


  parent reply	other threads:[~2013-08-24 16:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14 10:11 [Bug libstdc++/58153] New: " temporal at gmail dot com
2013-08-14 10:35 ` [Bug libstdc++/58153] " redi at gcc dot gnu.org
2013-08-14 11:16 ` temporal at gmail dot com
2013-08-24 16:30 ` fdumont at gcc dot gnu.org [this message]
2013-08-24 19:16 ` temporal at gmail dot com
2013-08-26 20:06 ` fdumont at gcc dot gnu.org
2013-08-27  3:10 ` temporal at gmail dot com
2015-04-09 14:49 ` 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-58153-4-y7HEW7g8zy@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: link
Be 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).