Home
last modified time | relevance | path

Searched refs:units (Results 1 – 25 of 220) sorted by relevance

123456789

/llvm-project-15.0.7/llvm/test/tools/llvm-dwarfutil/ELF/X86/
H A Dwarning-skipped-types.test2 ## contains type units.
4 …ge-collection --tombstone=maxpc %p/Inputs/type-units.o %t1 2>&1 | FileCheck %s -DFILE=%p/Inputs/ty…
6 # CHECK: [[FILE]]: warning: type units are not currently supported: file will be skipped
/llvm-project-15.0.7/llvm/test/DebugInfo/X86/
H A Daccel-tables-dwarf5.ll13 ; But not if also type units are enabled.
15 ; type units. Change this once DWARF v5 type units are implemented.
16 ; RUN: llc -mtriple=x86_64-pc-linux -filetype=obj -generate-type-units -debugger-tune=lldb < %s \
21 ; RUN: llc -mtriple=x86_64-apple-darwin12 -generate-type-units -filetype=obj < %s \
H A Dc-type-units.ll2 ; RUN: llc -o - %s -filetype=obj -O0 -debugger-tune=lldb -generate-type-units -mtriple=x86_64-unkno…
8 ; so we don't produce type units for them
11 source_filename = "test/DebugInfo/X86/c-type-units.ll"
H A Dstring-offsets-multiple-cus.ll3 ; RUN: llc -mtriple=x86_64-unknown-linux-gnu -filetype=obj -generate-type-units < %s | \
7 ; have multiple compile and type units. All units share one contribution to
29 ; Check that all 3 compile units have the correct DW_AT_str_offsets_base attributes
30 ; with the correct offsets. Check that strings referenced by compile units 2 and 3
35 ; Verify that all 3 type units have the proper DW_AT_str_offsets_base attribute.
H A Dgnu-names.ll16 ; No accelerator tables if type units are enabled, as DWARF v4 type units are
18 ; RUN: llc -mtriple=x86_64-pc-linux -filetype=obj -generate-type-units -debugger-tune=lldb < %s \
23 ; RUN: llc -mtriple=x86_64-apple-darwin12 -generate-type-units -filetype=obj < %s \
H A Daccel-tables.ll15 ; No accelerator tables if type units are enabled, as DWARF v4 type units are
17 ; RUN: llc -mtriple=x86_64-pc-linux -filetype=obj -generate-type-units -debugger-tune=lldb < %s \
22 ; RUN: llc -mtriple=x86_64-apple-darwin12 -generate-type-units -filetype=obj < %s \
H A Ddwarfdump-str-offsets-v4-dwarf64-dwp.s2 ## referenced by units in different formats: one unit is DWARF32 and another
5 ## This also checks that attributes in the units which use the DW_FORM_strx form
59 ## For simplicity and to make the test shorter, both compilation units share
/llvm-project-15.0.7/clang/test/ASTMerge/interface/
H A Dtest.m5 …ariable 'ivar2' declared with incompatible types in different translation units ('float' vs. 'int')
10 …class method 'foo' has incompatible result types in different translation units ('float' vs. 'int')
12 …od 'bar:' has a parameter with a different types in different translation units ('float' vs. 'int')
16 …od 'bar:' has a parameter with a different types in different translation units ('double' vs. 'flo…
/llvm-project-15.0.7/clang/test/ASTMerge/category/
H A Dtest.m5 …e method 'method2' has incompatible result types in different translation units ('float' vs. 'int')
7 …e method 'method3' has incompatible result types in different translation units ('float' vs. 'int')
9 …ance method 'blah' has incompatible result types in different translation units ('int' vs. 'float')
/llvm-project-15.0.7/clang/docs/
H A DLTOVisibility.rst7 translation units linked together into an executable or DSO, and a linkage
21 units. A class with public LTO visibility may be defined in multiple linkage
22 units, but the tradeoff is that the whole-program devirtualization and
25 of its definition, so it must be consistent between translation units.
27 In translation units built with LTO, LTO visibility is based on the
63 visibility attributes in multiple linkage units and have virtual calls
64 to derived classes in other linkage units work correctly. One example of
80 cases involving two linkage units, ``main`` and ``dso.so``.
106 these linkage units.
H A DStandardCPlusPlusModules.rst55 A module consists of one or more module units. A module unit is a special
67 In this document, module units are classified into:
83 units with the same declaration.
312 Remember that module units still have an object counterpart to the BMI
317 Module units are translation units. We need to compile them to object files
329 And the compilation process for module units are like:
339 …But we can't do this for the BMI from header units. See the later section for the definition of he…
600 In consistent filename suffix requirement for importable module units
749 Header units have pretty similar semantics with Clang modules.
779 However, these things are not part of Standard C++ Header units,
[all …]
/llvm-project-15.0.7/clang/test/ASTMerge/property/
H A Dtest.m5 …roperty 'Prop1' declared with incompatible types in different translation units ('int' vs. 'float')
7 …nce method 'Prop1' has incompatible result types in different translation units ('int' vs. 'float')
9 …operty 'Prop2' is synthesized to different ivars in different translation units ('ivar3' vs. 'ivar…
/llvm-project-15.0.7/clang/include/clang/Basic/
H A DDiagnosticASTKinds.td416 "translation units (%1 vs. %2)">;
419 "translation units (%1 vs. %2)">,
429 "translation units (%1 vs. %2)">;
432 "translation units (%1 vs. %2)">,
436 "units">;
439 "units">,
456 "translation units (%1 vs. %2)">;
459 "translation units (%1 vs. %2)">,
465 "translation units (%1 vs. %2)">;
525 "units (%1 vs. %2)">;
[all …]
/llvm-project-15.0.7/lldb/packages/Python/lldbsuite/test/test_runner/
H A Dprocess_control.py69 units = match.group(2)
70 if units is None:
73 elif units == 's':
76 elif units == 'm':
79 elif units == 'h':
82 elif units == 'd':
86 raise Exception("unexpected units value '{}'".format(units))
/llvm-project-15.0.7/llvm/test/DebugInfo/
H A Ddwarfdump-type-units.test1 RUN: llvm-dwarfdump -v %p/Inputs/dwarfdump-type-units.elf-x86-64 | FileCheck -check-prefix=INFO -ch…
2 RUN: llvm-dwarfdump -debug-types -debug-info %p/Inputs/dwarfdump-type-units.elf-x86-64 -summarize-t…
3 RUN: llvm-dwarfdump -v -debug-types %p/Inputs/dwarfdump-type-units.elf-x86-64 | FileCheck -check-pr…
/llvm-project-15.0.7/llvm/test/DebugInfo/WebAssembly/
H A Ddwarf-headers.ll1 ; RUN: llc -dwarf-version=4 -generate-type-units \
6 ; RUN: -dwarf-version=4 -generate-type-units \
11 ; RUN: llc -dwarf-version=5 -generate-type-units \
16 ; RUN: -dwarf-version=5 -generate-type-units \
64 ; Verify the v5 non-split headers. Type units come first.
/llvm-project-15.0.7/llvm/test/CodeGen/X86/
H A Ddwarf-headers.ll1 ; RUN: llc -dwarf-version=4 -generate-type-units \
6 ; RUN: -dwarf-version=4 -generate-type-units \
11 ; RUN: llc -dwarf-version=5 -generate-type-units \
16 ; RUN: -dwarf-version=5 -generate-type-units \
62 ; Verify the v5 non-split headers. Type units come first.
/llvm-project-15.0.7/lldb/test/Shell/SymbolFile/DWARF/
H A Ddebug-types-expressions.test3 # Make sure DWARF v4 type units work.
13 # Test type units in dwo files.
20 # And type units+dwo+dwarf5.
/llvm-project-15.0.7/llvm/test/tools/llvm-dwp/X86/
H A Dtype_dedup_v5.test1 # This test checks if llvm-dwp can deduplicate tu units (v5).
11 # CHECK: version = 5, units = 1, slots = 2
/llvm-project-15.0.7/lldb/docs/use/
H A Dtroubleshooting.rst15 etc), LLDB by default will only search for compile units whose filename
37 This tells LLDB to always look in all compile units and search for breakpoint
39 Setting breakpoints in header files always searches all compile units because
61 Checking if a module has any compile units (source files) is a good way to
80 We can also list the full paths to all compile units for a module using python:
/llvm-project-15.0.7/llvm/include/llvm/Target/
H A DTargetItinerary.td18 // Processor functional unit - These values represent the function units
45 // the choice of functional units that can be used to complete the
56 class InstrStage<int cycles, list<FuncUnit> units,
60 list<FuncUnit> Units = units; // choice of functional units
150 // the list of functional units that are included in the combination.
/llvm-project-15.0.7/lldb/test/Shell/SymbolFile/DWARF/x86/
H A Ddebug-types-basic.test3 # Make sure DWARF v4 type units work.
15 # Test type units in dwo files.
21 # And type units+dwo+dwarf5.
/llvm-project-15.0.7/llvm/lib/Target/VE/
H A DVECallingConv.td17 // F128 are assigned to the stack in 16-byte aligned units
20 // All of the rest are assigned to the stack in 8-byte aligned units.
54 // Alternatively, they are assigned to the stack in 8-byte aligned units.
72 // F128 are assigned to the stack in 16-byte aligned units
/llvm-project-15.0.7/llvm/lib/Target/Lanai/
H A DLanaiCallingConv.td26 // Otherwise they are assigned to the stack in 4-byte aligned units.
38 // Otherwise they are assigned to the stack in 4-byte aligned units.
/llvm-project-15.0.7/llvm/test/DebugInfo/Generic/
H A Ddebuginfofinder-inlined-cu.ll4 ; Verify that both compile units, even though one compile units's functions

123456789