| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
llvm-svn: 175983
|
| |
|
|
|
|
| |
array type.
llvm-svn: 175982
|
| |
|
|
|
|
| |
builds.
llvm-svn: 175981
|
| |
|
|
|
|
|
| |
true when shouldOnlyCommute is false, so we can remove code that checks
otherwise.
llvm-svn: 175980
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
itself recursively with a new instruction that has not been finalized, in order
to determine whether to keep the instruction. On 'make check' and test-suite the
only cases where the recursive invocation made any transformations were simple
instruction commutations, so I am restricting the recursive invocation to do
only this.
The other cases wouldn't work correctly when updating LiveIntervals, since the
new instructions don't have slot indices and LiveIntervals hasn't yet been
updated. If the other transformations were actually triggering in any test case
it would be possible to support it with a lot of effort, but since they don't
it's not worth it.
llvm-svn: 175979
|
| |
|
|
|
|
|
|
| |
available the
full information about the macro (e.g if it was imported and where).
llvm-svn: 175978
|
| |
|
|
| |
llvm-svn: 175977
|
| |
|
|
|
|
|
|
|
|
|
|
| |
consumer
just using ASTConsumer::HandleCXXStaticMemberVarInstantiation(), don't pass it with
ASTConsumer::HandleTopLevelDecl.
ASTConsumer::HandleTopLevelDecl is intended for user-written top-level decls;
a consumer can treat an instantiated static data member however it wants of course.
llvm-svn: 175976
|
| |
|
|
|
|
| |
proper. Fixed this already a few days ago for slti.
llvm-svn: 175975
|
| |
|
|
|
|
|
| |
unless it was requested to with an optional parameter that defaults to false, so
we don't need to handle that case in TwoAddressInstructionPass.
llvm-svn: 175974
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In conditional expressions, if the condition is split over multiple
lines, also break before both operands.
This prevents formattings like:
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa ==
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa ? b : c;
Which are bad, because they suggestion incorrect operator precedence:
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa ==
(aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa ? b : c);
This lead to the discovery that the expression parser incorrectly
handled conditional operators and that it could also handle semicolons
(which in turn reduced the amount of special casing for for-loops). As a
side-effect, we can now apply the bin-packing configuration to the
sections of for-loops.
llvm-svn: 175973
|
| |
|
|
| |
llvm-svn: 175972
|
| |
|
|
| |
llvm-svn: 175971
|
| |
|
|
|
|
|
|
|
|
| |
After changing the way several value inheritance hierarchies (TypeLoc,
CFGelement, ProgramPoint and SVal) handle casting, this documentation describes
how 3rd party code may need to be updated to compile with the new APIs.
As suggested by Sean Silva on cfe-dev.
llvm-svn: 175970
|
| |
|
|
|
|
| |
Post commit code review feedback from Matt Beaumont-Gay on r174248.
llvm-svn: 175969
|
| |
|
|
|
|
|
| |
Testing shows that it's empty in >99% of the cases and I couldn't find a case
where it contained more than 2 elements.
llvm-svn: 175967
|
| |
|
|
|
|
| |
Move the cold virtual method getNameForDiagnostic out of line.
llvm-svn: 175966
|
| |
|
|
| |
llvm-svn: 175965
|
| |
|
|
| |
llvm-svn: 175964
|
| |
|
|
| |
llvm-svn: 175963
|
| |
|
|
|
|
| |
Fixes PR15115.
llvm-svn: 175962
|
| |
|
|
|
|
| |
MachineInstrs don't have a slot index.
llvm-svn: 175961
|
| |
|
|
|
|
|
|
| |
This fixes llvm.org/PR15061.
Before: virtual void f(int *)const;
After: virtual void f(int *) const;
llvm-svn: 175960
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also don't break in long include directives as that is not desired.
We can now format:
#include "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
#define LL_FORMAT "ll"
printf("aaaaa: %d, bbbbbbbbb: %" LL_FORMAT "d, cccccccc: %" LL_FORMAT
"d, ddddddddd: %" LL_FORMAT "d\n");
Before, this led to weird results.
llvm-svn: 175959
|
| |
|
|
|
|
| |
running ASCI_Purple/SMG2000 in the test-suite.
llvm-svn: 175957
|
| |
|
|
| |
llvm-svn: 175956
|
| |
|
|
|
|
|
|
| |
TwoAddressInstructionPass. The code in rescheduleMIBelowKill() is a bit tricky,
since multiple instructions need to be moved down, one-at-a-time, in reverse
order.
llvm-svn: 175955
|
| |
|
|
| |
llvm-svn: 175954
|
| |
|
|
|
|
| |
StackFrame assumes m_sc is additive, but m_sc can lose its target. So now the SymbolContext::Clear() method takes a bool that indicates if the target should be cleared. Modified all existing code to properly set the bool argument.
llvm-svn: 175953
|
| |
|
|
| |
llvm-svn: 175952
|
| |
|
|
| |
llvm-svn: 175951
|
| |
|
|
|
|
| |
macros.The rest is some small misc. stuff.
llvm-svn: 175950
|
| |
|
|
|
|
| |
really simple cases) pointer arithmetic. This augments the existing bounds checking with language-level array bounds information.
llvm-svn: 175949
|
| |
|
|
| |
llvm-svn: 175948
|
| |
|
|
|
|
| |
in the gdb-remote Process plugin files.
llvm-svn: 175947
|
| |
|
|
| |
llvm-svn: 175946
|
| |
|
|
|
|
| |
expectedFailureClang take the bugnumber
llvm-svn: 175945
|
| |
|
|
| |
llvm-svn: 175944
|
| |
|
|
|
|
| |
rdar://12399248
llvm-svn: 175943
|
| |
|
|
|
|
|
|
| |
The decorators @expectedFailure (plain and special-case like i386, clang, ...) are modified to optionally take a bugnumber argument
If such an argument is specified, the failure report (or unexpected success report) will include the information passed in as part of the message
This is mostly useful for associating failures to issue IDs in issue management systems (e.g. the LLVM bugzilla)
llvm-svn: 175942
|
| |
|
|
| |
llvm-svn: 175941
|
| |
|
|
|
|
|
|
| |
Handle an implied 'sp' operand.
rdar://11466783
llvm-svn: 175940
|
| |
|
|
|
|
| |
rdar://13273675.
llvm-svn: 175939
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Use Optional<CFG*> where invalid states were needed previously. In the one case
where that's not possible (beginAutomaticObjDtorsInsert) just use a dummy
CFGAutomaticObjDtor.
Thanks for the help from Jordan Rose & discussion/feedback from Ted Kremenek
and Doug Gregor.
Post commit code review feedback on r175796 by Ted Kremenek.
llvm-svn: 175938
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Weather we should give C language linkage to functions and variables with
internal linkage probably depends on how much code assumes it. The standard
says they should have no language linkage, but gcc and msvc assign them
C language linkage.
This commit removes the hack that was preventing the mangling on static
functions declare in extern C contexts. It is an experiment to see if we
can implement the rules in the standard.
If it turns out that many users depend on these functions and variables
having C language linkage, we should change isExternC instead and try
to convince the CWG to change the standard.
llvm-svn: 175937
|
| |
|
|
| |
llvm-svn: 175936
|
| |
|
|
|
|
|
|
|
| |
and through to the debug info in the module. In order to make the
testcase a bit more efficient allow the filename to go through
compilation for compile and not assemble jobs and turn off the
extract for cases where we don't create an object.
llvm-svn: 175935
|
| |
|
|
|
|
| |
update testcase accordingly to give the correct name to the cu.
llvm-svn: 175934
|
| |
|
|
|
|
|
| |
the debug info for -gsplit-dwarf so we can encode that location
in the skeleton cu.
llvm-svn: 175933
|
| |
|
|
| |
llvm-svn: 175932
|