- Jan 19, 2015
-
-
Colin LeMahieu authored
llvm-svn: 226478
-
Vince Harron authored
This patch fixes a bug that prevented all gtest output from being displayed. Submitted for Tamas Berghammer llvm-svn: 226477
-
Adrian Prantl authored
frontends to use a DIExpression with a DW_OP_deref instead. This is not only a much more natural place for this informationl; there is also a technical reason: The FlagIndirectVariable is used to mark a variable that is turned into a reference by virtue of the calling convention; this happens for example to aggregate return values. The inliner, for example, may actually need to undo this indirection to correctly represent the value in its new context. This is impossible to implement because the DIVariable can't be safely modified. We can however safely construct a new DIExpression on the fly. llvm-svn: 226476
-
Adrian Prantl authored
with a DW_OP_deref instead. llvm-svn: 226474
-
Greg Fitzgerald authored
Original patch by Luke Iannini. Minor improvements and test added by Erik de Castro Lopo. Differential Revision: http://reviews.llvm.org/D6877 From: Erik de Castro Lopo <erikd@mega-nerd.com> llvm-svn: 226473
-
Colin LeMahieu authored
llvm-svn: 226472
-
Vince Harron authored
llvm-svn: 226471
-
Rafael Espindola authored
An assignment will produce a symbol with a given section and offset. There is no way to represent something like "1 byte after a common symbol". This matches the behavior of GNU as. Part of PR22217. llvm-svn: 226470
-
Bradley Smith authored
[ARM] SSAT/USAT with an 'asr #32' shift should result in an undefined encoding rather than unpredictable llvm-svn: 226469
-
Bradley Smith authored
llvm-svn: 226468
-
Rafael Espindola authored
No change in this commit, but clang was changed to also produce trivial comdats when needed. Original message: Don't create new comdats in CodeGen. This patch stops the implicit creation of comdats during codegen. Clang now sets the comdat explicitly when it is required. With this patch clang and gcc now produce the same result in pr19848. llvm-svn: 226467
-
Dmitry Vyukov authored
TSAN_SHADOW_COUNT is defined to 4 in all environments. Other values of TSAN_SHADOW_COUNT were never tested and were broken by recent changes to shadow mapping. Remove it as there is no reason to fix nor maintain it. llvm-svn: 226466
-
Rafael Espindola authored
llvm-svn: 226465
-
Andrey Churbanov authored
llvm-svn: 226464
-
Rafael Espindola authored
llvm-svn: 226463
-
Viktor Kutuzov authored
Committed unreviewed with permission. llvm-svn: 226462
-
Viktor Kutuzov authored
Differential Revision: http://reviews.llvm.org/D7051 llvm-svn: 226461
-
Chandler Carruth authored
from an API in the process of preparing for the new pass manager. llvm-svn: 226460
-
Chandler Carruth authored
and updated. This may appear to remove handling for things like alias analysis when splitting critical edges here, but in fact no callers of SplitEdge relied on this. Similarly, all of them wanted to preserve LCSSA if there was any update of the loop info. That makes the interface much simpler. With this, all of BasicBlockUtils.h is free of Pass arguments and prepared for the new pass manager. This is tho majority of utilities that relied on pass arguments. llvm-svn: 226459
-
Evgeniy Stepanov authored
Print a warning at verbosity=1 and higher instead of dying immediately. llvm-svn: 226458
-
Chandler Carruth authored
while refactoring this API for the new pass manager. No functionality changed here, the code didn't actually support this option. llvm-svn: 226457
-
Chandler Carruth authored
APIs and replace it and numerous booleans with an option struct. The critical edge splitting API has a really large surface of flags and so it seems worth burning a small option struct / builder. This struct can be constructed with the various preserved analyses and then flags can be flipped in a builder style. The various users are now responsible for directly passing along their analysis information. This should be enough for the critical edge splitting to work cleanly with the new pass manager as well. This API is still pretty crufty and could be cleaned up a lot, but I've focused on this change just threading an option struct rather than a pass through the API. llvm-svn: 226456
-
Sergey Dmitrouk authored
It became invalid after signature changes. llvm-svn: 226455
-
Daniel Jasper authored
Crashing input: /\ / comment llvm-svn: 226454
-
Evgeniy Stepanov authored
InternalAlloc is quite complex and its behavior may depend on the values of flags. As such, it should not be used while parsing flags. Sadly, LowLevelAlloc does not support deallocation of memory. llvm-svn: 226453
-
Evgeniy Stepanov authored
llvm-svn: 226452
-
Daniel Jasper authored
Previously crashing input: void f( #if A ); #else #endif llvm-svn: 226451
-
Daniel Jasper authored
Input "a<," made clang-format crash. llvm-svn: 226450
-
Daniel Jasper authored
llvm-svn: 226449
-
Daniel Jasper authored
llvm-svn: 226448
-
Daniel Jasper authored
llvm-svn: 226447
-
Daniel Jasper authored
This assert would trigger on: #d , = } llvm-svn: 226446
-
Manuel Klimek authored
Emacs functions by default use character positions; convert characters to offsets when handing parameters to clang-format and convert byte offsets we get from clang-format back to character positions. Reworked the code a bit so the 0-based to 1-based offset calculations are done in the same place where we do the multi-byte to offset mapping. llvm-svn: 226445
-
Chandler Carruth authored
test. Do that after we suppress the warnings for unknown pragmas as this warning flag is quite new in Clang and so old Clang's would warn all the time on this file. llvm-svn: 226444
-
Chandler Carruth authored
we can while splitting critical edges. The only code which called this and didn't require simplified loops to be preserved is polly, and the code behaves correctly there anyways. Without this change, it becomes really hard to share this code with the new pass manager where things like preserving loop simplify form don't make any sense. If anyone discovers this code behaving incorrectly, what it *should* be testing for is whether the loops it needs to be in simplified form are in fact in that form. It should always be trying to preserve that form when it exists. llvm-svn: 226443
-
David Majnemer authored
It shouldn't have been removed, the code which replaced it didn't cover this case. llvm-svn: 226442
-
NAKAMURA Takumi authored
llvm-svn: 226441
-
Viktor Kutuzov authored
Differential Revision: http://reviews.llvm.org/D6892 llvm-svn: 226440
-
Erik Eckstein authored
In case of blocks with many memory-accessing instructions, alias checking can take lot of time (because calculating the memory dependencies has quadratic complexity). I chose a limit which resulted in no changes when running the benchmarks. llvm-svn: 226439
-
Evgeniy Stepanov authored
And handle help=1 in standalone LSan. llvm-svn: 226438
-