| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
clang-format (https://reviews.llvm.org/D33932) to keep primary headers
at the top and handle new utility headers like 'gmock' consistently with
other utility headers.
No other change was made. I did no manual edits, all of this is
clang-format.
This should allow other changes to have more clear and focused diffs,
and is especially motivated by moving some headers into more focused
libraries.
llvm-svn: 304786
|
|
|
|
| |
llvm-svn: 280443
|
|
|
|
| |
llvm-svn: 253408
|
|
|
|
|
|
| |
patch by Jonathan Anderson!
llvm-svn: 253311
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The patch is generated using clang-tidy misc-use-override check.
This command was used:
tools/clang/tools/extra/clang-tidy/tool/run-clang-tidy.py \
-checks='-*,misc-use-override' -header-filter='llvm|clang' \
-j=32 -fix -format
http://reviews.llvm.org/D8925
llvm-svn: 234679
|
|
|
|
|
|
|
|
|
|
| |
mach-o supports "fat" files which are a header/table-of-contents followed by a
concatenation of mach-o files built for different architectures. Currently,
MemoryBuffer has no easy way to map a subrange (slice) of a file which lld
will need to select a mach-o slice of a fat file. The new function provides
an easy way to map a slice of a file into a MemoryBuffer. Test case included.
llvm-svn: 219260
|
|
|
|
| |
llvm-svn: 212405
|
|
|
|
|
|
| |
This finishes the transition to std::error_code.
llvm-svn: 210877
|
|
|
|
|
|
| |
This should make sure that most new uses use the std prefix.
llvm-svn: 210835
|
|
|
|
| |
llvm-svn: 210442
|
|
|
|
| |
llvm-svn: 209102
|
|
|
|
|
|
|
|
| |
This will allow external callers of these functions to switch over time
rather than forcing a breaking change all a once. These particular
functions were determined by building clang/lld/lldb.
llvm-svn: 202959
|
|
|
|
|
|
|
|
|
|
| |
subsequent changes are easier to review. About to fix some layering
issues, and wanted to separate out the necessary churn.
Also comment and sink the include of "Windows.h" in three .inc files to
match the usage in Memory.inc.
llvm-svn: 198685
|
|
|
|
| |
llvm-svn: 193429
|
|
|
|
|
|
| |
page size can be null terminated correctly by MemoryBuffer.
llvm-svn: 189965
|
|
|
|
|
|
| |
contain Offset when Offset >= 65536.
llvm-svn: 189021
|
|
|
|
| |
llvm-svn: 189020
|
|
|
|
| |
llvm-svn: 189001
|
|
|
|
|
|
|
|
| |
is greater than 8000.
PageSize, aka AllocationGranularity, is 65536 on Win32 (and Cygwin).
llvm-svn: 188999
|
|
|
|
|
|
|
| |
Run in two different modes: with and without reopening the temporary file
between creating it and mapping it with MemoryBuffer.
llvm-svn: 186986
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The main observation is that we never need both the filesize and the map size.
When mapping a slice of a file, it doesn't make sense to request a null
terminator and that would be the only case where the filesize would be used.
There are other cleanups that should be done in this area:
* A client should not have to pass the size (even an explicit -1) to say if
it wants a null terminator or not, so we should probably swap the argument
order.
* The default should be to not require a null terminator. Very few clients
require this, but many end up asking for it just because it is the default.
llvm-svn: 186984
|
|
|
|
| |
llvm-svn: 186887
|
|
|
|
| |
llvm-svn: 169250
|
|
Patch by Daniel Malea.
llvm-svn: 165246
|