Clang 11 upgrade #984

Is64bit is ambiguous. In this patch, we replace it with Is64BitAddrSize to make it clearer.

…sextload)) -> copy On AArch64 we generate redundant G_SEXTs or G_SEXT_INREGs because of this. Differential Revision: https://reviews.llvm.org/D81993

This patch implements builtins for the Test LSB by Byte instruction introduced in Power10. Differential Revision: https://reviews.llvm.org/D82431

Preserve SCC dead flags in SIOptimizeExecMaskingPreRA. This helps with removing redundant s_andn2 instructions later. Reviewed By: rampitec Differential Revision: https://reviews.llvm.org/D83637

Attach DbgLoc on insertvalue/extractvalue instructions created by DeadArgumentElimination. This fixes the PR46350. Differential Revision: https://reviews.llvm.org/D81939

Pre-commit clean up for D83641.

…mFPLoadStorePair In DAGCombiner::TransformFPLoadStorePair we were dropping the scalable property of TypeSize when trying to create an integer type of equivalent size. In fact, this optimisation makes no sense for scalable types since we don't know the size at compile time. I have changed the code to bail out when encountering scalable type sizes. I've added a test to llvm/test/CodeGen/AArch64/sve-fp.ll that exercises this code path. The test already emits an error if it encounters warnings due to implicit TypeSize->uint64_t conversions. Differential Revision: https://reviews.llvm.org/D83572

In getCastInstrCost() when comparing different sizes for src and dst types we should be using the TypeSize comparison operators instead of relying upon TypeSize being converted a uin64_t. Previously this meant we were dropping the scalable property and treating fixed and scalable vector types the same. Differential Revision: https://reviews.llvm.org/D83461

Summary: This patch introduces basic textDocument/foldingRange support. It relies on textDocument/documentSymbols to collect all symbols and uses takes ranges to create folds. The next steps for textDocument/foldingRange support would be: * Implementing FoldingRangeClientCapabilities and respecting respect client preferences * Specifying folding range kind * Migrating from DocumentSymbol implementation to custom RecursiveASTVisitor flow that will allow more flexibility * Supporting more folding range types: comments, PP conditional regions, includes and other code regions (e.g. public/private/protected sections of classes, control flow statement bodies) Tested: (Neo)Vim (coc-clangd) and VSCode. Related issue: clangd/clangd#310 Reviewers: sammccall Reviewed By: sammccall Subscribers: nridge, ilya-biryukov, MaskRay, jkorous, arphaman, kadircet, usaxena95, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D82436

I have added a new file: llvm/test/CodeGen/AArch64/README that describes what to do in the event one of the SVE codegen tests fails the warnings check. In addition, I've added comments to all the relevant SVE tests pointing users at the README file. Differential Revision: https://reviews.llvm.org/D83467

@nikic

