- Apr 09, 2019
-
-
Chen Zheng authored
Differential Revision: https://reviews.llvm.org/D60395 llvm-svn: 358017
-
Alexey Bataev authored
Patch allows to use allocate directives on the function parameters. llvm-svn: 358016
-
Stanislav Mekhanoshin authored
One of out of tree targets has regressed with this patch. Reverting it for now and let liveness to be fully reconstructed in case pass was used after the LIS is created to resolve the regression. Differential Revision: https://reviews.llvm.org/D60466 llvm-svn: 358015
-
Nikita Popov authored
This is D59386 for the signed add case. The computeConstantRange() result is now intersected into the existing known bits information, allowing to detect additional no-overflow/always-overflow conditions (though the latter isn't used yet). This (finally...) covers the motivating case from D59071. Differential Revision: https://reviews.llvm.org/D60420 llvm-svn: 358014
-
Sanjay Patel authored
Similar to: rL358005 Forego folding arbitrary vector constants to fix a possible miscompile bug. We can enhance the transform if we do want to handle the more complicated vector case. llvm-svn: 358013
-
Fangrui Song authored
In a sorted list of non-overlapping [LowPC,HighPC) ranges, locating an address with upper_bound on HighPC is simpler than lower_bound on LowPC. llvm-svn: 358012
-
Kostya Kortchinsky authored
Summary: As with other Sanitizers, and the current version of Scudo, we can provide flags in differents way: at compile time, through a weak function, through an environment variable. This change adds support for the configuration flags, and the string parsers. Those are fairly similar to the sanitizer_common way of doing things. Reviewers: morehouse, hctim, vitalybuka Reviewed By: morehouse, vitalybuka Subscribers: mgorny, delcypher, jdoerfert, #sanitizers, llvm-commits Tags: #llvm, #sanitizers Differential Revision: https://reviews.llvm.org/D59597 llvm-svn: 358011
-
Sanjay Patel authored
llvm-svn: 358010
-
Martin Storsjö authored
In this case, CMake doesn't know about the c++abi target within the same CMake run. This reverts this aspect back to how it was before SVN r357811. Differential Revision: https://reviews.llvm.org/D60448 llvm-svn: 358009
-
Sanjay Patel authored
llvm-svn: 358008
-
Sanjay Patel authored
llvm-svn: 358007
-
Raphael Isemann authored
llvm-svn: 358006
-
Sanjay Patel authored
// 0 - (X sdiv C) -> (X sdiv -C) provided the negation doesn't overflow. This fold has been around for many years and nobody noticed the potential vector miscompile from overflow until recently... So it seems unlikely that there's much demand for a vector sdiv optimization on arbitrary vector constants, so just limit the matching to splat constants to avoid the possible bug. Differential Revision: https://reviews.llvm.org/D60426 llvm-svn: 358005
-
Nico Weber authored
llvm-svn: 358004
-
Sanjay Patel authored
llvm-svn: 358003
-
Tom Stellard authored
Summary: The current llvm/clang et al. project can be built with the latest developer toolset (devtoolset-8) on RHEL, which provides GCC 8.2.1. However, the result compiler will not identify this toolset itself when compiling programs, which is of course not desirable. After the patch - which simply adds the name of the developer toolset to the existing list - it gets identified and selected, as shown below: [bamboo@bamboo llvm-project]$ clang -v clang version 9.0.0 (https://github.com/llvm/llvm-project.git e5ac385f) Target: x86_64-unknown-linux-gnu Thread model: posix InstalledDir: /home/bamboo/llvm/bin Found candidate GCC installation: /opt/rh/devtoolset-4/root/usr/lib/gcc/x86_64-redhat-linux/5.2.1 Found candidate GCC installation: /opt/rh/devtoolset-7/root/usr/lib/gcc/x86_64-redhat-linux/7 Found candidate GCC installation: /opt/rh/devtoolset-8/root/usr/lib/gcc/x86_64-redhat-linux/8 Found candidate GCC installation: /usr/lib/gcc/x86_64-redhat-linux/4.8.2 Found candidate GCC installation: /usr/lib/gcc/x86_64-redhat-linux/4.8.5 Selected GCC installation: /opt/rh/devtoolset-8/root/usr/lib/gcc/x86_64-redhat-linux/8 Candidate multilib: .;@m64 Candidate multilib: 32;@m32 Selected multilib: .;@m64 Patch By: Radu-Adrian Popescu Reviewers: tstellar, fedor.sergeev Reviewed By: tstellar Subscribers: jdoerfert, cfe-commits Tags: #clang Differential Revision: https://reviews.llvm.org/D59987 llvm-svn: 358002
-
Nemanja Ivanovic authored
This patch factors out mappings of scalar maths functions to their vector counterparts from TargetLibraryInfo.cpp to a separate VecFuncs.def file. Such mappings are currently available for Accelerate framework, and SVML library. This is in support of the follow-up: https://reviews.llvm.org/D59881 Patch by pjeeva01 Differential revision: https://reviews.llvm.org/D60211 llvm-svn: 358001
-
Chen Zheng authored
llvm-svn: 358000
-
Simon Pilgrim authored
An older version of this could return false but now that this always succeeds we can just inline and simplify it. llvm-svn: 357999
-
Anton Afanasyev authored
Summary: Use optimized hashing while writing time trace by join two hashes to one. Used for -ftime-trace option. Reviewers: rnk, takuto.ikuta Subscribers: hiraditya, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D60404 llvm-svn: 357998
-
Chih-Mao Chen authored
llvm-svn: 357997
-
Chih-Mao Chen authored
Previously the tests in lld for RISC-V were given in yaml format as LLVM's RISC-V assembler support was incomplete. Now that the assembler/disassembler has matured we can rewrite all tests to use LLVM's tools. Differential Revision: https://reviews.llvm.org/D60415 llvm-svn: 357996
-
Chih-Mao Chen authored
The code previously specified a 32-bit range for R_RISCV_HI20 and R_RISCV_LO12_[IS], however this is incorrect as the maximum offset on RV64 that can be formed from the immediate of lui and the displacement of an I-type or S-type instruction is -0x80000800 to 0x7ffff7ff. There is also the same issue with a c.lui and LO12 pair, whose actual addressable range should be -0x20800 to 0x1f7ff. The tests will be included in the next patch that converts all RISC-V tests to use llvm-mc instead of yaml2obj, as assembler support has matured enough to write tests in them. Differential Revision: https://reviews.llvm.org/D60414 llvm-svn: 357995
-
Andi-Bogdan Postelnicu authored
Summary: At Mozilla we are using this tool in order to perform review-time static-analysis, since some patches contain a large number of files we've discovered this issue, where `stderr` gets mixed with `stdout` thus obfuscating our possibility to parse the output. The patch that we are currently use can be found [here](https://searchfox.org/mozilla-central/source/build/build-clang/clang-tidy-8.patch). This is just an upstream of the original patch. Reviewers: JonasToth Reviewed By: JonasToth Subscribers: cfe-commits Tags: #clang, #clang-tools-extra Differential Revision: https://reviews.llvm.org/D60453 llvm-svn: 357994
-
Alex Bradbury authored
There were some errors in the committed test checks, left in due to a git stash apply mishap. llvm-svn: 357993
-
Simon Pilgrim authored
When bitcasting from a source op to a larger bitwidth op, split the demanded bits and OR them on top of one another and demand those merged bits in the SimplifyDemandedBits call on the source op. llvm-svn: 357992
-
Alex Bradbury authored
One of the tests in riscv64-lp64-lp64f-lp64d would have had a different lowering for lp64f/lp64d as a float argument was missed. llvm-svn: 357991
-
Simon Pilgrim authored
llvm-svn: 357990
-
Alex Bradbury authored
Split tests in to files representing the subset of RISC-V ABIs they should have identical output for. llvm-svn: 357989
-
David Stenberg authored
Summary: With MergeValues() removed, amend DebugLocEntry's constructor so that it takes multiple values rather than a single, and keep non-fragment values in OpenRanges, as this allows some cleanup of the code in buildLocationList(). Reviewers: aprantl, dblaikie, loladiro Reviewed By: aprantl Subscribers: hiraditya, llvm-commits Tags: #debug-info, #llvm Differential Revision: https://reviews.llvm.org/D59303 llvm-svn: 357988
-
Simon Pilgrim authored
llvm-svn: 357987
-
Bjorn Pettersson authored
Make sure ASTImporter::Import_New(const Decl *) returns a Expected<const Decl *> and not Expected<Decl *> to make the clang/unittests/AST/ASTImporterTest.cpp compile without the warning clang/unittests/AST/ASTImporterTest.cpp:117:12: error: no viable conversion from 'Expected<clang::Decl *>' to 'Expected<const clang::Decl *>' return Imported; (I got the above when building with clang 3.6). llvm-svn: 357985
-
Pavel Labath authored
Summary: Some of these were present in files which should never be read by swig (and we also had one in the interface file, which is only read by swig). They are probably leftovers from the time when we were running swig over lldb headers directly. While writing this patch, I noticed that some of the #ifdefs were guarding public functions that were operating on lldb_private data types. While it wasn't strictly necessary for this patch, I made these private, as nobody should really be accessing them. This can potentially break existing code if it happened to use these methods, though it will only break at build time -- if someone builds against an old header, he should still be able to link to a new lldb library, since the functions are still there. We could keep these public for backward compatbility, but I would argue that if anyone was actually using these functions for anything, his code is already broken. Reviewers: JDevlieghere, clayborg, jingham Subscribers: lldb-commits Differential Revision: https://reviews.llvm.org/D60400 llvm-svn: 357984
-
Jonas Devlieghere authored
This fixes the following doxygen warning when building the lldb-cpp-doc target. This commit fixes: SBStructuredData.h:94 warning: Found unknown command `\dst' SBStructuredData.h:97 warning: Found unknown command `\dst' SBStructuredData.h:98 warning: Found unknown command `\dst' SBStructuredData.h:100 warning: Found unknown command `\dst' SBStructuredData.h:104 warning: Found unknown command `\dst' Patch by: Konrad Kleine Differential revision: https://reviews.llvm.org/D60443 llvm-svn: 357983
-
Rui Ueyama authored
Because of r357925, this member function doesn't have to be a template of ELFT. llvm-svn: 357982
-
Hiroshi Inoue authored
llvm-svn: 357981
-
Jonas Devlieghere authored
There was a space missing in some the documentation for lldb::BreakpointsWriteToFile. This fixes the following doxygen error when building the lldb-cpp-doc target: llvm-project/lldb/include/lldb/API/SBTarget.h:775 warning: Found unknown command `\btrue' Patch by: Konrad Kleine Differential revision: https://reviews.llvm.org/D60442 llvm-svn: 357980
-
Martin Storsjö authored
llvm-svn: 357979
-
Dan Liew authored
Summary: This will make it easier to expand on the documentation in the future that avoids cluttering the code. rdar://problem/49476995 Reviewers: kubamracek, yln, samsonov, dvyukov, vitalybuka Subscribers: #sanitizers, llvm-commits Tags: #llvm, #sanitizers Differential Revision: https://reviews.llvm.org/D60398 llvm-svn: 357978
-
Pavel Labath authored
llvm-svn: 357977
-