Home
last modified time | relevance | path

Searched refs:labels (Results 1 – 25 of 162) sorted by relevance

1234567

/llvm-project-15.0.7/flang/lib/Semantics/
H A Dresolve-labels.cpp816 for (const parser::Label &label : labels) { in AddLabelReference()
857 const auto iter{labels.find(label)}; in GetLabel()
858 if (iter == labels.cend()) { in GetLabel()
871 auto branchTarget{GetLabel(labels, label)}; in CheckBranchesIntoDoBody()
927 auto doTarget{GetLabel(labels, label)}; in CheckLabelDoConstraints()
976 auto target{GetLabel(labels, label)}; in CheckScopeConstraints()
1014 auto branchTarget{GetLabel(labels, label)}; in CheckBranchTargetConstraints()
1048 auto ioTarget{GetLabel(labels, label)}; in CheckDataXferTargetConstraints()
1073 auto target{GetLabel(labels, label)}; in CheckAssignTargetConstraints()
1096 CheckAssignTargetConstraints(assigns, labels, context); in CheckAssignConstraints()
[all …]
H A Dcheck-coarray.cpp25 std::set<parser::Label> labels() { return labels_; } in labels() function in Fortran::semantics::CriticalBodyEnforce
146 context_, criticalBodyEnforce.labels(), criticalStmt.source, "CRITICAL"}; in Enter()
/llvm-project-15.0.7/openmp/runtime/tools/
H A DsummarizeStats.py65 def set_varlabels(self, labels): argument
66 self.set_thetagrids(theta * 180/np.pi, labels,fontsize=14)
181 labels = [0.2, 0.4, 0.6, 0.8, 1, 2, 3, 4, 5, 10]
185 ax.set_rgrids(labels)
244 labels = ["Compute - " + "%.2f" % sizes[0], "Non Compute - " + "%.2f" % sizes[1]]
248 plt.legend(patches[0], labels, loc='best', bbox_to_anchor=(-0.1,1), fontsize=16)
253 labels = data.keys()
260 labels[i] = labels[i] + " - %.2f" % percent[i]
265 plt.legend(patches[0], labels, loc='best', bbox_to_anchor=(-0.1,1), fontsize=16)
/llvm-project-15.0.7/llvm/docs/
H A DBugLifeCycle.rst31 Furthermore, some of the metadata in the bug tracker, such as what labels we
44 You can apply `labels <https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/…
55 should be added along with any other labels that help to classify the report,
77 * When able to do so, please add the appropriate labels to classify the bug,
93 `documentation for our labels <https://github.com/llvm/llvm-project/labels>`_.
143 Project member with write access to the project can create new labels, but we
144 discourage adding ad hoc labels because we want to control the proliferation of
145 labels and avoid single-use labels. If you would like a new label added, please
/llvm-project-15.0.7/clang/docs/
H A DDataFlowSanitizerDesign.rst12 a number of taint labels with any data stored in any memory region
14 it operates on a running program, and tracks how the labels propagate
29 A number of functions are provided which will attach taint labels to
30 memory regions and extract the set of labels associated with a
132 operands, such as addition), we can simply OR the two labels in O(1).
134 Users are responsible for managing the 8 integer labels (i.e., keeping
135 track of what labels they have used so far, picking one that is yet
209 with each byte or bit of data, as some other tools do. Instead, labels are
211 all shadow labels corresponding to bytes loaded, and stores will
215 Propagating labels through arguments
[all …]
H A DDataFlowSanitizer.rst69 ABI or whether it should use a variant of this ABI that also propagates labels
71 how labels are propagated in the former case. DataFlowSanitizer comes with a
117 propagate labels in shadow memory.
141 category, which will make all stores and return values set zero labels.
183 * ``-dfsan-combine-offset-labels-on-gep`` -- Controls whether to propagate
202 labels of just ``v1`` and ``v2``.
269 DataFlowSanitizer supports up to 8 labels, to achieve low CPU and code
270 size overhead. Base labels are simply 8-bit unsigned integers that are
271 powers of 2 (i.e. 1, 2, 4, 8, ..., 128), and union labels are created
272 by ORing base labels.
[all …]
/llvm-project-15.0.7/llvm/test/CodeGen/X86/
H A Dbasic-block-sections-labels.ll1 ; Check the basic block sections labels option
2 …6_64 -function-sections -unique-section-names=true -basic-block-sections=labels | FileCheck %s --c…
3 …_64 -function-sections -unique-section-names=false -basic-block-sections=labels | FileCheck %s --c…
4 …6_64 -function-sections -unique-section-names=true -basic-block-sections=labels -split-machine-fun…
H A Dbasic-block-sections-labels-empty-function.ll2 ; RUN: llc < %s -mtriple=x86_64 -basic-block-sections=labels | FileCheck %s
/llvm-project-15.0.7/.github/workflows/
H A Dclosed-issues.yml7 automate-issues-labels:
13 remove-labels: 'awaiting-review'
H A Dnew-issues.yml7 automate-issues-labels:
13 add-labels: 'new issue'
H A Dllvm-bugs.yml41 labels : issue.data.labels.map((label) => label.name),
/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/dex/command/
H A DParseCommand.py81 def _build_command(command_type, labels, addresses, raw_text: str, path: str, lineno: str) -> Comma… argument
93 line = labels.get(label_name, None)
218 def add_line_label(labels, label, cmd_path, cmd_lineno): argument
220 if label.eval() in labels:
230 labels[label.eval()] = label.get_line()
248 labels = {} # dict of {name: line}.
295 labels,
319 add_line_label(labels, command, path, cmd_point.get_lineno())
/llvm-project-15.0.7/llvm/test/Instrumentation/DataFlowSanitizer/
H A Dlookup_table.ll1 ; RUN: opt < %s -dfsan -dfsan-combine-pointer-labels-on-load=false -dfsan-combine-offset-labels-on-…
2 ; RUN: opt < %s -dfsan -dfsan-combine-pointer-labels-on-load=false -dfsan-combine-offset-labels-on-…
H A Ddont_combine_offset_labels_on_gep.ll1 ; RUN: opt < %s -dfsan -dfsan-combine-offset-labels-on-gep=false -S | FileCheck %s
2 ; RUN: opt < %s -dfsan -dfsan-combine-offset-labels-on-gep=false -dfsan-track-origins=1 -S | FileCh…
/llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/hicpp/
H A Dmultiway-paths-covered.rst9 …dard.com/rule/6-1-4-ensure-that-a-switch-statement-has-at-least-two-case-labels-distinct-from-the-…
60 …dard.com/rule/6-1-4-ensure-that-a-switch-statement-has-at-least-two-case-labels-distinct-from-the-…
61 requires every ``switch`` statement to have at least two ``case`` labels other than a `default` lab…
63 Degenerated ``switch`` statements without any labels are caught as well.
H A Davoid-goto.rst8 Rule `6.3.1 High Integrity C++ <http://www.codingstandard.com/rule/6-3-1-ensure-that-the-labels-for…
/llvm-project-15.0.7/llvm/test/MC/PowerPC/
H A Dppc64-prefix-align-labels.s7 # it is added correctly with resepect to the labels in the .s file.
8 # The test contains 3 labels at the end (1:, 2:, 3:). The label 2: is on the
/llvm-project-15.0.7/llvm/test/Transforms/SimplifyCFG/
H A Dbbi-23595.ll8 ; As those basic blocks are now empty, their associated labels are removed.
10 ; For the given test case, the labels 'W' and 'cleanup4' are removed.
/llvm-project-15.0.7/llvm/utils/vim/indent/
H A Dllvm.vim45 " Indent labels the same as the current opening block
66 " Add a 'shiftwidth' after lines that start a block or labels
/llvm-project-15.0.7/clang/test/SemaCXX/
H A Dswitch-implicit-fallthrough.cpp268 expected-warning{{unannotated fall-through between switch labels}} \ in fallthrough_in_local_class()
288 expected-warning{{unannotated fall-through between switch labels}} \ in fallthrough_in_lambda()
H A Dswitch-implicit-fallthrough-blocks.cpp13 expected-warning{{unannotated fall-through between switch labels}} \ in fallthrough_in_blocks()
/llvm-project-15.0.7/llvm/test/MC/X86/AlignedBundling/
H A Dlabeloffset.s32 # The difference between the labels should be 0x20 (0x40-0x20) not 0x1b
40 # and for 2 adjacent labels that both point to the correct instruction
/llvm-project-15.0.7/mlir/utils/vim/indent/
H A Dmlir.vim47 " Indent labels the same as the current opening block
68 " Add a 'shiftwidth' after lines that start a function, block/labels, or a
/llvm-project-15.0.7/llvm/test/tools/llvm-objdump/X86/
H A Delf-disassemble-no-symtab.test2 ## references and labels.
/llvm-project-15.0.7/llvm/test/CodeGen/ARM/
H A Dconstantpool-promote-duplicate.ll6 ; const1 and const2 both need labels for debug info, but will be coalesced into

1234567