| /llvm-project-15.0.7/llvm/test/tools/obj2yaml/ELF/ |
| H A D | relocation-addend.yaml | 1 ## Test how obj2yaml emits relocation addend descriptions. 6 ## Check how obj2yaml dumps an addend with an arbitrary positive value. 16 ## Check how obj2yaml dumps an addend with an arbitrary negative value. 21 ## Check how obj2yaml dumps an addend with the value INT64_MAX. 25 ## Check how obj2yaml dumps an addend with the value INT64_MIN. 58 ## Check how obj2yaml dumps an addend with an arbitrary positive value. 68 ## Check how obj2yaml dumps an addend with an arbitrary negative value. 73 ## Check how obj2yaml dumps an addend with the value INT32_MAX. 77 ## Check how obj2yaml dumps an addend with the value INT32_MIN.
|
| /llvm-project-15.0.7/llvm/docs/ |
| H A D | UserGuides.rst | 111 how to keep LLVM source code portable. 120 Information on how to write LLVM transformations and analyses. 123 Information on how to write LLVM transformations under the new pass 137 Information on how to write a new alias analysis implementation or how to 141 Information about the MemorySSA utility in LLVM, as well as how to use it. 167 This document specifies how to correctly update debug info in various kinds 171 This document explains how LLVM uses value tracking, or instruction 179 Information on how to write LLVM backends for machine targets. 215 Look here to see how to add instructions and intrinsics to LLVM.
|
| H A D | MarkdownQuickstartTemplate.md | 41 If possible, make your document a "how to". Give it a name `HowTo*.md` 42 like the other "how to" documents. This format is usually the easiest 45 You generally should not be writing documentation other than a "how to" 46 unless there is already a "how to" about your topic. The reason for this 47 is that without a "how to" document to read first, it is difficult for a
|
| H A D | GettingInvolved.rst | 26 An overview on how to contribute to LLVM. 42 Describes how to use the Phabricator code review tool hosted on 50 Describes how bugs are reported, triaged and closed. 57 Describes how to use the llvm-project repository on GitHub. 60 Describes how to use ``git bisect`` on LLVM's repository. 254 - General questions on how to contribute to LLVM; organizing meetups; 262 - General questions on how to contribute to LLVM; women in compilers; 283 …- General questions on how to contribute to LLVM/MLIR, Polly, Loop Optimization, FPL, Research in … 288 …- Clang internals for C/C++ language extensions and dialects, OpenCL, GPU, SPIR-V, how to contribu… 293 - SYCL compiler, offload tools, OpenCL and SPIR-V, how to contribute. [all …]
|
| H A D | GettingStartedTutorials.rst | 18 Discusses how to get up and running quickly with the LLVM infrastructure. 31 A collection of tips for frontend authors on how to generate IR
|
| H A D | Reference.rst | 140 Describes how to compile and run the test-suite benchmarks. 151 High-level documentation of how to use XRay in LLVM. 154 An example of how to debug an application with XRay. 203 This document describes segmented stacks and how they are used in LLVM.
|
| H A D | HowToBuildWithPGO.rst | 9 for how it actually runs. Users report that applying this to Clang and LLVM can 12 This guide walks you through how to build Clang with PGO, though it also applies 31 more information on how to run it, and the different options available to you. 46 PGO does best when the profiles gathered represent how the user plans to use the 74 how to build Clang/LLVM with PGO. 85 - Running the instrumented Clang/LLVM/lld/etc. on tasks that represent how
|
| /llvm-project-15.0.7/mlir/docs/Tutorials/Toy/ |
| H A D | _index.md | 5 particular, how [dialects](../../LangRef.md/#dialects) can help easily support 23 introducing base MLIR concepts. Here we show how to start attaching 28 with Interfaces. Here we will show how to plug dialect specific information 37 We'll demonstrate how to add a custom type to MLIR, and how it fits in the
|
| /llvm-project-15.0.7/lldb/docs/use/ |
| H A D | links.rst | 4 This page contains links to external resources on how to use LLDB. Being 23 Discover the various ways to display values in your app, how to format 24 custom data types, and how to extend LLDB using your own Python 3 31 Xcode debugging workflows. Learn how to take advantage of LLDB and 50 from the team that created LLDB, and see how it will help you track down
|
| /llvm-project-15.0.7/llvm/docs/tutorial/MyFirstLanguageFrontend/ |
| H A D | index.rst | 24 how fun and easy it can be. This tutorial will get you up and running 29 iteratively over the course of several chapters, showing how it is built 57 the AST ready, we show how easy it is to generate LLVM IR, and show 62 support. Later chapters show how to generate .o files. 64 the basic language up and running, we show how to extend 75 variables along with an assignment operator. This shows how easy it is 79 chapter explains how to take LLVM IR and compile it down to object
|
| /llvm-project-15.0.7/clang-tools-extra/test/modularize/ |
| H A D | ProblemsInconsistent.modularize | 15 …instance 'FUNC_STYLE(1, 0);' has different values in this header, depending on how it was included. 33 # CHECK-NEXT: error: Macro instance 'SYMBOL' has different values in this header, depending on how … 51 … instance 'defined(SYMBOL1)' has different values in this header, depending on how it was included. 66 …xpression instance 'SYMBOL1' has different values in this header, depending on how it was included. 76 …xpression instance 'SYMBOL2' has different values in this header, depending on how it was included. 86 … instance 'defined(SYMBOL1)' has different values in this header, depending on how it was included. 93 …]}}Inputs{{[/\\]}}InconsistentSubHeader.h' has different contents depending on how it was included.
|
| /llvm-project-15.0.7/libc/src/signal/linux/ |
| H A D | sigprocmask.cpp | 18 (int how, const sigset_t *__restrict set, 20 int ret = __llvm_libc::syscall(SYS_rt_sigprocmask, how, set, oldset,
|
| /llvm-project-15.0.7/clang/docs/ |
| H A D | LibASTMatchers.rst | 5 This document explains how to use Clang's LibASTMatchers to match interesting 12 about how the AST is structured. 45 when trying to figure out how to create a matcher for a specific pattern. This 46 section will teach you how to use a rigorous step-by-step pattern to build the 48 for some part of the AST. See the section about :ref:`how to write your own 53 The precondition to using the matchers is to understand how the AST for what you 56 how to dump a translation unit's AST into a human readable format.
|
| /llvm-project-15.0.7/llvm/include/llvm/Target/ |
| H A D | TargetPfmCounters.td | 35 // Processors can define how to measure cycles by defining a CycleCounter. 37 // Processors can define how to measure uops by defining a UopsCounter. 39 // Processors can define how to measure issued uops by defining IssueCounters.
|
| /llvm-project-15.0.7/clang/test/SemaCXX/ |
| H A D | switch.cpp | 46 template <En how> void foo() { in foo() 49 switch (how) { //expected-warning {{no case matching constant switch condition '2'}} in foo()
|
| /llvm-project-15.0.7/llvm/test/CodeGen/AVR/calling-conv/c/ |
| H A D | tiny.ll | 44 ; how arguments are passed. 71 ; how arguments are passed. 100 ; how arguments are passed. 133 ; how arguments are passed. 155 ; how arguments are passed. 177 ; how arguments are passed. 199 ; how arguments are passed.
|
| /llvm-project-15.0.7/llvm/test/CodeGen/X86/ |
| H A D | promote-assert-zext.ll | 7 ; ISel doesn't yet know how to eliminate this extra zero-extend. But until 8 ; it knows how to do so safely, it shouldn;t eliminate it.
|
| /llvm-project-15.0.7/clang/test/Rewriter/ |
| H A D | finally.m | 32 return; // The rewriter knows how to generate code for implicit finally 38 return; // The rewriter knows how to generate code for implicit finally
|
| /llvm-project-15.0.7/polly/test/ScopDetect/ |
| H A D | non-simple-memory-accesses.ll | 4 ; how to handle them correctly and the Alias Set Tracker models some of them 5 ; only as Unknown Instructions, which we do not know how to handle either.;
|
| /llvm-project-15.0.7/llvm/docs/GlobalISel/ |
| H A D | Porting.rst | 13 * :ref:`LegalizerInfo <api-legalizerinfo>` --- describe what is legal, and how 28 which gave an overview of how to bring up a new backend in GlobalISel.
|
| /llvm-project-15.0.7/llvm/docs/tutorial/ |
| H A D | index.rst | 14 This is the "Kaleidoscope" Language tutorial, showing how to implement a simple 43 A simple guide for how to implement an LLVM integrated assembler for an
|
| /llvm-project-15.0.7/mlir/examples/standalone/include/Standalone/ |
| H A D | StandaloneOps.td | 18 let summary = "Illustrates how to define an operation."; 20 The `standalone.foo` operation illustrates how to define a new
|
| /llvm-project-15.0.7/llvm/docs/HistoricalNotes/ |
| H A D | 2001-02-06-TypeNotationDebateResp4.txt | 15 of a stretch from learning the opcodes and how SSA form works, and how 33 in LLVM directly would understand how to do it without looking it up in a 48 > introduce, no matter how logical it is. 50 Erm... excuse me but how is this the "old array syntax"? If you are
|
| /llvm-project-15.0.7/llvm/cmake/modules/ |
| H A D | HandleLLVMStdlib.cmake | 31 message(WARNING "Not sure how to specify libc++ for this compiler") 50 message(WARNING "Not sure how to specify static linking of C++ standard "
|
| /llvm-project-15.0.7/llvm/test/tools/obj2yaml/Archives/ |
| H A D | regular.yaml | 1 ## Check how obj2yaml dumps regular archives. 3 ## Check how we dump an empty archive. 18 ## Check how we dump archives with multiple members. 21 ## Check how we dump empty field values.
|