Home
last modified time | relevance | path

Searched refs:can (Results 1 – 25 of 4017) sorted by relevance

12345678910>>...161

/llvm-project-15.0.7/llvm/test/CodeGen/AMDGPU/
H A Dattr-unparseable.ll3 ; CHECK: can't parse integer attribute amdgpu-num-sgpr
10 ; CHECK: can't parse integer attribute amdgpu-num-sgpr
17 ; CHECK: can't parse integer attribute amdgpu-num-sgpr
24 ; CHECK: can't parse first integer attribute amdgpu-flat-work-group-size
31 ; CHECK: can't parse first integer attribute amdgpu-flat-work-group-size
38 ; CHECK: can't parse second integer attribute amdgpu-flat-work-group-size
45 ; CHECK: can't parse second integer attribute amdgpu-flat-work-group-size
52 ; CHECK: can't parse second integer attribute amdgpu-flat-work-group-size
/llvm-project-15.0.7/clang/test/SemaObjC/
H A Dattr-swift-error.m24 // expected-error@-1 {{'__swift_error__' attribute with 'null_result' convention can only be applie…
38 // expected-error@-4 {{can only be applied}}
43 // expected-error@-4 {{can only be applied}}
47 // expected-error@-1 {{'__swift_error__' attribute can only be applied to a method with an error pa…
49 // expected-error@-1 {{'__swift_error__' attribute can only be applied to a method with an error pa…
51 // expected-error@-1 {{'__swift_error__' attribute can only be applied to a method with an error pa…
53 // expected-error@-1 {{'__swift_error__' attribute can only be applied to a method with an error pa…
84 // expected-error@-1 {{'__swift_error__' attribute can only be applied to a function with an error …
86 // expected-error@-1 {{'__swift_error__' attribute can only be applied to a function with an error …
88 // expected-error@-1 {{'__swift_error__' attribute can only be applied to a function with an error …
[all …]
H A Dflexible-array.m20 …exible' with variable sized type 'char[]' is not visible to subclasses and can conflict with their…
28 …exible' with variable sized type 'char[]' is not visible to subclasses and can conflict with their…
35 …exible' with variable sized type 'char[]' is not visible to subclasses and can conflict with their…
62 …exible' with variable sized type 'char[]' is not visible to subclasses and can conflict with their…
70 …exible' with variable sized type 'char[]' is not visible to subclasses and can conflict with their…
95 …exible' with variable sized type 'char[]' is not visible to subclasses and can conflict with their…
103 …exible' with variable sized type 'char[]' is not visible to subclasses and can conflict with their…
197 … with variable sized type 'struct Packet' is not visible to subclasses and can conflict with their…
247 …int last; // expected-warning {{field 'last' can overwrite instance variable 'flexible' with varia…
254 …int last; // expected-warning {{field 'last' can overwrite instance variable 'flexible' with varia…
[all …]
/llvm-project-15.0.7/llvm/docs/GlobalISel/
H A DPipeline.rst33 the gMIR to suit what the backend can support. There is a very small set of
35 can shape the MIR as they wish.
80 alternatives but Combiners can also focus on code size or other metrics.
87 Of course, combiners can be inserted in other places too. Also passes can be
100 function with the ``legalized`` property can have the ``MachineVerifier``
111 The main issue is that GlobalISel is a separate library, so we can't
126 can be serialized using ``-stop-before`` or ``-stop-after`` and loaded using
143 BlockExtractor to extract basic blocks into new functions. This can be used
145 regressions. It can also be coupled with function attributes to disable
161 single function at a time. This technique can be repeated for different
[all …]
/llvm-project-15.0.7/llvm/docs/
H A DXRay.rst15 instrumentation points and a runtime library that can dynamically enable and
18 More high level information about XRay can be found in the `XRay whitepaper`_.
45 You can use XRay in a couple of ways:
66 get XRay instrumentation points. You can tweak that number through the
76 You can do it using the GCC-style attributes or C++11-style attributes.
88 When linking a binary, you can either manually link in the `XRay Runtime
192 ``__xray_log_register_mode(...)`` can be chosen with this function.
201 an implementation's data can be cleared out through the
214 execution, and periodically append to a single log. This mode can be
234 implementation can be provided in the ``XRAY_FDR_OPTIONS`` environment
[all …]
H A DStackSafetyAnalysis.rst9 The Stack Safety Analysis determines if stack allocated variables can be
16 'safe' variables can be defined as variables that can not be used out-of-scope
17 (e.g. use-after-return) or accessed out of bounds. In the future it can be
46 We expect that users can tolerate false classification of variables as
48 can't accept false 'safe' classification which may cause sanitizers to miss actual
51 AddressSanitizer may help with this validation. We can instrument all variables
54 a 'safe' variable we can produce an additional report to let the user know that
H A DMarkdownQuickstartTemplate.md11 You can find this document in `docs/MarkdownQuickstartTemplate.md`. You
58 Your text can be *emphasized*, **bold**, or `monospace`.
68 sophisticated syntax which [can be more readable] for longer links since
69 it disrupts the flow less. You can put the `[link name]: <URL>` block
72 [can be more readable]: http://en.wikipedia.org/wiki/LLVM
74 Lists can be made like this:
82 You can also use unordered lists.
92 You can make blocks of code like this:
100 As an extension to markdown, you can also specify a highlighter to use.
153 you can mail the list or check the [Common Mark spec]. Sphinx specific
[all …]
/llvm-project-15.0.7/llvm/test/tools/yaml2obj/ELF/
H A Demachine.yaml1 ## Test how the Machine YAML field can be used to set the e_machine ELF header field.
3 ## Test we can use an arbitrary value.
17 ## Test we can't use a number that doesn't fit into 2 bytes.
23 ## Test we can use a known named constant.
30 ## Test we can't use an unknown string constant.
H A Dhash-section.yaml3 ## Check we can describe a SHT_HASH section using the "Content" tag.
40 ## Check we can set an arbitrary entry size for the SHT_HASH section.
46 ## Check we can describe a SHT_HASH section using "Bucket" and "Chain" tags.
72 ## Check we can't use "Content" and "Bucket" tags together.
89 ## Check we can't use "Content" and "Chain" tags together.
106 ## Check we can't use "Bucket" without "Chain".
122 ## Check we can't use "Chain" without "Bucket".
154 ## Check we can set any sh_link value with use of the "Link" tag.
185 ## Check we can use only "Size" to create a SHT_HASH section.
249 ## Check we can't use "Size" and "Bucket" tags together.
[all …]
/llvm-project-15.0.7/llvm/docs/Frontend/
H A DPerformanceTips.rst20 surprisingly small changes in the source IR can have a large effect on the
28 Studying Clang's CodeGen directory can also be a good source of ideas. Note
54 but can also represent dynamic frame expansion. When representing function
83 replace a sext with a zext when it can be proven safe, but if you have
88 <range-metadata>` and LLVM can do the sext to zext conversion for you.
118 MIPS, it can make a big difference.
160 or can be easily discharged by inspecting the loop index variables.
165 with the duplicated ones, this can provide a noticeable throughput
211 can be very impactful.
215 optimizations that can be performed. This can be highly impactful for
[all …]
/llvm-project-15.0.7/llvm/test/MC/Hexagon/PacketRules/
H A Drestrict_no_slot1_store.s9 # CHECK: note: Instruction can utilize slots: 0, 1, 2, 3
10 # CHECK: note: Instruction can utilize slots: 0, 1, 2, 3
11 # CHECK: note: Instruction can utilize slots: <None>
12 # CHECK: note: Instruction can utilize slots: 0
/llvm-project-15.0.7/lldb/docs/use/
H A Dintel_pt.rst9 LLDB can collect traces and dump them using its symbolication stack.
10 You can read more here
63 When you are debugging a process, you can turn on intel-pt tracing,
65 After turning it on, you can continue debugging, and at any breakpoint,
66 you can inspect the instruction list.
92 # you can keep pressing ENTER to see more and more instructions
103 but you can change it by running.
115 If you want to dump more instructions at a time, you can run
125 but you can do
139 Then you can just do
[all …]
H A Dondemand.rst4 On demand symbols can be enabled in LLDB for projects that generate debug info
6 enable debug information for all binaries and can end up producing many
7 gigabytes of debug information. This amount of debug information can greatly
8 increase debug session load times and can slow developer productivity when the
9 debug information isn't indexed. It can also cause expression evaluation to
38 Users can also put this command into their ~/.lldbinit file so it is always
51 target, some simple things can cause module to get its debug information
77 Setting breakpoints by function name can work, but we try to avoid using
84 mean that setting breakpoints on inline function names can fail for modules
135 can be looked up by name. For this feature to work reliably with on demand
[all …]
H A Dtutorial.rst29 Options can be placed anywhere on the command line, but if the arguments begin
62 To set the same file and line breakpoint in LLDB you can enter either of:
86 breakpoint on all C++ methods named foo you can enter either of:
101 You can limit any breakpoints to a specific executable image by using the
143 you can do:
157 since lldb reads the file ~/.lldbinit at startup, you can store all your
180 so I can run the native lldb breakpoint command with just b
214 or you can specify it after the fact with the "file" command:
233 You can find out about the breakpoints you've set with:
365 You can make breakpoint names in your .lldbinit file, so you can use them to
[all …]
H A Dsymbols.rst12 It can locate the symbols using a variety of methods:
20 DebugSymbols.framework also has global defaults that can be modified to allow
23 defaults is **com.apple.DebugSymbols**, and the defaults can be read, written
32 The following is a list of the defaults key value setting pairs that can
37 This default can be specified as a single string, or an array of
52 This default can be specified as a single string, or an array of
88 dictionaries can contain one or more of the following keys:
128 | | executable can be provided. |
130 | **DBGError** | If a binary can not be located |
132 | | readable error can be returned. |
[all …]
/llvm-project-15.0.7/mlir/docs/
H A DCanonicalization.md13 multi-level IR, we can provide a single canonicalization infrastructure and
70 In [ODS](OpDefinitions.md), an operation can set the `hasCanonicalizer` bit or
87 Canonicalization patterns can then be provided in the source file:
110 mechanism, and can be invoked directly anywhere with an `OpBuilder` via
117 "local" transformation, and can be invoked without the need for a pattern
136 /// 1. They can leave the operation alone and without changing the IR, and
140 /// 3. They can return an existing value or attribute that can be used instead
155 /// 1. They can leave the operation alone and without changing the IR, and
159 /// 3. They can return a list of existing values or attribute that can be used
188 When the `fold` hook on an operation is not successful, the dialect can
[all …]
/llvm-project-15.0.7/llvm/test/CodeGen/Mips/
H A Dtls-models.ll22 ; Non-PIC code can use initial-exec, PIC code has to use general dynamic.
33 ; Non-PIC code can use local exec, PIC code can use local dynamic.
47 ; Non-PIC code can use initial exec, PIC should use local dynamic.
58 ; Non-PIC code can use local exec, PIC code can use local dynamic.
83 ; Non-PIC code can use local exec, PIC code use initial exec as specified.
/llvm-project-15.0.7/lldb/docs/
H A Dlldb-for-gdb-users.txt58 This can allow us to be more expressive, so you can say:
79 string match on command names, so the previous command can also be
102 you can do:
142 or you can specify it after the fact with the "file" command:
157 You can find out about the breakpoints you've set with:
213 Then you can either launch the process with the command:
221 Or you can attach to a process by name with:
364 You can also choose particular variables to view:
390 You can select another frame to view with:
418 You can also call functions:
[all …]
/llvm-project-15.0.7/bolt/docs/
H A DHeatmaps.md10 Heatmaps can be generated for BOLTed and non-BOLTed binaries. You can
23 Running with LBR (`-j any,u` or `-b`) is recommended. Heatmaps can be generated
34 By default the heatmap will be dumped to *stdout*. You can change it
37 code. You can change this granularity with a `-block-size` option.
47 it that way), then you can use an HTML conversion tool. E.g.:
/llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/cert/
H A Ddcl58-cpp.rst6 Modification of the ``std`` or ``posix`` namespace can result in undefined
26 …int x; // warning: modification of 'std' namespace can result in undefined behavior [cert-dcl58-cp…
29 …namespace posix::a { // warning: modification of 'posix' namespace can result in undefined behavior
33 …struct ::std::hash<long> { // warning: modification of 'std' namespace can result in undefined beh…
50 …void swap<bool>(bool &a, bool &b); // warning: modification of 'std' namespace can result in undef…
53 …(MyData &&, MyData &&) const { // warning: modification of 'std' namespace can result in undefined…
/llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/performance/
H A Dinefficient-vector-operation.rst9 It can also find calls that add element to protobuf repeated field in a loop
10 without calling Reserve() before the loop. Calling Reserve() first can avoid
24 // memory reallocations in v. This can be avoid by inserting a 'reserve(n)'
32 // reallocations. This can be avoid by inserting a
37 of ``range_expression`` can be ``std::vector``, ``std::array``,
49 // memory reallocations in v. This can be avoid by inserting a
/llvm-project-15.0.7/llvm/test/CodeGen/Thumb/
H A Daddr-modes.ll6 ; "ARMTargetLowering::isLegalAddressingMode can accept incorrect
10 ; It supports: r1 + r2, where r1 and r2 can be the same register.
26 ; Expected: GEP can be folded into LOAD.
35 ; Test case 03: 2*%x can be represented as %x + %x.
36 ; Expected: GEP can be folded into LOAD.
/llvm-project-15.0.7/clang/cmake/caches/
H A DREADME.txt7 You can use the caches files with the following CMake invocation:
25 The Apple-stage2 cache can be used directly to match the build settings Apple
31 The PGO CMake cache can be used to generate a multi-stage instrumented compiler.
32 You can configure your build directory with the following invocation of CMake:
66 This cache file can be used to generate a 3-stage clang build. You can configure
71 You can then run "ninja stage3-clang" to build stage1, stage2 and stage3 clangs.
/llvm-project-15.0.7/llvm/test/tools/llvm-nm/XCOFF/
H A Ddemangle.test5 ## 3. Name starting with . that can't be demangled
6 ## 4. Name starting with . that can be demangled
7 ## 5. Name not starting with . that can't be demangled
8 ## 6. Name not starting with . that can be demangled
/llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/readability/
H A Dredundant-declaration.rst19 Such redundant declarations can be removed without changing program behavior.
20 They can for instance be unintentional left overs from previous refactorings
24 Normally the code can be automatically fixed, :program:`clang-tidy` can remove

12345678910>>...161