- Jul 10, 2020
-
-
Albion Fung authored
This patch adds the instruction definitions and the assembly/disassembly tests for the Load/Store VSX Vector Rightmose instructions. Differential Revision: https://reviews.llvm.org/D83364
-
Joel E. Denny authored
Document the default of `fail` in `-help`. Extend `-dump-input=help` to help users find related command-line options, but let `-help` provide their full documentation. Reviewed By: probinson Differential Revision: https://reviews.llvm.org/D83091
-
Craig Topper authored
This time without the change to make operator| use operator&=. That seems to be the source of the gcc 5.3 miscompile. Original commit message: These represent the same thing but 64BIT only showed up from getHostCPUFeatures providing a list of featuers to clang. While EM64T showed up from getting the features for a named CPU. EM64T didn't have a string specifically so it would not be passed up to clang when getting features for a named CPU. While 64bit needed a name since that's how it is index. Merge them by filtering 64bit out before sending features to clang for named CPUs.
-
Stanislav Mekhanoshin authored
This is practically NFC at the moment because nothing really asks the real number or does anything useful with it. Differential Revision: https://reviews.llvm.org/D82202
-
Sanjay Patel authored
-
Sanjay Patel authored
-
Sanjay Patel authored
-
Sanjay Patel authored
-
Sanjay Patel authored
-
Nikita Popov authored
Make it easier to debug renaming issues.
-
Roman Lebedev authored
This likely has broken test/Transforms/Attributor/IPConstantProp/ tests. http://45.33.8.238/linux/22502/step_12.txt This reverts commit 205dc092.
-
Eric Christopher authored
as it's causing build errors with another clang so I'll need to approach this differently. This reverts commit c2827083.
-
Eric Christopher authored
as it was failing in Release+Asserts mode with an assert. This reverts commit bd206803.
-
Fangrui Song authored
This reverts commit c92a8c0a. It breaks builds and has unaddressed review comments.
-
Giorgis Georgakoudis authored
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
-
Roman Lebedev authored
Summary: This handles all three places where attributes could currently be - `GlobalVariable`, `Function` and `CallBase`. For last two, it correctly handles all three possible attribute locations (return value, arguments and function itself) There was a previous attempt at it D73853, which was committed in rGfc62b36a, but then reverted all the way back in rGb12176d2 due to some (osx?) test failures. Reviewers: nickdesaulniers, dblaikie, diegotf, george.burgess.iv, jdoerfert, Tyker, arsenm Reviewed By: nickdesaulniers Subscribers: wdng, MaskRay, arsenm, llvm-commits, mgorny Tags: #llvm Differential Revision: https://reviews.llvm.org/D83351
-
Roman Lebedev authored
Summary: As per lengthy/heated disscussion in D83351, and CodingStandards D83431. Reviewers: dblaikie, nickdesaulniers Reviewed By: nickdesaulniers Subscribers: llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D83434
-
Roman Lebedev authored
Reviewers: nickdesaulniers, dblaikie Reviewed By: nickdesaulniers Subscribers: llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D83435
-
Roman Lebedev authored
Summary: As per disscussion in D83351, using `for_each` is potentially confusing, at least in regards to inconsistent style (there's less than 100 `for_each` usages in LLVM, but ~100.000 `for` range-based loops Therefore, it should be avoided. Reviewers: dblaikie, nickdesaulniers Reviewed By: dblaikie, nickdesaulniers Subscribers: hubert.reinterpretcast, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D83431
-
Roman Lebedev authored
And just after 3 days, we have a hit in `InstCombiner::mergeStoreIntoSuccessor()`: https://bugs.llvm.org/show_bug.cgi?id=46661 To be recommitted once that is addressed. This reverts commit cd7f8051.
-
Petr Hosek authored
This change adds the necessary flags for building the full Fuchsia toolchain on Windows with MSVC. Differential Revision: https://reviews.llvm.org/D73810
-
Zequan Wu authored
Reviewers: hans, chandlerc!, asbirlea, nikic Reviewed By: hans, nikic Subscribers: steven_wu, dexonsmith, nikic, echristo, void, zhizhouy, cfe-commits, aeubanks, MaskRay, jvesely, nhaehnle, hiraditya, kerbowa, llvm-commits Tags: #llvm, #clang Differential Revision: https://reviews.llvm.org/D83013
-
Christopher Tetreault authored
Reviewers: efriedma, fpetrogalli, sdesmalen, RKSimon, arsenm Reviewed By: RKSimon Subscribers: wdng, tschuett, hiraditya, rkruppe, psnobl, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D82210
-
Craig Topper authored
Follow up from the transform being removed in D83360. If X is probably not poison, then the transform is safe. Still plan to remove or adjust the code from ConstantFolding after this. Differential Revision: https://reviews.llvm.org/D83440
-
Louis Dionne authored
This reduces the set of substitutions required to run the test suite.
-
David Tenty authored
Summary: AIX uses an environment variable called OBJECT_MODE to indicate to utilities in the toolchain whether they should be operating in 32-bit or 64-bit mode. This patch makes the clang driver recognize the current OBJECT_MODE setting when we are operating with an AIX target and adds a custom diagnostic for invalid settings. For more details about OBJECT_MODE on AIX see: https://www.ibm.com/support/knowledgecenter/SSGH2K_13.1.3/com.ibm.xlc1313.aix.doc/compiler_ref/tusetenv1.html https://www.ibm.com/support/knowledgecenter/SSGH2K_13.1.3/com.ibm.xlc1313.aix.doc/compiler_ref/opt_3264.html Reviewers: stevewan, hubert.reinterpretcast, ShuhongL, jasonliu Reviewed By: hubert.reinterpretcast, jasonliu Subscribers: jasonliu, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D82476
-
Jeremy Bruestle authored
Reviewed By: bondhugula, flaub Differential Revision: https://reviews.llvm.org/D82600
-
Jan Korous authored
This assert was failing: assert(CAT && "unexpected type for array initializer"); until this patch landed: 9a7eda1b PR45350: Handle unsized array CXXConstructExprs in constant evaluation
-
Kyungwoo Lee authored
Differential Revision: https://reviews.llvm.org/D83456
-
Jonas Devlieghere authored
There are bugs where you don't want the signal handler to trigger, most notably when that will cause another crash. Examples of this are lldb running out of memory or a bug in the reproducer generation code. This adds an escape hatch trough a (developer oriented) flag to not install the signal handler. rdar://problem/65149595 Differential revision: https://reviews.llvm.org/D83496
-
Jonas Devlieghere authored
This is a preparatory rename of the developer facing reproducer flags. reproducer-skip-version-check -> reproducer-no-version-check reproducer-auto-generate -> reproducer-generate-on-quit
-
Puyan Lotfi authored
The following: https://reviews.llvm.org/D82552 fixed an assert in the SelectionDag ISel legalizer for some CCs on armv7. I noticed that this fix also fixes the assert when using fastcc, so I am adding a fastcc regression test here. Differential Revision: https://reviews.llvm.org/D82443
-
cchen authored
Reviewers: ABataev, jdoerfert Reviewed By: ABataev Subscribers: yaxunl, guansong, arphaman, sstefan1, cfe-commits, sandoval, dreachem Tags: #clang Differential Revision: https://reviews.llvm.org/D82800
-
Louis Dionne authored
This preserves existing behavior before f5f58f1f.
-
Eric Christopher authored
-
Craig Topper authored
[InstSimplify] Don't fold vectors of partial undef in SimplifySelectInst if the non-undef element value might produce poison We can't fold to the non-undef value unless we know it isn't poison. So check each element with isGuaranteedNotToBeUndefOrPoison. This currently rules out all constant expressions. Differential Revision: https://reviews.llvm.org/D83442
-
Louis Dionne authored
-
Craig Topper authored
If we don't immediately lower the vector shift, the splat constant vector we created may get turned into a constant pool load before we get around to lowering the shift. This makes it a lot more difficult to create a shift by constant. Sometimes we fail to see through the constant pool at all and end up trying to lower as if it was a variable shift. This requires custom handling and may create an unsupported vselect on pre-sse-4.1 targets. Since we're after LegalizeVectorOps we are unable to legalize the unsupported vselect as that code is in LegalizeVectorOps rather than LegalizeDAG. So calling LowerShift immediately ensures that we get see the splat constant. Fixes PR46527. Differential Revision: https://reviews.llvm.org/D83455
-
David Blaikie authored
These were initially added to cleanup some transient/leftover files in r372054. Now that's all cleaned up, these are no longer needed.
-
Hiroshi Yamauchi authored
-