…visitUnconditionalBranchInst()` Summary: As @nikic is pointing out in https://bugs.llvm.org/show_bug.cgi?id=46680#c5, InstCombine should not have forward instruction scans, so let's move this transform into the proper place. This is pretty much NFCI. Reviewers: nikic, spatel Reviewed By: nikic Subscribers: hiraditya, llvm-commits, nikic Tags: #llvm Differential Revision: https://reviews.llvm.org/D83670

The approach is simple: if a pass reports that it's not modifying a Function/Module, compute a loose hash of that Function/Module and compare it with the original one. If we report no change but there's a hash change, then we have an error. This approach misses a lot of change but it's not super intrusive and can detect most of the simple mistakes. Differential Revision: https://reviews.llvm.org/D80916

The hardware spec require src0 of s_cmpk should be a register. So, we should not optimize s_cmp to s_cmpk if src0 is not register. Patch by Ruiling Song!

…ively" This reverts commit 8372d50. It broke the TestCases/Darwin/asan-symbolize-partial-report-with-module-map.cpp test on green dragon.

The code already supports addressing a fixed-size stack object from the frame-pointer, by first subtracting sizeof(SVE area) from FP. Reviewers: efriedma, cameron.mcinally, david-arm, rengolin Reviewed By: david-arm Differential Revision: https://reviews.llvm.org/D83125

…se env in tests"" This reverts commit 979c502. The underlying issue has been fixed in https://reviews.llvm.org/D83719.

Summary: This commit includes a couple of changes: * Benchmark selected projects by analyzing them multiple times * Compare two benchmarking results and visualizing them on one chart * Organize project build logging, so we can use the same code in benchmarks Differential Revision: https://reviews.llvm.org/D83539

Differential Revision: https://reviews.llvm.org/D83701

If a vector body has live-out values, it is probably a reduction, which needs a final reduction step after the loop. MVE has a VADDV instruction to reduce integer vectors, but doesn't have an equivalent one for float vectors. A live-out value that is not recognised as reduction later in the optimisation pipeline will result in the tail-predicated loop to be reverted to a non-predicated loop and this is very expensive, i.e. it has a significant performance impact, which is what we hope to avoid with fine tuning the ARM TTI hook preferPredicateOverEpilogue implementation. Differential Revision: https://reviews.llvm.org/D82953

Fix two obvious errors in the code and also update the test check. Also add one test to catch the failure. Patch by Ruiling Song! Differential Revision: https://reviews.llvm.org/D83280

Add a unit test for the compact DWARF expression printer which will be used by the llvm-objdump --debug-vars option. Differential revision: https://reviews.llvm.org/D75250

Add the DW_OP_breg0..DW_OP_breg31 and DW_OP_bregx opcodes to the DWARF expression printer. Differential revision: https://reviews.llvm.org/D74841

Add the DW_OP_entry_value and DW_OP_stack_value opcodes to the DWARF expression printer. Differential revision: https://reviews.llvm.org/D74843

…Solaris The new `LLVM-Unit :: Support/./SupportTests/ProgramEnvTest.TestExecuteAndWaitStatistics` test currently FAILs on Solaris: [ RUN ] ProgramEnvTest.TestExecuteAndWaitStatistics /vol/llvm/src/llvm-project/local/llvm/unittests/Support/ProgramTest.cpp:360: Failure Expected: (ProcStat->PeakMemory) > (0U), actual: 0 vs 0 [ FAILED ] ProgramEnvTest.TestExecuteAndWaitStatistics (22 ms) According to `llvm/lib/Support/Unix/Program.inc (llvm::sys::Wait)`, `PeakMemory` corresponds to `struct rusage.ru_maxrss`. However, Solaris `getrusage(3C)` documents NOTES The ru_maxrss, ru_ixrss, ru_idrss, and ru_isrss members of the rusage structure are set to 0 in this implementation. Since changing the test to check for `PeakMemory >= 0` instead is pointless and would generate a warning on targets where `ru_maxrss` is unsigned, this patch removes the check. Tested on `amd64-pc-solaris2.11`. Differential Revision: https://reviews.llvm.org/D83661

…f they are defined in non-fetched archive members After D69985, symbols for "-init" and "-fini" were unconditionally marked as used even if they were just lazy symbols seen when scanning archives. That resulted in exposing them in the symbol table of an output file, as Undefined, which added unwanted dependencies. The patch fixes the issue by checking the kind of the symbols before the marking. Differential Revision: https://reviews.llvm.org/D83549

This adds unit tests to check the expected behavior of the method in case the unit length field is truncated. Differential Revision: https://reviews.llvm.org/D83673

…ts section. DWARFListTableHeader::length() handles the zero value of HeaderData.Length in a special way, which makes the result different from the calculated value of FullLength, which leads to triggering an assertion. The patch moves the assertion a bit later when `FullLength` is already checked for minimal allowed value. Differential Revision: https://reviews.llvm.org/D82886

AArch64 does not support enabling rcpc via .arch_extension in assembly. GCC, on the other hand, does. This patch adds 'rcpc' as a valid value to .arch_extension handling. Differential Revision: https://reviews.llvm.org/D83685

Differential Revision: https://reviews.llvm.org/D83117

Differential Revision: https://reviews.llvm.org/D83118

This reverts commit 97106f9. This is based on feedback from https://reviews.llvm.org/D82988#2147105

…m fields. This adds `EPhOff`, `EPhEntSize` and `EPhNum` keys. Will be useful for creating broken objects for testing llvm-readelf. Differential revision: https://reviews.llvm.org/D83482

… Solaris/x86 A dozen 32-bit `AddressSanitizer` testcases FAIL on the latest beta of Solaris 11.4/x86, e.g. `AddressSanitizer-i386-sunos :: TestCases/null_deref.cpp` produces AddressSanitizer:DEADLYSIGNAL ================================================================= ==29274==ERROR: AddressSanitizer: stack-overflow on address 0x00000028 (pc 0x08135efd bp 0xfeffdfd8 sp 0x00000000 T0) #0 0x8135efd in NullDeref(int*) /vol/llvm/src/llvm-project/dist/compiler-rt/test/asan/TestCases/null_deref.cpp:15:10 #1 0x8135ea6 in main /vol/llvm/src/llvm-project/dist/compiler-rt/test/asan/TestCases/null_deref.cpp:21:3 #2 0x8084b85 in _start (null_deref.cpp.tmp+0x8084b85) SUMMARY: AddressSanitizer: stack-overflow /vol/llvm/src/llvm-project/dist/compiler-rt/test/asan/TestCases/null_deref.cpp:15:10 in NullDeref(int*) ==29274==ABORTING instead of the expected AddressSanitizer:DEADLYSIGNAL ================================================================= ==29276==ERROR: AddressSanitizer: SEGV on unknown address 0x00000028 (pc 0x08135f1f bp 0xfeffdf48 sp 0xfeffdf40 T0) ==29276==The signal is caused by a WRITE memory access. ==29276==Hint: address points to the zero page. #0 0x8135f1f in NullDeref(int*) /vol/llvm/src/llvm-project/local/compiler-rt/test/asan/TestCases/null_deref.cpp:15:10 #1 0x8135efa in main /vol/llvm/src/llvm-project/local/compiler-rt/test/asan/TestCases/null_deref.cpp:21:3 #2 0x8084be5 in _start (null_deref.cpp.tmp+0x8084be5) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /vol/llvm/src/llvm-project/local/compiler-rt/test/asan/TestCases/null_deref.cpp:15:10 in NullDeref(int*) ==29276==ABORTING I managed to trace this to a change in `<sys/regset.h>`: previously the header would primarily define the short register indices (like `UESP`). While they are required by the i386 psABI, they are only required in `<ucontext.h>` and could previously leak into unsuspecting user code, polluting the namespace and requiring elaborate workarounds like that in `llvm/include/llvm/Support/Solaris/sys/regset.h`. The change fixed that by restricting the definition of the short forms appropriately, at the same time defining all `REG_` prefixed forms for compatiblity with other systems. This exposed a bug in `compiler-rt/lib/sanitizer_common/sanitizer_linux.cpp`, however: Previously, the index for the user stack pointer would be hardcoded if `REG_ESP` wasn't defined. Now with that definition present, it turned out that `REG_ESP` was the wrong index to use: the previous value 17 (and `REG_SP`) corresponds to `REG_UESP` instead. With that change, the failures are all gone. Tested on `amd-pc-solaris2.11`. Differential Revision: https://reviews.llvm.org/D83664

This patch adds support for emitting value forms of DW_FORM_strx, DW_FORM_addrx, DW_FORM_loclistx and DW_FORM_rnglistx. Reviewed By: jhenderson Differential Revision: https://reviews.llvm.org/D83749

The glob expression for a test called "test" could match a log file for a the test "test_foo". Instead of globbing, maintain an explicit list of log files relevant to the current test.

…rom scalable. ComputeNumSignBits and computeKnownBits both trigger "Scalable flag may be dropped" warnings when a fixed length vector is extracted from a scalable vector. This patch assumes nothing about the demanded elements thus matching the behaviour when extracting a scalable vector from a scalable vector. Differential Revision: https://reviews.llvm.org/D83642

… calls. program_headers() returns the list of program headers. This change allows to continue attempt of dumping when something is wrong with program headers. Differential revision: https://reviews.llvm.org/D83554

…phoff field is invalid and refine testing. llvm-objdump currently calls report_fatal_error() when the e_phoff field is invalid. This is tested by elf-invalid-phdr.test which has the following issues: 1) It uses a precompiled object. 2) it could be a part of invalid.test. 3) It tests the Object lib, but we have no separate test for llvm-objdump. This patch addresses issues mentioned. Differential revision: https://reviews.llvm.org/D83559

More coverage for D83601.

…hanZeroImpl (PR46627) A miscompile with -0.0 is shown in: http://bugs.llvm.org/PR46627 This is because maxnum(-0.0, +0.0) does not specify a fixed result: http://llvm.org/docs/LangRef.html#llvm-maxnum-intrinsic So we need to tighten the constraints for when it is ok to say the result of maxnum is positive (including +0.0). Differential Revision: https://reviews.llvm.org/D83601

Imagine we have an YAML description for some object and we want to produce 2 outputs: with and without the section header. A natural way to do it would look like: ``` --- !ELF FileHeader: Class: ELFCLASS64 Data: ELFDATA2LSB Type: ET_REL Machine: EM_X86_64 Sections: ... SectionHeaderTable: NoHeaders: [[NOHEADERS]] ``` But currently, we do not distinguish between no `NoHeaders` key case and `NoHeaders == false`. Because of this we can't simply specify `NOHEADERS = false`, as tool starts to complain. With this patch the behavior changed. When we have: ``` SectionHeaderTable: NoHeaders: false ``` it is the same as we have no `SectionHeaderTable` at all. (`NoHeaders` key still can't be used with `Sections/Excluded` keys) Differential revision: https://reviews.llvm.org/D83672

Summary: Just unifying all that copy-pasted code. Reviewers: JDevlieghere Reviewed By: JDevlieghere Differential Revision: https://reviews.llvm.org/D83662

This reverts commit f1efb8b. Reverted because it doesn't correctly update the pass return status, see http://lab.llvm.org:8011/builders/llvm-clang-x86_64-expensive-checks-debian/builds/9441/steps/test-check-all/logs/FAIL%3A%20LLVM%3A%3Awiden-i32-i8ptr.ll

Summary: This patch implements lowering of OpenMP barrier construct from pft to OpenMPDialect. Patch is carved out of following merged PR's from fir-dev branch of https://github.com/flang-compiler/f18-llvm-project/ PR's: flang-compiler/f18-llvm-project#248 flang-compiler/f18-llvm-project#251 Unfortunately primary tool `bbc` for functional validation is not yet upstreamed. So this patch includes a unittest for lowering `!OMP barrier` construct. Some part of the these PR's still remains downstream(functional test and dialect registration to legalizer) for obvious reasons. Will upstream them when the dependencies are upstreamed. Reviewed By: schweitz, kiranchandramohan Differential Revision: https://reviews.llvm.org/D83659

New test to show the changes after D81805 is committed. Differential Revision: https://reviews.llvm.org/D83750

Because of the layout of stores (that don't have a destination operand) this check is exactly the same as the one in RISCVInstrInfo::isLoadFromStackSlot. Differential Revision: https://reviews.llvm.org/D81805

The _ExtInt type allows custom width integers, but the atomic memory access's operand must have a power-of-two size. _ExtInts with non-power-of-two size should not be allowed for atomic intrinsic. Before this change: $ cat test.c typedef unsigned _ExtInt(42) dtype; void verify_binary_op_nand(dtype* pval1, dtype val2) { __sync_nand_and_fetch(pval1, val2); } $ clang test.c clang-11: /home/ubuntu/llvm_workspace/llvm/clang/lib/CodeGen/CGBuiltin.cpp:117: llvm::Value* EmitToInt(clang::CodeGen::CodeGenFunction&, llvm::Value*, clang::QualType, llvm::IntegerType*): Assertion `V->getType() == IntType' failed. PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace, preprocessed source, and associated run script. After this change: $ clang test.c test.c:3:30: error: Atomic memory operand must have a power-of-two size { __sync_nand_and_fetch(pval1, val2); } ^ List of the atomic intrinsics that have this problem: __sync_fetch_and_add __sync_fetch_and_sub __sync_fetch_and_or __sync_fetch_and_and __sync_fetch_and_xor __sync_fetch_and_nand __sync_nand_and_fetch __sync_and_and_fetch __sync_add_and_fetch __sync_sub_and_fetch __sync_or_and_fetch __sync_xor_and_fetch __sync_fetch_and_min __sync_fetch_and_max __sync_fetch_and_umin __sync_fetch_and_umax __sync_val_compare_and_swap __sync_bool_compare_and_swap Differential Revision: https://reviews.llvm.org/D83340

