| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
| |
- We don't recognize double or NEON register names yet -- we don't have the
infrastructure to generate the right clobbers for them.
llvm-svn: 110775
|
|
|
|
| |
llvm-svn: 110774
|
|
|
|
| |
llvm-svn: 110764
|
|
|
|
|
|
| |
we have the full fix.
llvm-svn: 110706
|
|
|
|
| |
llvm-svn: 110442
|
|
|
|
| |
llvm-svn: 110370
|
|
|
|
| |
llvm-svn: 110265
|
|
|
|
|
|
|
| |
randomly. This makes us consistently show "-pedantic" as the warning option
for a warning where appropriate.
llvm-svn: 109987
|
|
|
|
|
|
|
| |
the files in the precompiled preamble have changed since it was build,
force the preamble to be rebuilt.
llvm-svn: 109937
|
|
|
|
|
|
| |
PCHReader and PCHWriter are initialized to correctly pick up all initializer. On the upside, this means that there is far less repetition in the dependent PCH now.
llvm-svn: 109823
|
|
|
|
|
|
| |
completely messed up source locations and thus caused a crash whenever a diagnostic was emitted in chained PCH files.
llvm-svn: 109660
|
|
|
|
|
|
|
| |
its absolute path on disk. Also, introduce a fun test for the
precompiled preamble, which almost works...
llvm-svn: 109470
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
reparsing an ASTUnit. When saving a preamble, create a buffer larger
than the actual file we're working with but fill everything from the
end of the preamble to the end of the file with spaces (so the lexer
will quickly skip them). When we load the file, create a buffer of the
same size, filling it with the file and then spaces. Then, instruct
the lexer to start lexing after the preamble, therefore continuing the
parse from the spot where the preamble left off.
It's now possible to perform a simple preamble build + parse (+
reparse) with ASTUnit. However, one has to disable a bunch of checking
in the PCH reader to do so. That part isn't committed; it will likely
be handled with some other kind of flag (e.g., -fno-validate-pch).
As part of this, fix some issues with null termination of the memory
buffers created for the preamble; we were trying to explicitly
NULL-terminate them, even though they were also getting implicitly
NULL terminated, leading to excess warnings about NULL characters in
source files.
llvm-svn: 109445
|
|
|
|
| |
llvm-svn: 109440
|
|
|
|
|
|
| |
into other code. Make it an array instead of a constant-length vector.
llvm-svn: 109384
|
|
|
|
| |
llvm-svn: 109023
|
|
|
|
|
|
| |
intmax_t is __int64 (long long to clang), per VS 2010 stdint.h
llvm-svn: 108980
|
|
|
|
|
|
|
|
| |
reparses an already-parsed translation unit. At the moment it's just a
convenience function, but we hope to use it for performance
optimizations.
llvm-svn: 108756
|
|
|
|
| |
llvm-svn: 108633
|
|
|
|
|
|
|
|
|
|
| |
represent builtins that have the "scanf" attribution (via the format attribute) just
like we do with printf functions. Follow-up work is needed to add similar support
for fscanf et al.
This is to support format-string checking for scanf functions.
llvm-svn: 108499
|
|
|
|
|
|
|
|
| |
whether to use objc_msgSend_fpret; the choice is target dependent, not Obj-C ABI
dependent.
- <rdar://problem/8139758> arm objc _objc_msgSend_fpret bug
llvm-svn: 108379
|
|
|
|
| |
llvm-svn: 108375
|
|
|
|
|
|
| |
constraints, per pr7338.
llvm-svn: 108028
|
|
|
|
| |
llvm-svn: 107956
|
|
|
|
|
|
| |
what gcc does.
llvm-svn: 107953
|
|
|
|
|
|
| |
from PR7583
llvm-svn: 107788
|
|
|
|
| |
llvm-svn: 106873
|
|
|
|
| |
llvm-svn: 106812
|
|
|
|
| |
llvm-svn: 106806
|
|
|
|
|
|
| |
target specific preprocessor define as well.
llvm-svn: 106715
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to use them instead of SourceRange. CharSourceRange is just a SourceRange
plus a bool that indicates whether the range has the end character resolved
or whether the end location is the start of the end token. While most of
the compiler wants to think of ranges that have ends that are the start of
the end token, the printf diagnostic stuff wants to highlight ranges within
tokens.
This is transparent to the diagnostic stuff. To start taking advantage of
the new capabilities, you can do something like this:
Diag(..) << CharSourceRange::getCharRange(Begin,End)
llvm-svn: 106338
|
|
|
|
| |
llvm-svn: 106220
|
|
|
|
| |
llvm-svn: 106188
|
|
|
|
|
|
|
| |
candidates printed. We default to 'all'. At the moment, 'best' prints only
the first 4 overloads, but we'll improve that over time.
llvm-svn: 105815
|
|
|
|
|
|
| |
select either the default Itanium ABI or the new, experimental Microsoft ABI.
llvm-svn: 105804
|
|
|
|
|
|
| |
__USER_LABEL_PREFIX__.
llvm-svn: 105771
|
|
|
|
|
|
| |
__StaticInit section.
llvm-svn: 105650
|
|
|
|
|
|
| |
scattered throughout the project Makefiles.
llvm-svn: 105638
|
|
|
|
|
|
| |
- This eliminates most dependencies on how Clang is installed relative to LLVM.
llvm-svn: 105637
|
|
|
|
| |
llvm-svn: 105500
|
|
|
|
| |
llvm-svn: 105116
|
|
|
|
| |
llvm-svn: 104990
|
|
|
|
|
|
|
|
|
|
|
|
| |
the x86-64 __va_list_tag with this attribute. The attribute causes the
affected type to behave like a fundamental type when considered by ADL.
(x86-64 is the only target we currently provide with a struct-based
__builtin_va_list)
Fixes PR6762.
llvm-svn: 104941
|
|
|
|
| |
llvm-svn: 104828
|
|
|
|
| |
llvm-svn: 104789
|
|
|
|
|
|
| |
Steven Watanabe!
llvm-svn: 104373
|
|
|
|
|
|
|
| |
than 127 groups so this was already failing given -fsigned-char. A subsequent
to commit to TableGen will generate shorts for the arrays themselves.
llvm-svn: 103703
|
|
|
|
|
|
|
| |
code into a MoveUpIncludeHierarchy helper, and use the helper to
fix a case involving macros which regressed from my recent patch.
llvm-svn: 103288
|
|
|
|
|
|
|
|
|
|
|
| |
to be algorithmically faster and avoid an std::map. This routine
basically boils down to finding the nearest common ancestor in a
tree, and we (implicitly) have information about nesting depth,
use it!
This wraps up rdar://7948633 - SourceManager::isBeforeInTranslationUnit has poor performance
llvm-svn: 103239
|
|
|
|
| |
llvm-svn: 103236
|