| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
llvm-svn: 166375
|
| |
|
|
|
|
|
|
| |
ConstantFoldInstOperands and crash.
Have to refactor the ConstantFolder interface one day to define bugs like this away. Fixes PR14131.
llvm-svn: 166374
|
| |
|
|
|
|
| |
literal-operator-id.
llvm-svn: 166373
|
| |
|
|
|
|
|
|
|
|
|
|
| |
since it also has an implicit exception specification. Downgrade the error to
an extwarn, since at least for operator delete, system headers like to declare
it as 'noexcept' whereas the implicit definition does not have an explicit
exception specification. Move the exception specification for user-declared
'operator delete' functions from the type-as-written into the type, to reflect
reality and to allow us to detect whether there was an implicit exception spec
or not.
llvm-svn: 166372
|
| |
|
|
|
|
|
|
|
| |
A[B[i]]+=x.
If the pointer is consecutive then it is safe to read and write. If the pointer is non-loop-consecutive then
it is unsafe to vectorize it because we may hit an ordering issue.
llvm-svn: 166371
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Xcode 4.5 passes -Wno-arc-abi to clang, which makes a clang newer than
r163917 warn that it doesn't understand -Wno-arc-abi. I asked if adding
this is ok at
http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20121015/066433.html
and nobody objected.
Adding this makes life a bit easier for the chromium project. If you think
this is a burden on for clang, shout, and I'll revert this.
llvm-svn: 166370
|
| |
|
|
| |
llvm-svn: 166369
|
| |
|
|
|
|
|
|
| |
to be printed truncated.
<rdar://problem/12389615>
llvm-svn: 166368
|
| |
|
|
| |
llvm-svn: 166367
|
| |
|
|
|
|
| |
change.
llvm-svn: 166366
|
| |
|
|
|
|
|
| |
the header file.
(followup patch to Sean's commit of r166355 earlier today.)
llvm-svn: 166365
|
| |
|
|
| |
llvm-svn: 166364
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is actually required by the C++ standard in
[basic.stc.dynamic.allocation]p3:
If an allocation function declared with a non-throwing
exception-specification fails to allocate storage, it shall return a
null pointer. Any other allocation function that fails to allocate
storage shall indicate failure only by throwing an exception of a type
that would match a handler of type std::bad_alloc.
We don't bother checking for the specific exception type, but just go off
the operator new prototype. This should help with a certain class of lazy
initalization false positives.
<rdar://problem/12115221>
llvm-svn: 166363
|
| |
|
|
| |
llvm-svn: 166362
|
| |
|
|
|
|
|
|
|
| |
initialized by a reference constant expression.
Our odr-use modeling still needs work here: we don't yet implement the 'set of
potential results of an expression' DR.
llvm-svn: 166361
|
| |
|
|
|
|
| |
No functional change intended.
llvm-svn: 166360
|
| |
|
|
|
|
|
|
|
|
| |
macro expansion ranges, make sure to check all the FileID
entries that are contained in the spelling range of the
expansion for the macro argument.
Fixes rdar://12537982
llvm-svn: 166359
|
| |
|
|
| |
llvm-svn: 166358
|
| |
|
|
|
|
| |
inline assembly. Also make sure the remove the ignored statements from the IR.
llvm-svn: 166357
|
| |
|
|
|
|
| |
and attaching APIs.
llvm-svn: 166356
|
| |
|
|
|
|
|
|
|
|
| |
- Fixed a crash when the executable module
couldn't be found.
- Fixed a problem that made it impossible
to attach to processes in the simulator
using the SBTarget::Attach.
llvm-svn: 166355
|
| |
|
|
| |
llvm-svn: 166354
|
| |
|
|
| |
llvm-svn: 166353
|
| |
|
|
| |
llvm-svn: 166352
|
| |
|
|
|
|
|
|
|
| |
For example:
for (i=0; i<n; i++)
sum += A[i] + B[i] + i;
llvm-svn: 166351
|
| |
|
|
|
|
|
|
| |
(The change at Clang side was committed in r166345)
2. Cosmetic change in order to conform to coding standards.
llvm-svn: 166350
|
| |
|
|
| |
llvm-svn: 166349
|
| |
|
|
| |
llvm-svn: 166348
|
| |
|
|
| |
llvm-svn: 166347
|
| |
|
|
|
|
|
|
|
|
| |
Added commands to the KDP plug-in that allow sending raw commands through the KDP protocol. You specify a command byte and a payload as ASCII hex bytes, and the packet is created with a valid header/sequenceID/length and sent. The command responds with a raw ASCII hex string that contains all bytes in the reply including the header.
An example of sending a read register packet for the GPR on x86_64:
(lldb) process plugin packet send --command 0x07 --payload 0100000004000000
llvm-svn: 166346
|
| |
|
|
| |
llvm-svn: 166345
|
| |
|
|
| |
llvm-svn: 166344
|
| |
|
|
| |
llvm-svn: 166343
|
| |
|
|
|
|
|
| |
Currently, it is enabled only if option "enable-mips-tail-calls" is given and
all of the callee's arguments are passed in registers.
llvm-svn: 166342
|
| |
|
|
| |
llvm-svn: 166341
|
| |
|
|
| |
llvm-svn: 166340
|
| |
|
|
| |
llvm-svn: 166339
|
| |
|
|
| |
llvm-svn: 166338
|
| |
|
|
| |
llvm-svn: 166337
|
| |
|
|
| |
llvm-svn: 166318
|
| |
|
|
| |
llvm-svn: 166317
|
| |
|
|
|
|
|
| |
a memory operand. Retain this information and then add the sizing directives
to the IR. This allows the backend to do proper instruction selection.
llvm-svn: 166316
|
| |
|
|
|
|
|
|
|
| |
"load-kexts" instead of "disable-kext-loading" since the value is a boolean. This was requested by the person who requested the feature. It now defaults to true:
(lldb) settings show plugin.dynamic-loader.darwin-kernel.load-kexts
plugin.dynamic-loader.darwin-kernel.load-kexts (boolean) = true
llvm-svn: 166315
|
| |
|
|
| |
llvm-svn: 166314
|
| |
|
|
|
|
|
|
| |
input is zero.
Fixes PR13028.
llvm-svn: 166313
|
| |
|
|
| |
llvm-svn: 166312
|
| |
|
|
|
|
| |
Grzegorz Jablonski.
llvm-svn: 166311
|
| |
|
|
| |
llvm-svn: 166310
|
| |
|
|
|
|
| |
--> DataLayout changes.
llvm-svn: 166309
|
| |
|
|
| |
llvm-svn: 166308
|