Summary: This is designed for tweaking compile commands by specifying flags to add/remove in a config file. Something like: CompileFlags: { Remove: -fcolor-diagnostics } Having users tweak raw argv (e.g. with a regex) is going to end in tears: bugs around clang-cl, xclang, aliases, joined-vs-separate args etc are inevitable. This isn't in tooling because of the performance choices: build a big table up-front to make subsequent actions fast. Maybe it should be though. Reviewers: adamcz, hokein Subscribers: ilya-biryukov, MaskRay, jkorous, arphaman, kadircet, usaxena95, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D81958

Summary: Names of local variables have no linkage (see C++20 [basic.link] p8). Names of variables in unnamed namespace have internal linkage (see C++20 [basic.link] p4). Reviewers: aaron.ballman, rsmith, ymandel Reviewed By: ymandel Subscribers: cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D83700

Summary: Currently forward decls are included with all the op classes. But there are cases (say when splitting up headers) where one wants the forward decls but not all the classes. Add an option to enable this. This does not change any current behavior (some further refactoring is probably due here). Differential Revision: https://reviews.llvm.org/D83727

Instead of having complex logic around how to include the libc++ headers and __config_site, handle that by defining cxx-headers as an INTERFACE library and linking against it. After this patch, linking against cxx-headers is sufficient to get the right __config_site include and include paths for libc++. Differential Revision: https://reviews.llvm.org/D82702

Summary: This can be run after a ninja-based build, and analyzes the ninja build files and dependency database to spot any missing dependencies in the build scripts. I wrote it in the course of investigating D82659, and it seems likely to be useful again. Reviewers: thakis, chandlerc, theraven Reviewed By: thakis Subscribers: riccibruno, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D83032

Summary: While here, add documentation to CompileFlags and CompileFlags.Add. Reviewers: hokein Subscribers: ilya-biryukov, MaskRay, jkorous, arphaman, kadircet, usaxena95, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D83705

…n' attribute This is another problem raised in: http://bugs.llvm.org/PR46627

…stat. Summary: This is motivated by: - code completion: nice to do no i/o on the request path - background index: deciding whether to enqueue each file would stat the config file thousands of times in quick succession. Currently it's applied uniformly to all requests though. This gives up on performing stat() outside the lock, all this achieves is letting multiple threads stat concurrently (and thus finish without contention for nonexistent files). The ability to finish without IO (just mutex lock + integer check) should outweigh this, and is less sensitive to platform IO characteristics. Reviewers: kadircet Subscribers: ilya-biryukov, MaskRay, jkorous, arphaman, usaxena95, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D83755

In synchronous mode, the process connect command and its aliases should wait for the stop event before claiming the command is complete. Currently, the stop event is always handled asynchronously by the debugger. The implementation takes the same approach as Process::ResumeSynchronous which hijacks the event and handles it on the current thread. Similarly, after this patch, the stop event is part of the command return object, which is the property used by the test case. Differential revision: https://reviews.llvm.org/D83728

Summary: This patch extends the ModuleSpec class to include a DataBufferSP which contains the module data. If this data is provided, LLDB won't try to hit the filesystem to create the Module, but use only the data stored in the ModuleSpec. Reviewers: labath, espindola Subscribers: emaste, MaskRay, lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D83512

…xx-headers The libc++ headers were included twice, which broke the #include_next logic.

This patch adds override to several overriding virtual functions that were missing the keyword within the clang/ directory. These were found by the new -Wsuggest-override.

Loop metadata nodes do not adhere to the documented property: (a) LoopIDs are not unique: Any pass that duplicates IR will do it including its metadata (e.g. LoopVersioning) such that multiple loops are linked with the same LoopID. There is even a test case (Transforms/LoopUnroll/unroll-pragmas-disabled.ll) for multiple loops with the same LoopID. (b) LoopIDs are not persistent: Adding or removing an item from a LoopID can only be done by creating a new MDNode and assigning it to the loop's branch(es). Passes such as LoopUnroll (llvm.loop.unroll.disable) and LoopVectorize (llvm.loop.isvectorized) use this to mark loops to not be transformed multiple times or to avoid that a LoopVersioned original loop is transformed. Update the documentation according to how llvm.loop is used in practice. Differential Revision: https://reviews.llvm.org/D55290

- Avoid generating "assert(resultTypes.size() >= 0u)" which is always true Differential Revision: https://reviews.llvm.org/D83735

Summary: llvm-cov.test generates .gcov files and compared with target sample files. Since the files do not contain any binary data (files are plain ASCII texts), remove -a from diff. And this fix will the error on AIX since the default diff tool on AIX does not support -a option. Reviewers: hubert.reinterpretcast, daltenty, stevewan Subscribers: llvm-commits Tags: #LLVM Differential Revision: https://reviews.llvm.org/D83711

- Arguments of the first block of a region are considered region arguments. - Add API on Region class to deal with these arguments directly instead of using the front() block. - Changed several instances of existing code that can use this API - Fixes https://bugs.llvm.org/show_bug.cgi?id=46535 Differential Revision: https://reviews.llvm.org/D83599

