| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
|
| |
PPC ISA 2.06 (P7, A2, etc.) has a popcntd instruction. Add this instruction and
tell TTI about it so that popcount-loop recognition will know about it.
llvm-svn: 178233
|
| |
|
|
|
|
| |
toolchain flags for MIPS targets.
llvm-svn: 178232
|
| |
|
|
| |
llvm-svn: 178231
|
| |
|
|
| |
llvm-svn: 178230
|
| |
|
|
|
|
| |
Add a test for r178158.
llvm-svn: 178229
|
| |
|
|
|
|
| |
(inlined memcpy is not instrumented)
llvm-svn: 178228
|
| |
|
|
|
|
|
|
| |
gcc provides -mmfcrf and -mno-mfcrf for controlling what we call
the mfocrf target feature. Also, PPC is now making use of the
static function AddTargetFeature used by the Mips Driver code.
llvm-svn: 178227
|
| |
|
|
| |
llvm-svn: 178226
|
| |
|
|
|
|
| |
This has broken buildbots for a few hours.
llvm-svn: 178223
|
| |
|
|
|
|
|
|
| |
This reverts commit c8d65364223a04b179958a50a4bf0f89b21dd7d2.
This broke a bunch of the buildbots.
llvm-svn: 178222
|
| |
|
|
|
|
| |
don't support JIT.
llvm-svn: 178221
|
| |
|
|
|
|
|
|
| |
There were a few places where kill flags were not being set correctly, and
where 32-bit instruction variants were being used with 64-bit registers. After
r178180, this code was being triggered causing llc to assert.
llvm-svn: 178220
|
| |
|
|
| |
llvm-svn: 178219
|
| |
|
|
|
|
|
| |
typedef. Also don't warn on the _Atomic type specifier, just on the _Atomic
type qualifier.
llvm-svn: 178218
|
| |
|
|
|
|
| |
type qualifier.
llvm-svn: 178217
|
| |
|
|
| |
llvm-svn: 178216
|
| |
|
|
|
|
|
|
|
| |
This reverts commit 342d92c7a0adeabc9ab00f3f0d88d739fe7da4c7.
Turns out we're going with a different schema design to represent
DW_TAG_imported_modules so we won't need this extra field.
llvm-svn: 178215
|
| |
|
|
| |
llvm-svn: 178214
|
| |
|
|
|
|
|
|
|
| |
This reverts commit 5035c483b7fcbf0fa2a7afba24fa35a10995d195.
This schema change wasn't necessary after all. I'm going ith a different
solution that will hopefully use space more conservatively.
llvm-svn: 178213
|
| |
|
|
|
|
| |
Introduced in r178207
llvm-svn: 178212
|
| |
|
|
| |
llvm-svn: 178211
|
| |
|
|
|
|
| |
sugar for the _Atomic type specifier.
llvm-svn: 178210
|
| |
|
|
|
|
|
|
| |
- the ".app" would be treated as the app bundle final characters
and the SpringBoard launch would fail.
<rdar://problem/13258935>
llvm-svn: 178209
|
| |
|
|
| |
llvm-svn: 178208
|
| |
|
|
| |
llvm-svn: 178207
|
| |
|
|
|
|
|
| |
Holding the Python lock while we call the Python C API to post-process objects returned from the OS plugins
This should avoid issues where some Python objects get invalidated while we are in the middle of processing them and we end up with an invalid Python state and a crash
llvm-svn: 178206
|
| |
|
|
|
|
|
|
|
|
| |
us to think we can't even get the
frame at index 0. We should ALWAYS be able to get that.
<rdar://problem/13497571>
llvm-svn: 178205
|
| |
|
|
| |
llvm-svn: 178204
|
| |
|
|
|
|
| |
ThreadPlanCallFunction isn't valid.
llvm-svn: 178203
|
| |
|
|
|
|
| |
<rdar://problem/13485541>
llvm-svn: 178202
|
| |
|
|
|
|
| |
made for some reason.
llvm-svn: 178201
|
| |
|
|
|
|
|
|
|
| |
each of which was only present in one version:
* Give the right diagnostic for 'restrict' applied to a non-pointer, non-reference type.
* Don't reject 'restrict' applied indirectly to an Objective-C object pointer type (eg, through template instantiation).
llvm-svn: 178200
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When we are consuming the current token just to enter a new token stream, we push
the current token in the back of the stream so that we get it again.
Unfortunately this had the effect where if the current token is a code-completion one,
we would code-complete once during consuming it and another time after the stream ended.
Fix this by making sure that, in this case, ConsumeAnyToken() will consume a code-completion
token without invoking code-completion.
rdar://12842503
llvm-svn: 178199
|
| |
|
|
|
|
| |
a pointer or reference type.
llvm-svn: 178198
|
| |
|
|
| |
llvm-svn: 178196
|
| |
|
|
|
|
| |
conversion between floating-point types.
llvm-svn: 178195
|
| |
|
|
|
|
| |
far from clear whether these have undefined behavior, and these checks are helping no-one. Keep the double->float overflow warnings, though, since those are useful in practice, even though it's unclear whether such operations have defined behavior.
llvm-svn: 178194
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
form of call in preference to memory indirect on Atom.
In this case, the patch applies the optimization to the code for reloading
spilled registers.
The patch also includes changes to sibcall.ll and movgs.ll, which were
failing on the Atom buildbot after the first patch was applied.
This patch by Sriram Murali.
llvm-svn: 178193
|
| |
|
|
|
|
| |
generating spurious over-completion warning flags
llvm-svn: 178192
|
| |
|
|
|
|
|
|
| |
LLDB is crashing when logging is enabled from lldb-perf-clang. This has to do with the global destructor chain as the process and its threads are being torn down.
All logging channels now make one and only one instance that is kept in a global pointer which is never freed. This guarantees that logging can correctly continue as the process tears itself down.
llvm-svn: 178191
|
| |
|
|
|
|
|
|
| |
Made sure we were looking a correct section
Added Mips32/64 as an extra check
Updated llvm-objdump to generate symbolic info for Mips relocations
llvm-svn: 178190
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
With this notion, if parties outside the ScriptInterpreter itself need to acquire a lock on script APIs, they can do so by a pattern like this:
{
auto lock = interpeter->AcquireInterpreterLock();
// do whatever you need to do...
} // lock will automatically be released here
This might be useful for classes that use the Python convenience objects (e.g. PythonDictionary) to ensure they keep the underlying interpreter in a safe and controlled condition while they call through the C API functions
Of course, the ScriptInterpreter still manages its internal locking correctly when necessary :-)
llvm-svn: 178189
|
| |
|
|
| |
llvm-svn: 178188
|
| |
|
|
| |
llvm-svn: 178187
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
expression. Specifically, this syntax:
ImmDisp [ BaseReg + Scale*IndexReg + Disp ]
We don't currently support:
ImmDisp [ Symbol ]
rdar://13518671
llvm-svn: 178186
|
| |
|
|
| |
llvm-svn: 178184
|
| |
|
|
|
|
| |
front. Removed some trailing spaces.
llvm-svn: 178182
|
| |
|
|
|
|
|
|
|
| |
Per feedback by Doug, we should avoid platform-specific implementations
in lib/Headers as much as possible.
This reverts commit r178110.
llvm-svn: 178181
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
PPCInstrInfo
These functions should have the same list of load/store instructions. Now that
all load/store forms have been normalized (to single instructions or pseudos)
they can be resynchronized.
Found by inspection, although hopefully this will improve optimization. I've
also added some comments.
llvm-svn: 178180
|
| |
|
|
|
|
|
| |
is accessing 'isa' as an object pointer.
// rdar://13503456. FixIt to follow in another patch.
llvm-svn: 178179
|