aboutsummaryrefslogtreecommitdiff
path: root/gcc/tree-data-ref.c
diff options
context:
space:
mode:
authorJakub Jelinek <jakub@redhat.com>2021-11-23 11:02:54 +0100
committerJakub Jelinek <jakub@redhat.com>2021-11-23 11:03:44 +0100
commit2780484bc376a89edb0c97b6b85209f4c27f34ee (patch)
treee5c066342cebb43318c69819acdf24d2b9e383ba /gcc/tree-data-ref.c
parent6033b27eade9c31c0be50657094c89ef9068892d (diff)
downloadgcc-2780484bc376a89edb0c97b6b85209f4c27f34ee.zip
gcc-2780484bc376a89edb0c97b6b85209f4c27f34ee.tar.gz
gcc-2780484bc376a89edb0c97b6b85209f4c27f34ee.tar.bz2
inliner: Remove unused transform_lang_insert_block hook
This struct copy_body_data's hook is always NULL since merge of the tuples branch, before that it has been shortly used by the C++ FE during ctor/dtor cloning to chain the remapped blocks, but only very shortly, before transform_lang_insert_block was a bool and the call to insert_block was done through a langhook. I'd say that for something that hasn't been used since 4.4 there is zero chance we'll want to use it again in the near future. 2021-11-23 Jakub Jelinek <jakub@redhat.com> gcc/ * tree-inline.h (struct copy_body_data): Remove transform_lang_insert_block member. * tree-inline.c (remap_block): Don't call id->transform_lang_insert_block. (optimize_inline_calls, copy_gimple_seq_and_replace_locals, tree_function_versioning, maybe_inline_call_in_expr, copy_fn): Don't initialize id.transform_lang_insert_block. * gimplify.c (gimplify_omp_loop): Likewise. gcc/c/ * c-typeck.c (c_clone_omp_udr): Don't initialize id.transform_lang_insert_block. gcc/cp/ * semantics.c (clone_omp_udr): Don't initialize id.transform_lang_insert_block. * optimize.c (clone_body): Likewise.
Diffstat (limited to 'gcc/tree-data-ref.c')
0 files changed, 0 insertions, 0 deletions