…ngAttrEmitter ClangAttrEmitter.cpp generates ParsedAttr derived classes with virtual overrides in them (which end up in AttrParsedAttrImpl.inc); this patch ensures these generated functions are marked override, and not (redundantly) virtual. I hesitate to say NFC since this does of course affect the behavior of the generator code, but the generated code behaves the same as it did before, so it's NFC in that sense. Differential Revision: https://reviews.llvm.org/D83616

This fixes warnings raised by Clang's new -Wsuggest-override, in preparation for enabling that warning in the LLVM build. This patch also removes the virtual keyword where redundant, but only in places where doing so improves consistency within a given file. It also removes a couple unnecessary virtual destructor declarations in derived classes where the destructor inherited from the base class is already virtual. Differential Revision: https://reviews.llvm.org/D83709

If we deduced the arity of a pack in two different ways, but didn't deduce an element of the pack in either of those deductions, we'd merge that element to produce a null template argument, which we'd incorrectly interpret as the merge having failed. Testcase based on one supplied by Hubert Tong.

Summary: We only support Build/Skip for now, but with 'Load' or similar as an option for future (load existing shards but don't build new ones). This requires creating the config for each TU on startup. In LLVM, this is 4000 occurrences for a total of 800ms on my machine. But together with caching from D83755 it is only 25ms. Reviewers: kadircet Subscribers: ilya-biryukov, MaskRay, jkorous, arphaman, usaxena95, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D83768

Skip TestProcessConnect.py on Windows and Android (the same platforms as TestPlatformProcessConnect.py) and mark it as a NO_DEBUG_INFO test so we don't run all the variants.

Summary: This is a follow up to https://reviews.llvm.org/D78306 Reviewers: DavidTruby, sscalpone, jdoerfert Reviewed By: DavidTruby Subscribers: tskeith, Meinersbur, ChinouneMehdi, richard.barton.arm, mehdi_amini, mgorny, llvm-commits Tags: #llvm, #flang Differential Revision: https://reviews.llvm.org/D81695

As per discussion in D69207, have lit ignore UnicodeDecodeErrors when running with python 2 in an ASCII shell. Differential Revision: https://reviews.llvm.org/D82754

- Make the open more Pythonic. - Remove the unused `cleanup` Make target. - Remove commented-out/obvious/low-value comments. - Cleanup the forked process PID list.

Use runBuildCommands, like all other builders, to raise a build-specific error when the command fails.

Summary: The following preprocessor macros are implied when `-march=armv8.6a+sve`: ``` __ARM_FEATURE_SVE 1 __ARM_FEATURE_SVE_BF16 1 __ARM_FEATURE_SVE_MATMUL_FP32 1 __ARM_FEATURE_SVE_MATMUL_INT8 1 ``` Reviewers: sdesmalen, efriedma, SjoerdMeijer, rengolin Subscribers: tschuett, kristof.beyls, danielkiss, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D83079

…ager. LazyReexportsManager instances use the trampoline pool, but they don't need to own it. Keeping TrampolinePool ownership separate allows re-use of the trampoline pool by other clients.

I mistyped the ubsan objc_cast handler names on the first try. Testing: ./bin/llvm-lit projects/compiler-rt/test/asan/X86_64HDarwinConfig/TestCases/Darwin/interface_symbols_darwin.cpp

Add missing const - addresses clang tidy warnings. Differential Revision: https://reviews.llvm.org/D83794

…id ODR violations <rdar://problem/65537147> Differential Revision: https://reviews.llvm.org/D83796

Currently custom code predicates can only really be used for contextless checks tied to a single instruction (e.g. check the def for hasOneUse). If you do want to inspect the input instructions in the source pattern, you cannot without re-verifying the opcode and type checks implied by the patterns, since this check was emitted before any operand constraints. Really, these are pattern level predicates that implicitly depend on the instruction and operand checks. Introduce a filtering function so the custom predicate is emitted last. I'm not sure this is the most elegant solution. It seems like this is really a different thing from the InstructionMatcher/IPM_ predicate kinds. I initially tried keeping this in a separate predicate list, but that also seemed awkward. This only half fixes the problem I'm trying to solve. The AMDGPU pattern I'm attempting to port also uses the PredicateCodeUsesOperands feature to allow checks on the source operands when the input pattern is commuted. Really the emitter should reject the pattern since it doesn't handle this case, but at this point it would be more productive to just implement this.

Summary: This patch introduce the parser for OpenACC 3.0 in Flang. It uses the same TableGen mechanism than OpenMP. Reviewers: nvdatian, sscalpone, tskeith, klausler, ichoyjx, jdoerfert, DavidTruby Reviewed By: klausler Subscribers: MaskRay, SouraVX, mgorny, hiraditya, jfb, sstefan1, llvm-commits Tags: #llvm, #flang Differential Revision: https://reviews.llvm.org/D83649

Summary: Without this, printing sets and maps hidden behind using declarations fail. Reviewers: #libc! Subscribers: libcxx-commits Tags: #libc Differential Revision: https://reviews.llvm.org/D83732

This is a prerequisite for having ClangdLSPServer inject its own.

Fixed a typo in `std-ops-to-spitv.mlir` test. Reviewed By: rriddle Differential Revision: https://reviews.llvm.org/D83791

This changes the matrix load/store intrinsic definitions to load/store from/to a pointer, and not from/to a pointer to a vector, as discussed in D83477. This also includes the recommit of "[Matrix] Tighten LangRef definitions and Verifier checks" which adds improved language reference descriptions of the matrix intrinsics and verifier checks. Differential Revision: https://reviews.llvm.org/D83785

Summary: Changed default F18_FC from pgf90 to gfortran. Removed unnecessary references to pgf90 in favor of more generic naming. Reviewers: sscalpone, richard.barton.arm, DavidTruby, jdoerfert, clementval Reviewed By: sscalpone, richard.barton.arm, clementval Subscribers: sstefan1, tskeith, klausler, clementval, flang-commits, llvm-commits Tags: #llvm, #flang Differential Revision: https://reviews.llvm.org/D83488

…til after ICP" This restores commit 80d0a13, and the follow on fix in 873c0d0, with a new fix for test failures after a 2-stage clang bootstrap, and a more robust fix for the Chromium build failure that an earlier version partially fixed. See also discussion on D75201. Reviewers: evgeny777 Subscribers: mehdi_amini, Prazek, hiraditya, steven_wu, dexonsmith, arphaman, davidxl, cfe-commits, llvm-commits Tags: #clang, #llvm Differential Revision: https://reviews.llvm.org/D73242

This patch adds support for archive files as inputs to llvm-link. One of the use-cases is for OpenMP, where device specific libraries need to be extracted from libraries containing bundled object files. The clang-offload-bundler will support extracting these archives, which will be passed into llvm-link, see https://reviews.llvm.org/D80816. Reviewed By: jdoerfert Differential Revision: https://reviews.llvm.org/D81109

Summary: (Possible to flip back on the branch if this breaks things) Reviewers: kadircet Subscribers: ilya-biryukov, MaskRay, jkorous, arphaman, usaxena95, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D83790

Summary: Add debug counter and stats counter to assume queries and assume builder here is the collected stats on a build of check-llvm + check-clang. "assume-builder.NumAssumeBuilt": 2720879, "assume-builder.NumAssumesMerged": 761396, "assume-builder.NumAssumesRemoved": 1576212, "assume-builder.NumBundlesInAssumes": 6518809, "assume-queries.NumAssumeQueries": 85566380, "assume-queries.NumUsefullAssumeQueries": 2727360, the NumUsefullAssumeQueries stat is actually pessimistic because in a few places queries ask to keep providing information to try to get better information. and this isn't counted as a usefull query evem tho it can be usefull Reviewers: jdoerfert Reviewed By: jdoerfert Subscribers: hiraditya, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D83506

This patch handles CFI with basic block sections, which unlike DebugInfo does not support ranges. The DWARF standard explicitly requires emitting separate CFI Frame Descriptor Entries for each contiguous fragment of a function. Thus, the CFI information for all callee-saved registers (possibly including the frame pointer, if necessary) have to be emitted along with redefining the Call Frame Address (CFA), viz. where the current frame starts. CFI directives are emitted in FDE’s in the object file with a low_pc, high_pc specification. So, a single FDE must point to a contiguous code region unlike debug info which has the support for ranges. This is what complicates CFI for basic block sections. Now, what happens when we start placing individual basic blocks in unique sections: * Basic block sections allow the linker to randomly reorder basic blocks in the address space such that a given basic block can become non-contiguous with the original function. * The different basic block sections can no longer share the cfi_startproc and cfi_endproc directives. So, each basic block section should emit this independently. * Each (cfi_startproc, cfi_endproc) directive will result in a new FDE that caters to that basic block section. * Now, this basic block section needs to duplicate the information from the entry block to compute the CFA as it is an independent entity. It cannot refer to the FDE of the original function and hence must duplicate all the stuff that is needed to compute the CFA on its own. * We are working on a de-duplication patch that can share common information in FDEs in a CIE (Common Information Entry) and we will present this as a follow up patch. This can significantly reduce the duplication overhead and is particularly useful when several basic block sections are created. * The CFI directives are emitted similarly for registers that are pushed onto the stack, like callee saved registers in the prologue. There are cfi directives that emit how to retrieve the value of the register at that point when the push happened. This has to be duplicated too in a basic block that is floated as a separate section. Differential Revision: https://reviews.llvm.org/D79978

…sed has live users after conversion Up until now, there has been an implicit agreement that when an operation is marked as "erased" all uses of that operation's results are guaranteed to be removed during conversion. How this works in practice is that there is either an assert/crash/asan failure/etc. This revision adds support for properly detecting when an erased operation has dangling users, emits and error and fails the conversion. Differential Revision: https://reviews.llvm.org/D82830

Summary: Ignore callback uses when adding a callback function in the CallGraph. Callback functions are typically created when outlining, e.g. for OpenMP, so they have internal scope and linkage. They should not be added to the ExternalCallingNode since they are only callable by the specified caller function at creation time. A CGSCC pass, such as OpenMPOpt, may need to update the CallGraph by adding a new outlined callback function. Without ignoring callback uses, adding breaks CGSCC pass restrictions and results to a broken CallGraph. Reviewers: jdoerfert Subscribers: hiraditya, sstefan1, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D83370

This adds a `parseOptionalAttribute` method to the OpAsmParser that allows for parsing optional attributes, in a similar fashion to how optional types are parsed. This also enables the use of attribute values as the first element of an assembly format optional group. Differential Revision: https://reviews.llvm.org/D83712

Use short division of big-radix values by powers of two when converting values with negative unbiased exponents rather than multiplication by smaller powers of five; this reduces the overall outer iteration count. This change is a win across the entire range of inputs. Reviewed By: tskeith Differential Revision: https://reviews.llvm.org/D83806

For `.reloc offset, *, *`, currently offset can be a constant or symbol. This patch makes it support any expression which can be folded to sym+constant. Reviewed By: stefanp Differential Revision: https://reviews.llvm.org/D83751

Instead of detecting it automatically but also allowing for the setting to be specified explicitly, always detect whether exceptions are enabled based on whether -fno-rtti (or equivalent) is used. It's less confusing to have a single way of tweaking that knob. This change follows the lead of 71d88ce.

Always clean up subprocesses on tear down instead of relying on the caller to do so. This is not only less error prone but also means the tests can be more concise. Differential revision: https://reviews.llvm.org/D83787

Remote connections are not supported on Windows.

Summary: This allows users of the llvm library discover whether llvm was built with the tensorflow c API dependency, which helps if using the TFUtils wrapper, for example. We don't do the same for the LLVM_HAVE_TF_AOT flag, because that does not expose any API. Reviewers: mehdi_amini, davidxl Subscribers: mgorny, aaron.ballman, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D83746

We need to retain carriage return characters in source files that are not parts of multi-byte line endings; they are significant in CHARACTER literal constants. Reviewed By: tskeith Differential Revision: https://reviews.llvm.org/D83808

This should have been included in D69585. Differential Revision: https://reviews.llvm.org/D83622

Following on fcf7cc2 and 672207c which granted checks the ability to read boolean configuration arguments as `true` or `false`. This enables storing the options back to the configuration file using `true` and `false`. This is in line with how clang-format dumps boolean options in its style config. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D83053

Reviewers: efriedma, lebedev.ri, fhahn, c-rhodes, david-arm Reviewed By: efriedma, david-arm Subscribers: tschuett, rkruppe, psnobl, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D83001

…to FuzzerPlatform.h, and adjust includes in other files. Summary: This patch separates platform related macros in lib/fuzzer/FuzzerDefs.h into lib/fuzzer/FuzzerPlatform.h, and use FuzzerPlatform.h where necessary. This separation helps when compiling libFuzzer's interceptor module (under review); an unnecessary include of standard headers (such as string.h) may produce conflicts/ambiguation with the interceptor's declarations/definitions of library functions, which complicates interceptor implementation. Reviewers: morehouse, hctim Reviewed By: morehouse Subscribers: krytarowski, #sanitizers Tags: #sanitizers Differential Revision: https://reviews.llvm.org/D83805

Summary: -fembed-bitcode options doesn't embed warning options since they are useless to code generation. Make sure it handles the W_value group and not embed those options in the output. Reviewers: zixuw, arphaman Reviewed By: zixuw Subscribers: jkorous, dexonsmith, ributzka, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D83813

This reverts commit 9b7e24c. See comments in https://reviews.llvm.org/D82148.

…olymorphic value Summary: C7113 States that "An ac-value shall not be unlimited polymorphic." We failed to detect this situation which resulted in a crash when trying to get the underlying derived type specification of the unlimited polymorphic value. I added code to avoid the crash, code to emit an error message, and a test. Reviewers: klausler, tskeith, DavidTruby Subscribers: llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D83793

… definitions. Summary: This patch fixes sanitizer-windows build errors. Reviewers: morehouse, hctim Reviewed By: morehouse, hctim Subscribers: #sanitizers Tags: #sanitizers Differential Revision: https://reviews.llvm.org/D83823

It was basically impossible to figure out where the failure point was

I/O from/to an unopened unit number needs to open &/or create a "fort.$UNIT" file. Fixes FCVS test fm401.f. Reviewed By: tskeith Differential Revision: https://reviews.llvm.org/D83809

Create the reproducer directory under the build root if it doesn't exists. The reproducer will only create the top level directory.

Allow repeated nulls in list-directed input (e.g., "4*,") and ignore excess characters in list-directed LOGICAL input after the T or F. Fixes FCVS test fm923.f. Reviewed By: sscalpone Differential Revision: https://reviews.llvm.org/D83810

IR archive.

destructor via a pointer of the wrong static type. This caused crashes during deallocation in C++14 builds when using a deallocator whose sized delete requires the size argument to be correct. Also make the LazyCallThroughManager destructor protected to catch this sort of bug in the future.

Summary: This patch adds semantic checking for the OpenACC 3.0 clauses validity. Reviewers: sscalpone, tskeith, klausler, ichoyjx, DavidTruby, jdoerfert Reviewed By: tskeith, klausler Subscribers: mgorny, llvm-commits Tags: #llvm, #flang Differential Revision: https://reviews.llvm.org/D83807

This pacth fix out-of-tree build of Flang after the introduction of acc_gen. Reviewed By: sscalpone Differential Revision: https://reviews.llvm.org/D83835

the form that takes func as an argument isn't compatible with the optional bugnumber argument. This means that only correct for to use it is now @skipIfRosetta(bugnumber='url')

all clients to delete it via the correct dynamic type.

…ry to create a load/store/alloca with no alignment or insertion position If no alignment is specified we try to find the datalayout by using the insert position to get the module so we can get the datalayout. But if those are null, then we deference a null pointer. This patch adds asserts to make the failure a little more obvious than just seg faulting. Differential Revision: https://reviews.llvm.org/D83829

Fixes an UBSAN error.

Summary: The `getIdAddr()` function returns the address of the ID of the abstract attribute Reviewers: jdoerfert, sstefan1, uenoku, homerdin, baziotis Reviewed By: jdoerfert Subscribers: okura, hiraditya, uenoku, kuter, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D83172

Add handling of s_andn2 and mask of 0. This eliminates redundant instructions from uniform control flow. Reviewed By: rampitec Differential Revision: https://reviews.llvm.org/D83641

Summary: This patch introduces basic unittest interface for the Attributor and a simple test case for casting. Reviewers: jdoerfert, sstefan1, uenoku, homerdin, baziotis Reviewed By: jdoerfert Subscribers: mgorny, uenoku, kuter, okura, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D83754

Summary: This patch added dependency graph to the attributor so that we can dump the dependencies between AAs more easily. We can also apply general graph algorithms to the graph, making it easier for us to create deep wrappers. Reviewers: jdoerfert, sstefan1, uenoku, homerdin, baziotis Reviewed By: jdoerfert Subscribers: jfb, okura, mgrang, kuter, lebedev.ri, hiraditya, uenoku, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D78861

Rather than handling zlib handling manually, use find_package from CMake to find zlib properly. Use this to normalize the LLVM_ENABLE_ZLIB, HAVE_ZLIB, HAVE_ZLIB_H. Furthermore, require zlib if LLVM_ENABLE_ZLIB is set to YES, which requires the distributor to explicitly select whether zlib is enabled or not. This simplifies the CMake handling and usage in the rest of the tooling. This is a reland of abb0075 with all followup changes and fixes that should address issues that were reported in PR44780. Differential Revision: https://reviews.llvm.org/D79219

This reverts commit 6b78ed6.

Summary: This patch added dependency graph to the attributor so that we can dump the dependencies between AAs more easily. We can also apply general graph algorithms to the graph, making it easier for us to create deep wrappers. Reviewers: jdoerfert, sstefan1, uenoku, homerdin, baziotis Reviewed By: jdoerfert Subscribers: jfb, okura, mgrang, kuter, lebedev.ri, hiraditya, uenoku, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D78861

This reverts commit 8c1a79d because it fails when zlib isn't installed.

Since D83271 we can optimize the GPU state machine to avoid spurious call edges that increase the register usage of kernels. With this patch we inform the user why and if this optimization is happening and when it is not. Reviewed By: ye-luo Differential Revision: https://reviews.llvm.org/D83707

Since D82572, we keep "reference" edges for callback call sites. While not strictly necessary they can improve the traversal order. However, we did not update them properly in case a pass removed the callback call site which caused a verification error (PR46687). With this patch we update these reference edges properly during the invocation of `CallGraphSCCPass::RefreshCallGraph` in non-checking mode. Reviewed By: sdmitriev Differential Revision: https://reviews.llvm.org/D83718

During code generation we might change/add basic blocks so keeping a list of them is fairly easy to break. Nested parallel regions were enough. The new scheme does recompute the list of blocks to be outlined once it is needed. Reviewed By: anchu-rajendran Differential Revision: https://reviews.llvm.org/D82722

This reverts commit 8df7af5.

…on name

The dependencies in llvm/unittests/Transforms/IPO/CMakeLists.txt introduced in revision 0750757 were incomplete, leading to link errors for a DBUILD_SHARED_LIBS=True build.

Summary: This change avoids exposing tensorflow types when including TFUtils.h. They are just an implementation detail, and don't need to be used directly when implementing an analysis requiring ML model evaluation. The TFUtils APIs, while generically typed, are still not exposed unless the tensorflow C library is present, as they currently have no use otherwise. Reviewers: mehdi_amini, davidxl Subscribers: hiraditya, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D83843

…options Differential Revision: https://reviews.llvm.org/D83720

…y to vector.transfer Summary: linalg.copy + linalg.fill can be used to create a padded local buffer. The `masked` attribute is only valid on this padded buffer. When forwarding to vector.transfer ops, the attribute must be reset conservatively. Differential Revision: https://reviews.llvm.org/D83782

Summary: A reshape aliases its input memref, so it acts like a view. Differential Revision: https://reviews.llvm.org/D83773

This patch addresses the comments from https://reviews.llvm.org/D83030 and https://reviews.llvm.org/D82639. `this->` is removed when not inside the template. Also, type conversion for `spv.func` takes `convertRegionTypes()` in order to apply type conversion on all blocks within the function. Reviewed By: rriddle Differential Revision: https://reviews.llvm.org/D83786

They currently show that the not equal case may be improved. See PR42876 Differential Revision: https://reviews.llvm.org/D65801

The existing code already considered this case. Unfortunately a typo in the condition prevents it from triggering. Also the existing code, had it run, forgot to do the folding. This fixes PR42876. Differential Revision: https://reviews.llvm.org/D65802

Currently if two multi-letter extensions are provided in a -march= string, the verification code checks the version of the first and consumes the second, resulting in that part of the architecture string being ignored. This adds a test that when a version number has been parsed for an extension, there are no subsequent characters. Differential Revision: https://reviews.llvm.org/D83819

…stantPast value Summary: Certain `NSDate` constructors return a special `NSConstantDate` class which currently ends up being unformatted as it's not in the list of supported classes for the NSDate formatter. This patch adds that class to the supported class list so LLDB produces a summary for it. One of these special constructors is `[NSDate distantPast]` which returns the date for `0001-01-01 00:00:00 UTC`. LLDB has a special case for formatting this date but for some reason we did hardcode the wrong summary string in that special case. Maybe the summary string was correct back when the code was written but it isn't correct anymore (`distantPast` isn't actually defined to be a special date but just some 'a guaranteed temporal boundary.' so maybe someone changed the value in the last 10 years). If someone else is wondering why we even have this special case for `distantPast` but not for the future. The reason seems to be that our date formatting for really old dates is off by 24 hours. So for example, adding one second to `distantPast` will cause LLDB to print `0000-12-30 00:00:01 UTC` (which is 24 hours behind the expected result). So to make our code appear to be correct it seems we just hardcoded the most common NSDate result from that time span. I'll replace that logic with a generic solution in a probably more invasive follow up patch. I also took the freedom to replace the magic value `-63114076800` with some constant + documentation. I heard there are some people that don't know from the top of their head that there are 63114076800 seconds between 1. Jan 0001 and 1. January 2001 in whatever calendar system NSDate is using. Reviewers: mib, davide Reviewed By: mib Subscribers: JDevlieghere Differential Revision: https://reviews.llvm.org/D83217

Summary: Failure type 1: This test can fail when the path of the build includes the strings we're checking for. E.g "/gcc" is found in ".../gcc_7.3.0/..." To correct this look for '"' on the end of all matches. So that we only match the end of paths printed by clang -###. (which would be ".../gcc_7.3.0/.../gcc" for the example) Also look for other gcc names like gcc-x.y.z in the first check. This confirms that the copy of clang we made is isolated as expected. Failure type 2: If you use a triple like "powerpc64le-linux-gnu" clang actually reports "powerpc64le-unknown-linux-gnu". Then it searches for the former. That combined with Mac OS adding a version number to cmake's triple means we can't trust cmake or clang to give us the one default triple. To fix the test, write to both names. As they don't overlap with our fake triple, we're still showing that the lookup works. Reviewers: MaskRay, stevewan Reviewed By: stevewan Subscribers: miyuki, JDevlieghere, steven.zhang, stevewan, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D83055

Some of the system registers readable on AArch64 and ARM platforms return different values with each read (for example a timer counter), these shouldn't be hoisted outside loops or otherwise interfered with, but the normal @llvm.read_register intrinsic is only considered to read memory. This introduces a separate @llvm.read_volatile_register intrinsic and maps all system-registers on ARM platforms to use it for the __builtin_arm_rsr calls. Registers declared with asm("r9") or similar are unaffected.

Fix incorrect use of the size of Path when accessing PathUTF16, as the UTF-16 path can be shorter. Added unit test for coverage of this test case. Thanks to Ding Fei (danix800) for the code fix, see https://reviews.llvm.org/D83321. Differential Revision: https://reviews.llvm.org/D83689

This improves condition in the ELFFile::program_headers(). Previously if was possible to read the headers from the wrong place when the value of e_phoff was so large that computation overflowed. Differential revision: https://reviews.llvm.org/D83774

In 2b3c505, the pointer arguments for the matrix load and store intrinsics was changed to always be the element type of the vector argument. This patch updates the MatrixBuilder to not add the pointer type to the overloaded types and adjusts the clang/mlir tests. This should fix a few build failures on GreenDragon, including http://green.lab.llvm.org/green/job/test-suite-verify-machineinstrs-x86_64-O0-g/7891/

In D83482 we agreed to name e_* fields that are used for overriding values (like e_phoff) as EPh* (e.g. EPhOff). Currently we have a set of e_sh* fields that are named inconsistently with this rule. This patch renames all of them. Differential revision: https://reviews.llvm.org/D83766

Summary: Without these, the generic branch relaxation pass will underestimate the range required for branches spanning these and we can end up with "fixup value out of range" errors rather than relaxing the branches. Some of the instructions in the expansion may end up being compressed but exactly determining that is awkward, and these conservative values should be safe, if slightly suboptimal in rare cases. Reviewers: asb, lenary, luismarques, lewis-revill Reviewed By: asb, luismarques Subscribers: hiraditya, rbar, johnrusso, simoncook, sabuasal, niosHD, kito-cheng, shiva0217, MaskRay, zzheng, edward-jones, rogfer01, MartinMosbeck, brucehoult, the_o, rkruppe, jfb, PkmX, jocewei, psnobl, benna, Jim, s.egerton, pzheng, sameer.abuasal, apazos, evandro, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D77443

Follow-on from D77443. Although we're not fixing any of these pseudo-instructions, the potential for them to be out of sync still exists.

Names of YAML keys changed in rG7a587ca93200c49e47fe205ce037895c81c5a542

# Conflicts: # .gitignore # README.md # clang-tools-extra/clang-tidy-vs/ClangTidy/packages.config # clang-tools-extra/clangd/CMakeLists.txt # clang-tools-extra/clangd/ClangdLSPServer.cpp # clang-tools-extra/clangd/ClangdLSPServer.h # clang-tools-extra/clangd/ClangdServer.cpp # clang-tools-extra/clangd/ClangdServer.h # clang-tools-extra/clangd/Diagnostics.cpp # clang-tools-extra/clangd/tool/ClangdMain.cpp # clang/include/clang/AST/ASTContext.h # clang/include/clang/AST/ASTNodeTraverser.h # clang/include/clang/AST/Decl.h # clang/include/clang/AST/DeclBase.h # clang/include/clang/AST/Expr.h # clang/include/clang/AST/Stmt.h # clang/include/clang/AST/TextNodeDumper.h # clang/include/clang/AST/Type.h # clang/include/clang/AST/TypeNodes.def # clang/include/clang/Basic/CodeGenOptions.def # clang/include/clang/Basic/DiagnosticGroups.td # clang/include/clang/Basic/DiagnosticParseKinds.td # clang/include/clang/Basic/DiagnosticSemaKinds.td # clang/include/clang/Basic/Specifiers.h # clang/include/clang/Driver/Options.td # clang/include/clang/Parse/Parser.h # clang/include/clang/Sema/DeclSpec.h # clang/include/clang/Serialization/ASTBitCodes.h # clang/include/clang/Serialization/ASTReader.h # clang/include/clang/Serialization/ASTWriter.h # clang/lib/AST/ASTContext.cpp # clang/lib/AST/ASTImporter.cpp # clang/lib/AST/ASTStructuralEquivalence.cpp # clang/lib/AST/CMakeLists.txt # clang/lib/AST/Decl.cpp # clang/lib/AST/Expr.cpp # clang/lib/AST/ItaniumMangle.cpp # clang/lib/AST/TextNodeDumper.cpp # clang/lib/AST/Type.cpp # clang/lib/AST/TypePrinter.cpp # clang/lib/Basic/IdentifierTable.cpp # clang/lib/CMakeLists.txt # clang/lib/CodeGen/CGDebugInfo.h # clang/lib/CodeGen/CGDecl.cpp # clang/lib/CodeGen/CGExpr.cpp # clang/lib/CodeGen/CodeGenFunction.cpp # clang/lib/CodeGen/ItaniumCXXABI.cpp # clang/lib/Frontend/CompilerInvocation.cpp # clang/lib/Parse/ParseDecl.cpp # clang/lib/Parse/ParseDeclCXX.cpp # clang/lib/Parse/ParseExpr.cpp # clang/lib/Parse/ParseExprCXX.cpp # clang/lib/Parse/ParsePragma.cpp # clang/lib/Sema/CMakeLists.txt # clang/lib/Sema/DeclSpec.cpp # clang/lib/Sema/Sema.cpp # clang/lib/Sema/SemaCast.cpp # clang/lib/Sema/SemaChecking.cpp # clang/lib/Sema/SemaDecl.cpp # clang/lib/Sema/SemaExceptionSpec.cpp # clang/lib/Sema/SemaExpr.cpp # clang/lib/Sema/SemaInit.cpp # clang/lib/Sema/SemaTemplateDeduction.cpp # clang/lib/Sema/SemaType.cpp # clang/lib/Sema/TreeTransform.h # clang/lib/Serialization/ASTReader.cpp # clang/lib/Serialization/ASTReaderDecl.cpp # clang/lib/Serialization/ASTReaderStmt.cpp # clang/lib/Serialization/ASTWriter.cpp # clang/lib/Serialization/ASTWriterStmt.cpp # clang/lib/StaticAnalyzer/Core/ExprEngine.cpp # clang/test/AST/ast-dump-attr.m # clang/test/AST/ast-dump-c-attr.c # clang/test/AST/sourceranges.cpp # clang/test/Analysis/designated-initializer.c # clang/test/lit.cfg.py # clang/test/lit.site.cfg.py.in # clang/tools/clang-format-vs/README.txt # clang/tools/clang-import-test/clang-import-test.cpp # llvm/CMakeLists.txt # llvm/include/llvm/Demangle/MicrosoftDemangleNodes.h # llvm/unittests/ADT/CMakeLists.txt

(cherry picked from commit 44140eb) (cherry picked from commit f29b94c)

…ng serialization information)

…ence calls for Checked C specific expressions

…erAST

(cherry picked from commit 08939ad)

…bility methods)

