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 analyzer/107943] [11/12/13 Regression] gcc -fanalyzer hangs in openssl curve25519.c since r11-3840-gaf66094d03779377 Date: Thu, 30 Mar 2023 10:16:30 +0000 [thread overview] Message-ID: <bug-107943-4-8asZKCccSP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107943-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107943 --- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> --- Samples: 193K of event 'cycles', Event count (approx.): 206254655627 Overhead Samples Command Shared Object Symbol 12.11% 23476 cc1 cc1 [.] ana::store_manager::get_concrete_binding 9.71% 18828 cc1 cc1 [.] hash_table<hash_map<ana::concrete_binding, ana::concrete_binding*, simple_hashmap_traits<default_hash_traits<ana::concrete_binding>, ana::concrete_binding*> >::hash_entry, false, xcallocator>::find_with_hash 6.73% 13045 cc1 cc1 [.] hash_table<hash_map<ana::binding_key const*, ana::svalue const*, simple_hashmap_traits<default_hash_traits<ana::binding_key const*>, ana::svalue const*> >::hash_entry, false, xcallocator>::find_slot_with_hash 5.64% 10937 cc1 libc-2.31.so [.] _int_malloc 5.20% 10087 cc1 cc1 [.] ana::region_model_manager::get_or_create_constant_svalue 5.06% 9815 cc1 libc-2.31.so [.] _int_free 4.84% 9380 cc1 cc1 [.] hash_table<hash_map<ana::binding_key const*, ana::svalue const*, simple_hashmap_traits<default_hash_traits<ana::binding_key const*>, ana::svalue const*> >::hash_entry, false, xcallocator>::expand 4.63% 8971 cc1 cc1 [.] hash_table<hash_map<ana::element_region::key_t, ana::element_region*, simple_hashmap_traits<default_hash_traits<ana::element_region::key_t>, ana::element_region*> >::hash_entry, false, xcallocator>::find_with_hash 4.59% 8886 cc1 cc1 [.] iterative_hash 3.30% 6396 cc1 cc1 [.] ana::binding_cluster::bind_compound_sval 2.58% 4995 cc1 cc1 [.] ana::store::~store 2.19% 4250 cc1 cc1 [.] hash_table<hash_map<ana::binding_key const*, ana::svalue const*, simple_hashmap_traits<default_hash_traits<ana::binding_key const*>, ana::svalue const*> >::hash_entry, false, xcallocator>::find_with_hash looks like for larger workloads it gets memory bound - optimizing data structures (and hash functions?) might be helpful.
next prev parent reply other threads:[~2023-03-30 10:16 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-01 6:10 [Bug analyzer/107943] New: gcc -fanalyzer hangs in openssl curve25519.c bernd.edlinger at hotmail dot de 2022-12-01 10:11 ` [Bug analyzer/107943] " marxin at gcc dot gnu.org 2022-12-01 10:52 ` bernd.edlinger at hotmail dot de 2022-12-01 10:54 ` bernd.edlinger at hotmail dot de 2022-12-01 11:13 ` [Bug analyzer/107943] [11/12/13 Regression] gcc -fanalyzer hangs in openssl curve25519.c since r11-3840-gaf66094d03779377 marxin at gcc dot gnu.org 2022-12-01 14:10 ` marxin at gcc dot gnu.org 2022-12-05 4:56 ` bernd.edlinger at hotmail dot de 2023-01-13 10:22 ` rguenth at gcc dot gnu.org 2023-03-30 10:16 ` rguenth at gcc dot gnu.org [this message] 2023-03-30 11:01 ` rguenth at gcc dot gnu.org 2023-04-14 4:48 ` law at gcc dot gnu.org 2023-05-29 10:07 ` [Bug analyzer/107943] [11/12/13/14 " 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-107943-4-8asZKCccSP@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).