| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
llvm-svn: 157491
|
| |
|
|
|
|
|
|
| |
entity imported by the ASTImporter had a NamedDecl
with a name that wasn't a plain string (e.g., a
selector).
llvm-svn: 157488
|
| |
|
|
|
|
| |
LC_ENCRYPTION_INFO with "cryptid == 0" is not actually encrypted and LLDB fails to read memory from file.
llvm-svn: 157487
|
| |
|
|
|
|
| |
method template.
llvm-svn: 157486
|
| |
|
|
|
|
| |
NV_CONTRIB
llvm-svn: 157485
|
| |
|
|
|
|
| |
Reading memory from a file when the section is encrypted doesn't show an error. No we do.
llvm-svn: 157484
|
| |
|
|
| |
llvm-svn: 157483
|
| |
|
|
|
|
| |
a mach file from memory even though we have a process. So now we don't read the string table strings from memory when we don't have to.
llvm-svn: 157482
|
| |
|
|
|
|
|
| |
add support for select
add experimental support for alloc_size metadata
llvm-svn: 157481
|
| |
|
|
|
|
| |
function template.
llvm-svn: 157480
|
| |
|
|
|
|
|
|
|
|
| |
to pass around a struct instead of a large set of individual values. This
cleans up the interface and allows more information to be added to the struct
for future targets without requiring changes to each and every target.
NV_CONTRIB
llvm-svn: 157479
|
| |
|
|
| |
llvm-svn: 157478
|
| |
|
|
| |
llvm-svn: 157477
|
| |
|
|
| |
llvm-svn: 157476
|
| |
|
|
|
|
| |
the visibility.
llvm-svn: 157475
|
| |
|
|
|
|
| |
msvc-incompatible. (compatible to mingw32 and netbsd, though)
llvm-svn: 157474
|
| |
|
|
| |
llvm-svn: 157473
|
| |
|
|
|
|
|
| |
When the flag is set to zero, we do not check for errors in malloc_usable_size.
This may be useful to work around a bug in Nvidia drivers prior to 295.*
llvm-svn: 157472
|
| |
|
|
|
|
| |
stack-align=8, eg. win32 and netbsd.
llvm-svn: 157471
|
| |
|
|
|
|
|
| |
Similar fixes for function and member template to follow as I write the
testcases.
llvm-svn: 157470
|
| |
|
|
| |
llvm-svn: 157469
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
with arbitrary topologies (previously it would give up when hitting a diamond
in the use graph for example). The testcase from PR12764 is now reduced from
a pile of additions to the optimal 1617*%x0+208. In doing this I changed the
previous strategy of dropping all uses for expression leaves to one of dropping
all but one use. This works out more neatly (but required a bunch of tweaks)
and is also safer: some recently fixed bugs during recursive linearization were
because the linearization code thinks it completely owns a node if it has no uses
outside the expression it is linearizing. But if the node was also in another
expression that had been linearized (and thus all uses of the node from that
expression dropped) then the conclusion that it is completely owned by the
expression currently being linearized is wrong. Keeping one use from within each
linearized expression avoids this kind of mistake.
llvm-svn: 157467
|
| |
|
|
|
|
| |
recursion and crashes)
llvm-svn: 157466
|
| |
|
|
| |
llvm-svn: 157465
|
| |
|
|
|
|
| |
depending on -m32/-m64 addr2line says either e.g. __xsan_strnlen or just strnlen
llvm-svn: 157464
|
| |
|
|
| |
llvm-svn: 157462
|
| |
|
|
| |
llvm-svn: 157459
|
| |
|
|
|
|
|
|
|
|
|
| |
-Wsometimes-uninitialized. This detects cases where an explicitly-written branch
inevitably leads to an uninitialized variable use (so either the branch is dead
code or there is an uninitialized use bug).
This chunk of warnings tentatively lives within -Wuninitialized, in order to
give it more visibility to existing Clang users.
llvm-svn: 157458
|
| |
|
|
| |
llvm-svn: 157456
|
| |
|
|
| |
llvm-svn: 157455
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
these functions will end in the sequence
mov %rbp, %rsp
ret
call __stack_chk_fail
instead of the usual mov, ret. The x86 assembly profiler only looked
for functions ending in 'ret' and added the Unwind row describing how to
set the CFA based on that -- the addition of the call insn (which is jumped
to earlier in the function body) threw off that inspection.
Resolves the need to "step" twice to get out of these functions when doing
source-level stepping.
<rdar://problem/11469705>
llvm-svn: 157454
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Load custom plugins when running scan-build. This is useful when
additional static analysis Checkers must be provided via clang's plugin
interface.
Loading additional plugins can now be done via the scan-build call:
scan-build -load-plugin <plugin.so>
A patch by Thomas Hauth.
llvm-svn: 157452
|
| |
|
|
| |
llvm-svn: 157451
|
| |
|
|
| |
llvm-svn: 157450
|
| |
|
|
|
|
|
| |
Store (debugging) register names as offsets into a string table instead
of as char pointers.
llvm-svn: 157449
|
| |
|
|
|
|
| |
small bug in the process.
llvm-svn: 157446
|
| |
|
|
|
|
|
| |
if the value isn't an unsigned char or EOF behavior is undefined
(and on Windows there's an assertion)
llvm-svn: 157445
|
| |
|
|
|
|
| |
functional change.
llvm-svn: 157440
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Sending async packets can deadlock a program on darwin. We currently allow breakpoint packets and memory read/write packets (for software breakpoints) to be sent while a program is running. In the GDB remote plug-in, we will interrupt the run, send the async packet and resume (currently with the continue packet that caused the program to resume). If the GDB server supports the "vCont" packet, we might have initially continued with each thread stating it should continue. If new threads show up while we are stopped, which happend when running GCD, we can end up with new threads that we aren't mentioning in the continue list. So we start with a thread list of 1,2,3 and continue:
continue thread 1, continue thread 2, continue thread 3
Now we interrupt and set a breakpoint and we actually have threads 1,2,3,4 now when we are about to resume, yet we send:
continue thread 1, continue thread 2, continue thread 3
Any thread that isn't mentioned is currently going to stay suspended. This causes the deadlock.
llvm-svn: 157439
|
| |
|
|
| |
llvm-svn: 157438
|
| |
|
|
|
|
| |
(except the part about choosing direction)
llvm-svn: 157437
|
| |
|
|
| |
llvm-svn: 157436
|
| |
|
|
|
|
|
|
| |
backing two propeties because proprty names
match except for first letter being of different
case. // rdar://11528439, [PR12936].
llvm-svn: 157435
|
| |
|
|
| |
llvm-svn: 157434
|
| |
|
|
| |
llvm-svn: 157433
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Like this:
foreach i = 0-127 in ...
Use braces for composite ranges:
foreach i = {0-3,9-7} in ...
llvm-svn: 157432
|
| |
|
|
|
|
| |
Only fully expanded Records should go into RecordKeeper.
llvm-svn: 157431
|
| |
|
|
|
|
| |
Use static type checking.
llvm-svn: 157430
|
| |
|
|
| |
llvm-svn: 157429
|
| |
|
|
| |
llvm-svn: 157428
|