…DumpExprsSet

… ASTRecordWriter

… to generate a bug report

…n type

… and ASTWriter

…/Transformer/SourceCode.h

…rents call in CheckedRegions.cpp

… * from ArgFrontendActonFactory::create

… fix build warnings)

…edArrayKind

…perator with VisitBinaryOperator (due to clang 11 changes to RecursiveASTVisitor)

…ch source range output in Stmt::dump

… output

…_CFG and TRACE_RANGE

…ubscripts, and member expressions

…tions

…terType

…pe and IncompleteArrayType

…eGenericFunction arguments to serialization information for FunctionProtoType

Checked C support. As per the comment on line 1509, the variable NumfunctionDeclBits needs to be 33 (the sum of the sizes of all the bit fields) The size of class CXXConstructorDeclBitfields (on line 1591) needs to be 64 bits. Accordingly, the value of the field NumCtorInitializers (one line 1603) needs to be adjusted.

Comparing StmtExprs causes an assertion failure in CanonBounds.cpp since their children are Stmts, not Exprs. This assertion failure previously caused the CodeGen/arm-neon-range-checks.c test to fail.

…aBounds.cpp

…BoundsCastExpression

…r.c test This reflects the pruning of ImplicitValueInitExprs from the CFG in llvm-project commit 9fdcae7

