public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tim Lange <mail@tim-lange.me>
To: GCC Mailing List <gcc@gcc.gnu.org>
Subject: Usage of the C++ stdlib unordered_map in GCC
Date: Tue, 30 Aug 2022 21:57:45 +0200	[thread overview]
Message-ID: <942GHR.WGPY8O255349@tim-lange.me> (raw)

Hello,

I was preparing a patch for GCC and used the unordered_map from the C++ 
stdlib in my patch. Later on, I noticed that it is used nowhere else 
inside GCC except for some files in the go frontend.

I wondered, now that building GCC requires a C++11 host compiler, 
whether there is a consensus on which data structure implementation is 
preferred. Should I rather use a hash_map instead of an unordered_map 
or is it on my side to decide which one I choose?

- Tim



             reply	other threads:[~2022-08-30 19:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 19:57 Tim Lange [this message]
2022-08-30 20:07 ` Marek Polacek
2022-08-31  9:37   ` Jonathan Wakely
2022-08-31 14:35     ` Jason Merrill
2022-08-31 14:35       ` Jason Merrill
2022-08-31 15:22       ` Tim Lange

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=942GHR.WGPY8O255349@tim-lange.me \
    --to=mail@tim-lange.me \
    --cc=gcc@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).