public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/109983] [12/13/14 regression] Wireshark compilation hangs with -O2 -fipa-pta
Date: Fri, 26 May 2023 09:28:38 +0000	[thread overview]
Message-ID: <bug-109983-4-ocqUMjmPNC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109983-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109983

--- Comment #1 from Sam James <sjames at gcc dot gnu.org> ---
I let perf spin for a while and got this w/ 13:

```
$ perf record gcc-13 -O2 -fipa-pta -c packet-rnsap.c.i
[^C'd after ~2 minutes]

$ perf report
    43.18%  cc1      cc1                      [.] bitmap_ior_into
    40.43%  cc1      cc1                      [.] bitmap_bit_p
     9.65%  cc1      cc1                      [.] bitmap_set_bit
     2.87%  cc1      cc1                      [.] solve_graph
     0.98%  cc1      cc1                      [.] solution_set_expand
     0.80%  cc1      cc1                      [.] add_graph_edge
     0.39%  cc1      cc1                      [.] find
     0.04%  cc1      cc1                      [.]
symbol_table::decl_assembler_name_hash
     0.04%  cc1      libc.so.6                [.] malloc
     0.03%  cc1      cc1                      [.] ggc_set_mark
     0.03%  cc1      cc1                      [.] verify_ssa
     0.03%  cc1      cc1                      [.] gt_ggc_mx_lang_tree_node
     0.03%  cc1      cc1                      [.] walk_gimple_op
     0.03%  cc1      cc1                      [.] walk_tree_1
     0.03%  cc1      cc1                      [.]
base_pool_allocator<memory_block_pool>::allocate
     0.03%  cc1      cc1                      [.] solve_constraints
     0.02%  cc1      cc1                      [.]
bitmap_list_insert_element_after
     0.02%  cc1      cc1                      [.] verify_gimple_call
     0.02%  cc1      libc.so.6                [.] cfree
     0.02%  cc1      cc1                      [.] ggc_internal_alloc
     0.02%  cc1      cc1                      [.] verify_gimple_in_cfg
     0.02%  cc1      cc1                      [.] equiv_class_lookup_or_add
     0.02%  cc1      cc1                      [.] verify_gimple_stmt
     0.02%  cc1      [unknown]                [k] 0xffffffff89000b90
     0.02%  cc1      cc1                      [.] do_per_function
     0.01%  cc1      cc1                      [.]
hash_table<default_hash_traits<tree_node*>, false, xcallocator>::verify
     0.01%  cc1      cc1                      [.] contains_struct_check
     0.01%  cc1      cc1                      [.]
hash_table<hash_map<nofree_string_hash, align_flags,
simple_hashmap_traits<default_hash_traits<nofree_string_hash>, align_flags>
>::hash_entry, false, xcallocator>::verify
     0.01%  cc1      cc1                      [.] free_dominance_info
     0.01%  cc1      cc1                      [.]
operands_scanner::get_expr_operands
     0.01%  cc1      cc1                      [.] verify_expr_location_1
     0.01%  cc1      cc1                      [.] _cpp_lex_direct
     0.01%  cc1      cc1                      [.] verify_location
     0.01%  cc1      cc1                      [.] (anonymous
namespace)::dom_info::calc_dfs_tree_nonrec
     0.01%  cc1      cc1                      [.] (anonymous
namespace)::dom_info::calc_idoms
[...]
```

  reply	other threads:[~2023-05-26  9:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-26  9:26 [Bug ipa/109983] New: " sjames at gcc dot gnu.org
2023-05-26  9:28 ` sjames at gcc dot gnu.org [this message]
2023-05-26  9:36 ` [Bug ipa/109983] " sjames at gcc dot gnu.org
2023-05-26 10:38 ` slyfox at gcc dot gnu.org
2023-05-26 10:48 ` sjames at gcc dot gnu.org
2023-05-26 11:04 ` slyfox at gcc dot gnu.org
2023-05-26 18:17 ` slyfox at gcc dot gnu.org
2023-05-26 20:03 ` slyfox at gcc dot gnu.org
2023-05-26 20:09 ` pinskia at gcc dot gnu.org
2023-05-30  7:25 ` rguenth at gcc dot gnu.org
2023-05-30  8:39 ` rguenth at gcc dot gnu.org
2023-05-30  9:08 ` rguenth at gcc dot gnu.org
2023-05-31 10:37 ` rguenth at gcc dot gnu.org
2023-05-31 10:49 ` rguenth at gcc dot gnu.org
2023-05-31 11:27 ` cvs-commit at gcc dot gnu.org
2023-05-31 11:27 ` rguenth at gcc dot gnu.org
2023-05-31 19:27 ` [Bug ipa/109983] [12/13 " sjames at gcc dot gnu.org
2023-06-06  8:42 ` rguenth at gcc dot gnu.org
2023-06-23 10:29 ` cvs-commit at gcc dot gnu.org
2023-11-27 11:34 ` [Bug ipa/109983] [12 " cvs-commit at gcc dot gnu.org
2023-11-27 11:38 ` rguenth 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-109983-4-ocqUMjmPNC@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).