… the -fno-checkedc-extension argument

* Use VisitUnaryOperator and VisitBinaryOperator VisitUnary* and VisitBin* * Add case for DesignatedInitExpr in getExprConstraintVars

For creating an empty DeclRefExpr, we need to pass NumTemplateArgs. This depends on the NumExprFields. In Checked C, we changed the NumExprFields from 5 to 7. But upstream has this field as 6. So we adjust this and change it to 8. (cherry picked from commit 9902f10)

) 277d84a. We first submitted them in PR #837, but Mandeep noticed (#837 (review)) and the unintended changes were removed from that PR in 74bfcaf. However, when the squash of PR #837 was merged with the original commits in cfc998e, the unintended changes were incorrectly retained. They got submitted again in the next 3C PR (#891), and no one noticed that time. (cherry picked from commit cfe00ea)

…re 9 of them). Needs to be reviewed.

Fixes the SemaOpenCLCXX/address-space-lambda.cl test. DeclaratorChunk::getFunction clears the attribute pool of its TheDeclarator argument if its MethodQualifiers argument is non-null. Previously, a call to getFunction from ParseLambdaExpressionAfterIntroducer was missing the MethodQualifiers argument. This caused the attributes of the declarator to be set incorrectly, which resulted in incorrect OpenCL address spaces for declarations involving lambda expressions.

