| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Added checks for regs which should not be 15.
rdar://problem/9237734
llvm-svn: 128945
|
|
|
|
| |
llvm-svn: 128944
|
|
|
|
|
|
| |
still used by RegionInfo :(
llvm-svn: 128943
|
|
|
|
|
|
|
|
| |
classified div.
It would be better to browse without stylesheet. (eg. on ViewVC)
llvm-svn: 128942
|
|
|
|
|
|
|
|
|
| |
For register-controlled shifts, we should check that the encoding constraint
Inst{7} = 0 and Inst{4} = 1 is satisfied.
rdar://problem/9237693
llvm-svn: 128941
|
|
|
|
|
|
| |
doing the expansion earlier (using a custom inserter) to allow for the chance of predicating these instructions.
llvm-svn: 128940
|
|
|
|
|
|
| |
consistent and also to lighten up the page a bit.
llvm-svn: 128939
|
|
|
|
| |
llvm-svn: 128938
|
|
|
|
|
|
|
| |
targets) when load/store results in multiple instructions.
// rdar://8808439
llvm-svn: 128937
|
|
|
|
|
|
| |
coalescing is now universal.
llvm-svn: 128936
|
|
|
|
| |
llvm-svn: 128935
|
|
|
|
| |
llvm-svn: 128934
|
|
|
|
| |
llvm-svn: 128933
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
marked explicitly as uninitialized through direct self initialization:
int x = x;
With r128894 we prevented warnings about this code, and this patch
teaches the analysis engine to continue analyzing subsequent uses of
'x'. This should wrap up PR9624.
There is still an open question of whether we should suppress the
maybe-uninitialized warnings resulting from variables initialized in
this fashion. The definitely-uninitialized uses should always be warned.
llvm-svn: 128932
|
|
|
|
| |
llvm-svn: 128929
|
|
|
|
| |
llvm-svn: 128928
|
|
|
|
| |
llvm-svn: 128927
|
|
|
|
|
|
| |
of a basic block.
llvm-svn: 128925
|
|
|
|
| |
llvm-svn: 128924
|
|
|
|
| |
llvm-svn: 128923
|
|
|
|
|
|
|
|
| |
Modify DisassembleCoprocessor() of ARMDisassemblerCore.cpp to react to the change.
rdar://problem/9236873
llvm-svn: 128922
|
|
|
|
| |
llvm-svn: 128921
|
|
|
|
| |
llvm-svn: 128920
|
|
|
|
| |
llvm-svn: 128919
|
|
|
|
|
|
|
|
| |
def into the remaining use.
Rematerialization can leave single-use loads behind that we might as well fold whenever possible.
llvm-svn: 128918
|
|
|
|
|
|
| |
callback functions.
llvm-svn: 128917
|
|
|
|
|
|
|
|
| |
generate a warning any time the strcat() function is used with a note suggesting to use a function which provides bounded buffers. CWE-119.
Also, brings the security syntax checker more inline with coding standards.
llvm-svn: 128916
|
|
|
|
| |
llvm-svn: 128915
|
|
|
|
| |
llvm-svn: 128914
|
|
|
|
| |
llvm-svn: 128913
|
|
|
|
| |
llvm-svn: 128912
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
developers can see if their driver changed any cl::Option's. The
current implementation isn't perfect but handles most kinds of
options. This is nice to have when decomposing the stages of
compilation and moving between different drivers. It's also a good
sanity check when comparing results produced by different command line
invocations that are expected to produce the comparable results.
Note: This is not an attempt to prolong the life of cl::Option. On the
contrary, it's a placeholder for a feature that must exist when
cl::Option is replaced by a more appropriate framework. A new
framework needs: a central option registry, dynamic name lookup,
non-global containers of option values (e.g. per-module,
per-function), *and* the ability to print options values and their defaults at
any point during compilation.
llvm-svn: 128911
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
developers can see if their driver changed any cl::Option's. The
current implementation isn't perfect but handles most kinds of
options. This is nice to have when decomposing the stages of
compilation and moving between different drivers. It's also a good
sanity check when comparing results produced by different command line
invocations that are expected to produce the comparable results.
Note: This is not an attempt to prolong the life of cl::Option. On the
contrary, it's a placeholder for a feature that must exist when
cl::Option is replaced by a more appropriate framework. A new
framework needs: a central option registry, dynamic name lookup,
non-global containers of option values (e.g. per-module,
per-function), *and* the ability to print options values and their defaults at
any point during compilation.
llvm-svn: 128910
|
|
|
|
| |
llvm-svn: 128909
|
|
|
|
| |
llvm-svn: 128908
|
|
|
|
|
|
| |
usable/possible.
llvm-svn: 128907
|
|
|
|
| |
llvm-svn: 128906
|
|
|
|
| |
llvm-svn: 128905
|
|
|
|
|
|
|
|
|
|
| |
getEDInfo(), in which case this code would dereference
NULL. EDInst can already handle NULL info, so avoid
the dereference and pass NULL through.
Reviewed by Sean Callanan
llvm-svn: 128904
|
|
|
|
|
|
| |
Finish what r128736 started.
llvm-svn: 128903
|
|
|
|
| |
llvm-svn: 128902
|
|
|
|
|
|
|
|
| |
function more clear and obvious in behavior.
Add some comments documenting the behavior of the primary diagnostic helper.
llvm-svn: 128901
|
|
|
|
|
|
|
| |
diagnostic emission. The fixit hint, when suggested, typically has
nothing to do with the nature or form of the reference.
llvm-svn: 128899
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
extracts a function to handle the emission of the diagnostic separately
from the walking over the set of uninitialized uses.
Also updates the naming used within this extracted function to be a bit
more consistent with the rest of Clang's naming patterns.
The next step will be breaking this apart so that we can go through
different functions rather than tracking so many boolean variables.
llvm-svn: 128898
|
|
|
|
|
|
|
|
|
|
| |
An alternative syntax is available for a modified immediate constant that permits the programmer to specify
the encoding directly. In this syntax, #<const> is instead written as #<byte>,#<rot>, where:
<byte> is the numeric value of abcdefgh, in the range 0-255
<rot> is twice the numeric value of rotation, an even number in the range 0-30.
llvm-svn: 128897
|
|
|
|
| |
llvm-svn: 128896
|
|
|
|
|
|
|
|
|
| |
if dLo == 15 || dHi == 15 || n == 15 || m == 15 then UNPREDICTABLE;
if dHi == dLo then UNPREDICTABLE;
rdar://problem/9230202
llvm-svn: 128895
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
int x = x;
GCC disables its warnings on this construct as a way of indicating that
the programmer intentionally wants the variable to be uninitialized.
Only the warning on the initializer is turned off in this iteration.
This makes the code a lot more ugly, but starts commenting the
surprising behavior here. This is a WIP, I want to refactor it
substantially for clarity, and to determine whether subsequent warnings
should be suppressed or not.
llvm-svn: 128894
|
|
|
|
| |
llvm-svn: 128893
|
|
|
|
|
|
| |
ADC/ABC with the appropriate S-bit input value.
llvm-svn: 128892
|