2019-07-29 22:24:20 +02:00
|
|
|
/*===-- FixedMetadataKinds.def - Fixed metadata kind IDs -------*- C++ -*-=== *\
|
|
|
|
|
|*
|
|
|
|
|
|* Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
|
|
|
|
|
|* See https://llvm.org/LICENSE.txt for license information.
|
|
|
|
|
|* SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
|
|
|
|
|
|*
|
|
|
|
|
\*===----------------------------------------------------------------------===*/
|
|
|
|
|
|
|
|
|
|
#ifndef LLVM_FIXED_MD_KIND
|
|
|
|
|
#error "LLVM_FIXED_MD_KIND(EnumID, Name, Value) is not defined."
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_dbg, "dbg", 0)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_tbaa, "tbaa", 1)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_prof, "prof", 2)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_fpmath, "fpmath", 3)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_range, "range", 4)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_tbaa_struct, "tbaa.struct", 5)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_invariant_load, "invariant.load", 6)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_alias_scope, "alias.scope", 7)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_noalias, "noalias", 8)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_nontemporal, "nontemporal", 9)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_mem_parallel_loop_access,
|
|
|
|
|
"llvm.mem.parallel_loop_access", 10)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_nonnull, "nonnull", 11)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_dereferenceable, "dereferenceable", 12)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_dereferenceable_or_null, "dereferenceable_or_null", 13)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_make_implicit, "make.implicit", 14)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_unpredictable, "unpredictable", 15)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_invariant_group, "invariant.group", 16)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_align, "align", 17)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_loop, "llvm.loop", 18)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_type, "type", 19)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_section_prefix, "section_prefix", 20)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_absolute_symbol, "absolute_symbol", 21)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_associated, "associated", 22)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_callees, "callees", 23)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_irr_loop, "irr_loop", 24)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_access_group, "llvm.access.group", 25)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_callback, "callback", 26)
|
|
|
|
|
LLVM_FIXED_MD_KIND(MD_preserve_access_index, "llvm.preserve.access.index", 27)
|
2019-09-11 18:19:50 +02:00
|
|
|
LLVM_FIXED_MD_KIND(MD_misexpect, "misexpect", 28)
|
Reland: Dead Virtual Function Elimination
Remove dead virtual functions from vtables with
replaceNonMetadataUsesWith, so that CGProfile metadata gets cleaned up
correctly.
Original commit message:
Currently, it is hard for the compiler to remove unused C++ virtual
functions, because they are all referenced from vtables, which are referenced
by constructors. This means that if the constructor is called from any live
code, then we keep every virtual function in the final link, even if there
are no call sites which can use it.
This patch allows unused virtual functions to be removed during LTO (and
regular compilation in limited circumstances) by using type metadata to match
virtual function call sites to the vtable slots they might load from. This
information can then be used in the global dead code elimination pass instead
of the references from vtables to virtual functions, to more accurately
determine which functions are reachable.
To make this transformation safe, I have changed clang's code-generation to
always load virtual function pointers using the llvm.type.checked.load
intrinsic, instead of regular load instructions. I originally tried writing
this using clang's existing code-generation, which uses the llvm.type.test
and llvm.assume intrinsics after doing a normal load. However, it is possible
for optimisations to obscure the relationship between the GEP, load and
llvm.type.test, causing GlobalDCE to fail to find virtual function call
sites.
The existing linkage and visibility types don't accurately describe the scope
in which a virtual call could be made which uses a given vtable. This is
wider than the visibility of the type itself, because a virtual function call
could be made using a more-visible base class. I've added a new
!vcall_visibility metadata type to represent this, described in
TypeMetadata.rst. The internalization pass and libLTO have been updated to
change this metadata when linking is performed.
This doesn't currently work with ThinLTO, because it needs to see every call
to llvm.type.checked.load in the linkage unit. It might be possible to
extend this optimisation to be able to use the ThinLTO summary, as was done
for devirtualization, but until then that combination is rejected in the
clang driver.
To test this, I've written a fuzzer which generates random C++ programs with
complex class inheritance graphs, and virtual functions called through object
and function pointers of different types. The programs are spread across
multiple translation units and DSOs to test the different visibility
restrictions.
I've also tried doing bootstrap builds of LLVM to test this. This isn't
ideal, because only classes in anonymous namespaces can be optimised with
-fvisibility=default, and some parts of LLVM (plugins and bugpoint) do not
work correctly with -fvisibility=hidden. However, there are only 12 test
failures when building with -fvisibility=hidden (and an unmodified compiler),
and this change does not cause any new failures for either value of
-fvisibility.
On the 7 C++ sub-benchmarks of SPEC2006, this gives a geomean code-size
reduction of ~6%, over a baseline compiled with "-O2 -flto
-fvisibility=hidden -fwhole-program-vtables". The best cases are reductions
of ~14% in 450.soplex and 483.xalancbmk, and there are no code size
increases.
I've also run this on a set of 8 mbed-os examples compiled for Armv7M, which
show a geomean size reduction of ~3%, again with no size increases.
I had hoped that this would have no effect on performance, which would allow
it to awlays be enabled (when using -fwhole-program-vtables). However, the
changes in clang to use the llvm.type.checked.load intrinsic are causing ~1%
performance regression in the C++ parts of SPEC2006. It should be possible to
recover some of this perf loss by teaching optimisations about the
llvm.type.checked.load intrinsic, which would make it worth turning this on
by default (though it's still dependent on -fwhole-program-vtables).
Differential revision: https://reviews.llvm.org/D63932
llvm-svn: 375094
2019-10-17 11:58:57 +02:00
|
|
|
LLVM_FIXED_MD_KIND(MD_vcall_visibility, "vcall_visibility", 29)
|