…into updated-master-11-last # Conflicts: # clang/lib/AST/CanonBounds.cpp # clang/test/CheckedC/inferred-bounds/compound-literals.c

…ax node Checked C binds string literals to temporaries. Add CHKCBindTemporaryExpression as a syntax node and add a separate Checked C case for the StringLiteral syntax test that expects a CHKCBindTemporary parent for StringLiteral expressions.

…AST matcher Checked C binds string literals to temporaries. Add a matcher that ignores parens and temporary bindings on expressions and use the matcher in the IgnoringParens ASTMatcher test.

…penMP test cases after upgrade.

…f some OpenMP test cases after upgrade." This reverts commit 2afbfb5. Reverting this fix in order to resubmit these changes as a PR because it will be easier to incorporate review comments and other changes.

With Git Unix utilities and cygwin utilities, the grep tool does not strip carriage returns from files. When the diff tool compares the output of grep to another file in the ir-support.c test, the output of grep contains carriage returns while the other file does not. This does not occur when using GnuWin32 utilities. The --strip-trailing-cr argument causes diff to remove carriage returns from the input files before comparing them.

…/checkedc-clang into updated-master-11-last

(See commit 5b67a18 which added the ignoringParenTmp matcher)

…in (#979) * Fix for handling CapturedDecl, which was causing the failure of certain OpenMP test case after upgrade. * Addressed review comments. * Addressed David's review comment about handling invalid source locations before calling CompareLoc. * Removed redundant "else". * Removed CompareLoc as this is not the best thing to use in ordering two CapturedDecls. An interim solution using pointer comparison is present, with a TODO for an improved ordering. * Minor fix.

…into updated-master-11-last

Commits on Jan 5, 2021

Add clang/out directory to .gitignore

kakje committed Jan 5, 2021

Configuration menu

View commit details

Copy full SHA for 93749c7

Browse repository at this point

Copy the full SHA

93749c7 View commit details

Browse the repository at this point in the history

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Clang 11 upgrade #984

Clang 11 upgrade #984

Commits on Jul 14, 2020

Commits on Jul 15, 2020

Commits on Dec 15, 2020

Commits on Dec 16, 2020

Commits on Dec 17, 2020

Commits on Dec 18, 2020

Commits on Dec 19, 2020

Commits on Dec 29, 2020

Commits on Dec 31, 2020

Commits on Jan 1, 2021

Commits on Jan 4, 2021

Commits on Jan 5, 2021

Commits on Jan 8, 2021

Commits on Jan 9, 2021

Commits on Jan 12, 2021

Commits on Jan 14, 2021

Commits on Jan 15, 2021

Commits on Jan 18, 2021

Commits on Jan 19, 2021

Commits on Jan 21, 2021

Commits on Jan 23, 2021

Commits on Jan 26, 2021

Commits on Jan 27, 2021

Commits on Feb 2, 2021

Commits on Feb 9, 2021

Commits on Feb 10, 2021

Commits on Feb 12, 2021

Commits on Feb 13, 2021

Commits on Feb 19, 2021

Commits on Feb 20, 2021