| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
the beginning and end of the range are in different macro arguments.
PR14399.
llvm-svn: 168984
|
| |
|
|
|
|
| |
functionality change.
llvm-svn: 168977
|
| |
|
|
|
|
|
|
|
|
|
|
| |
import of that module elsewhere, don't try to build the module again:
it won't work, and the experience is quite dreadful. We track this
information somewhat globally, shared among all of the related
CompilerInvocations used to build modules on-the-fly, so that a
particular Clang instance will only try to build a given module once.
Fixes <rdar://problem/12552849>.
llvm-svn: 168961
|
| |
|
|
| |
llvm-svn: 168959
|
| |
|
|
| |
llvm-svn: 168958
|
| |
|
|
| |
llvm-svn: 168956
|
| |
|
|
| |
llvm-svn: 168953
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
features of ASan:
1) init-order sanitizer: initialization-order checker.
Status: usable, but may produce false positives w/o proper blacklisting.
2) use-after-return sanitizer
Status: implemented, but heavily understed.
Should be optional, as it significanlty slows program down.
3) use-after-scope sanitizer
Status: in progress.
llvm-svn: 168950
|
| |
|
|
|
|
| |
before libstdc++ like we do with ubsan.
llvm-svn: 168918
|
| |
|
|
|
|
|
|
| |
Original commit message:
Remove redundant code.
llvm-svn: 168900
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Among other differences, GCC accepts
typedef int IA[];
typedef int A10[10];
static A10 *f(void);
static IA *f(void);
void g(void) {
(void)sizeof(*f());
}
but clang used to reject it with:
invalid application of 'sizeof' to an incomplete type 'IA' (aka 'int []')
The intention of c99's 6.2.7 seems to be that we should use the composite type
and accept as gcc does.
Doing the type merging required some extra fixes:
* Use the type from the function type in initializations, even if an parameter
is available.
* Fix the merging of the noreturn attribute in function types.
* Make CodeGen handle the fact that an parameter type can be different from
the corresponding type in the function type.
llvm-svn: 168895
|
| |
|
|
|
|
| |
mangling templates
llvm-svn: 168862
|
| |
|
|
|
|
|
| |
'getPointerWidth(0) >= 64' test to be a method on TargetInfo, ready to be
properly cleaned up.
llvm-svn: 168856
|
| |
|
|
| |
llvm-svn: 168855
|
| |
|
|
| |
llvm-svn: 168851
|
| |
|
|
|
|
|
|
|
|
|
| |
performed, to determine whether that special member is deleted or constexpr.
That overload resolution process can in turn trigger the instantiation of a
template, which can do anything, including triggering the declaration of that
very same special member function. When this happens, do not try to recursively
declare the special member -- that's impossible. Instead, only try to realise
the truth. There is no special member.
llvm-svn: 168847
|
| |
|
|
|
|
| |
<rdar://problem/12759044>.
llvm-svn: 168843
|
| |
|
|
|
|
| |
rdar://12771737
llvm-svn: 168841
|
| |
|
|
|
|
| |
appertains to a friend declaration, that declaration shall be a definition.
llvm-svn: 168826
|
| |
|
|
|
|
|
|
|
|
| |
in deciding a copy/dispose field is needed in a byref structure
and when generating the copy/dispose helpers. In certain
cases, these fields were being added but no copy/dispose was
being generated. This was uncovered in ARC, but not in MRR.
// rdar://12759433
llvm-svn: 168825
|
| |
|
|
|
|
| |
specifications.
llvm-svn: 168824
|
| |
|
|
|
|
|
| |
decayed to a pointer type. Patch by WenHan Gu, with a little tweaking and
additional testcases by me.
llvm-svn: 168822
|
| |
|
|
|
|
| |
rdar://12723368
llvm-svn: 168821
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the original parameter or return type.
Since we do not accurately represent the data fields of a union, we should not
directly load or store a union type.
As an exmple, if we have i8,i8, i32, i32 as one field type and i32,i32 as
another field type, the first field type will be chosen to represent the union.
If we load with the union's type, the 3rd byte and the 4th byte will be skipped.
rdar://12723368
llvm-svn: 168820
|
| |
|
|
|
|
|
|
|
| |
determine which member function would be the callee from within the template
definition, don't pass that function as a "non-member function" to
CreateOverloadedBinOp. Instead, just rely on it to select the member function
for itself.
llvm-svn: 168818
|
| |
|
|
|
|
| |
diagnostic for invalid sets of sanitizers
llvm-svn: 168794
|
| |
|
|
|
|
| |
Clang part.
llvm-svn: 168782
|
| |
|
|
| |
llvm-svn: 168778
|
| |
|
|
|
|
|
|
| |
string literal needs cleaning (because it contains line-splicing in the
encoding prefix or in the ud-suffix), do not clean the section between the
double-quotes -- that's the "raw" bit!
llvm-svn: 168776
|
| |
|
|
|
|
|
| |
constructor/assignment operator with a const-qualified parameter type. The
prior method for determining this incorrectly used overload resolution.
llvm-svn: 168775
|
| |
|
|
|
|
| |
generally by r168757.
llvm-svn: 168774
|
| |
|
|
|
|
|
|
|
|
|
| |
allocated using the allocator associated with an ASTContext.
Use this inside CXXRecordDecl::DefinitionData instead of an UnresolvedSet to
avoid a potential memory leak.
rdar://12761275
llvm-svn: 168771
|
| |
|
|
|
|
| |
expose only the iterators instead.
llvm-svn: 168770
|
| |
|
|
|
|
|
|
|
|
|
|
| |
a special member" diagnostic from warning to error, and fix the cases where it
produced diagnostics with incorrect wording.
We don't support this as an extension, and we ban it even in C++98 mode. This
breaks too much (for instance, the ABI-specified calling convention for a type
can change if it acquires a copy constructor through the addition of a default
argument).
llvm-svn: 168769
|
| |
|
|
|
|
|
|
|
|
|
| |
initializer.
The stop-gap here is to just drop such objects when processing the InitListExpr.
We still need a better solution.
Fixes <rdar://problem/12755044>.
llvm-svn: 168757
|
| |
|
|
|
|
|
| |
arc specific diagnostic on the selector. This is objc-arc
part of // rdar://11303469
llvm-svn: 168756
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This was also covered by <rdar://problem/12753384>. The static analyzer
evaluates a CXXConstructExpr within an initializer expression and
RegionStore doesn't know how to handle the resulting CXXTempObjectRegion
that gets created. We need a better solution than just dropping the
value, but we need to better understand how to implement the right
semantics here.
Thanks to Jordan for his help diagnosing the behavior here.
llvm-svn: 168741
|
| |
|
|
|
|
|
|
|
|
|
| |
objc_loadWeak. This retains and autorelease the weakly-refereced
object. This hidden autorelease sometimes makes __weak variable alive even
after the weak reference is erased, because the object is still referenced
by an autorelease pool. This patch overcomes this behavior by loading a
weak object via call to objc_loadWeakRetained(), followng it by objc_release
at appropriate place, thereby removing the hidden autorelease. // rdar://10849570
llvm-svn: 168740
|
| |
|
|
|
|
|
| |
r128056 moved PrettyStackTraceParserEntry construction from Parser.h
to ParseAST.cpp, so there's no need to keep this class in a header.
llvm-svn: 168731
|
| |
|
|
|
|
| |
by Olivier Goffart!
llvm-svn: 168726
|
| |
|
|
|
|
| |
add some assertions. No functionality change.
llvm-svn: 168725
|
| |
|
|
| |
llvm-svn: 168707
|
| |
|
|
|
|
| |
is not used in any #ifdef.
llvm-svn: 168703
|
| |
|
|
|
|
| |
Introduces new sanitizer "unsigned-integer-overflow".
llvm-svn: 168701
|
| |
|
|
| |
llvm-svn: 168674
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ELF ABI.
Complex values are to be passed in registers as though the real and
imaginary parts were passed as separate parameters. Prior to this
patch, complex values were passed as byval aggregates. It turns out
that specifying getDirect() for all complex types when classifying the
argument type results in the desired behavior.
The new Clang test case verifies that the correct LLVM IR is generated
for caller and callee for each of the underlying types for _Complex.
llvm-svn: 168673
|
| |
|
|
| |
llvm-svn: 168667
|
| |
|
|
|
|
| |
- This ensures we see the right buffer size for the file.
llvm-svn: 168636
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
syntactic locations around class specifiers.
This change list implemented logic that explicitly detects several combinations of locations where C++11 attribute
specifiers might be incorrectly placed within a class specifier. Previously we emit generic diagnostics like
"expected identifier" for such cases; now we emit specific diagnostic against the misplaced attributes, this also
fixed a bug in old code where attributes appear at legitimate locations were incorrectly rejected.
Thanks to Richard Smith for reviewing!
llvm-svn: 168626
|
| |
|
|
|
|
| |
I'm looking at ways to fix the relevant test so it can catch this sort of mistake.
llvm-svn: 168618
|