| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Differential revision: http://reviews.llvm.org/D15045
llvm-svn: 254393
|
| |
|
|
| |
llvm-svn: 254392
|
| |
|
|
|
|
|
|
|
|
| |
Reviewers: dblaikie, pcc
Subscribers: llvm-commits
Differential Revision: http://reviews.llvm.org/D15064
llvm-svn: 254391
|
| |
|
|
|
|
|
|
|
|
| |
Reviewers: dblaikie, pcc
Subscribers: llvm-commits
Differential Revision: http://reviews.llvm.org/D15063
llvm-svn: 254390
|
| |
|
|
|
|
| |
Use undefined instead of setzero as the pass through input since its going to be fully overwritten. Use cmpeq of two zero vectors to produce the all 1s vector. Casting -1 to a double and vectorizing causes a constant load of a -1.0 floating point value.
llvm-svn: 254389
|
| |
|
|
|
|
|
|
| |
memory on the left hand side of the fsub/fdiv operations in their patterns.
Not sure how to test this. I noticed by inspection in the isel tables where the same pattern tried to produce DIV and DIVR or SUB and SUBR.
llvm-svn: 254388
|
| |
|
|
| |
llvm-svn: 254387
|
| |
|
|
|
|
| |
types to size_t to match.
llvm-svn: 254386
|
| |
|
|
|
|
| |
manually. NFC
llvm-svn: 254385
|
| |
|
|
|
|
| |
and array size. NFC
llvm-svn: 254384
|
| |
|
|
| |
llvm-svn: 254383
|
| |
|
|
|
|
| |
Interestingly the original code may have had a bug because it was passing the byte size of a uint16_t array instead of the number of entries.
llvm-svn: 254382
|
| |
|
|
|
|
| |
size that I would have otherwise cconverted to array_lengthof. NFC
llvm-svn: 254381
|
| |
|
|
| |
llvm-svn: 254380
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
stepping on MIPS
This patch will clear bug 25194 - LLDB-Server Assertion raised when single stepping on MIPS. The problem was that while emulating instructions, old and new pc values would have garbage value in their upper 32 bits. Therefore checking if pc was changed (old_pc == new_pc) would always return false, because of which pc was not getting updated.
/* If we haven't changed the PC, change it here */
if (old_pc == new_pc)
{
new_pc += 4;
Context context;
return false;
}
Reviewers: tberghammer, clayborg
Subscribers: dsanders, lldb-commits, mohit.bhakkad, bhushan, jaydeep, nitesh.jain
Differential: http://reviews.llvm.org/D14633
llvm-svn: 254379
|
| |
|
|
|
|
| |
Reported by: David Blaikie
llvm-svn: 254378
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
interfaces, and update all uses of old interfaces.
(This is the second attempt to submit this patch. The first caused two assertion
failures and was reverted. See https://llvm.org/bugs/show_bug.cgi?id=25687)
The patch in http://reviews.llvm.org/D13745 is broken into four parts:
1. New interfaces without functional changes (http://reviews.llvm.org/D13908).
2. Use new interfaces in SelectionDAG, while in other passes treat probabilities
as weights (http://reviews.llvm.org/D14361).
3. Use new interfaces in all other passes.
4. Remove old interfaces.
This patch is 3+4 above. In this patch, MBB won't provide weight-based
interfaces any more, which are totally replaced by probability-based ones.
The interface addSuccessor() is redesigned so that the default probability is
unknown. We allow unknown probabilities but don't allow using it together
with known probabilities in successor list. That is to say, we either have a
list of successors with all known probabilities, or all unknown
probabilities. In the latter case, we assume each successor has 1/N
probability where N is the number of successors. An assertion checks if the
user is attempting to add a successor with the disallowed mixed use as stated
above. This can help us catch many misuses.
All uses of weight-based interfaces are now updated to use probability-based
ones.
Differential revision: http://reviews.llvm.org/D14973
llvm-svn: 254377
|
| |
|
|
|
|
|
|
|
|
|
| |
SUMMARY:
For MIPS, ARCH is specified without m.
Reviewers: clayborg
Subscribers: nitesh.jain, mohit.bhakkad, sagar, bhushan and lldb-commits
Differential Revision: http://reviews.llvm.org/D14978
llvm-svn: 254376
|
| |
|
|
| |
llvm-svn: 254375
|
| |
|
|
| |
llvm-svn: 254372
|
| |
|
|
|
|
|
| |
Nobody was checking the returnvalue of recede()/advance() so we can
simply replace this code with asserts.
llvm-svn: 254371
|
| |
|
|
| |
llvm-svn: 254370
|
| |
|
|
| |
llvm-svn: 254369
|
| |
|
|
|
|
|
| |
This is in preparation to expose the RegisterOperands class as
RegisterPressure API.
llvm-svn: 254368
|
| |
|
|
|
|
| |
Adds initial parsing and semantic analysis for 'taskloop' directive.
llvm-svn: 254367
|
| |
|
|
|
|
|
|
|
|
| |
probability-based interfaces, and update all uses of old interfaces."
and the follow-up r254356: "Fix a bug in MachineBlockPlacement that may cause assertion failure during BranchProbability construction."
Asserts were firing in Chromium builds. See PR25687.
llvm-svn: 254366
|
| |
|
|
|
|
| |
embedded file.
llvm-svn: 254365
|
| |
|
|
| |
llvm-svn: 254364
|
| |
|
|
| |
llvm-svn: 254363
|
| |
|
|
|
|
| |
Patch by Justin Lebar
llvm-svn: 254362
|
| |
|
|
| |
llvm-svn: 254361
|
| |
|
|
| |
llvm-svn: 254360
|
| |
|
|
|
|
|
| |
type changes when the initializer is attached). Don't hold onto the
GlobalVariable*; recompute it from the VarDecl* instead.
llvm-svn: 254359
|
| |
|
|
| |
llvm-svn: 254358
|
| |
|
|
| |
llvm-svn: 254357
|
| |
|
|
|
|
|
|
| |
BranchProbability construction.
The root cause is the rounding behavior in BranchProbability construction. We may consider to use truncation instead in the future.
llvm-svn: 254356
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This just concatenates the common DWP sections without doing any of the
fancy DWP things like:
1) update str_offsets
2) deduplicating strings
3) merging/creating cu/tu_index
Patches for these will follow shortly.
(also not sure about target triple/object file type for this tool - do I
really need a whole triple just to write an object file that contains
purely static/hardcoded bytes in each section? & I guess I should just
pick it based on the first input, maybe, rather than hardcoding for now
- but we only produce .dwo on ELF platforms with objcopy for now anyway)
llvm-svn: 254355
|
| |
|
|
| |
llvm-svn: 254354
|
| |
|
|
|
|
|
| |
Detect unsafe byval function arguments and move them to the unsafe
stack.
llvm-svn: 254353
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
SDAG currently can emit debug location for function parameters when
an llvm.dbg.declare points to either a function argument SSA temp,
or to an AllocaInst. This change extends this logic by adding a
fallback case when neither of the above is true.
This is required for SafeStack, which may copy the contents of a
byval function argument into something that is not an alloca, and
then describe the target as the new location of the said argument.
llvm-svn: 254352
|
| |
|
|
|
|
|
|
| |
The current code does not take alloca array size into account and,
as a result, considers any access past the first array element to be
unsafe.
llvm-svn: 254350
|
| |
|
|
|
|
| |
choice of format
llvm-svn: 254349
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
interfaces, and update all uses of old interfaces.
The patch in http://reviews.llvm.org/D13745 is broken into four parts:
1. New interfaces without functional changes (http://reviews.llvm.org/D13908).
2. Use new interfaces in SelectionDAG, while in other passes treat probabilities
as weights (http://reviews.llvm.org/D14361).
3. Use new interfaces in all other passes.
4. Remove old interfaces.
This patch is 3+4 above. In this patch, MBB won't provide weight-based
interfaces any more, which are totally replaced by probability-based ones.
The interface addSuccessor() is redesigned so that the default probability is
unknown. We allow unknown probabilities but don't allow using it together
with known probabilities in successor list. That is to say, we either have a
list of successors with all known probabilities, or all unknown
probabilities. In the latter case, we assume each successor has 1/N
probability where N is the number of successors. An assertion checks if the
user is attempting to add a successor with the disallowed mixed use as stated
above. This can help us catch many misuses.
All uses of weight-based interfaces are now updated to use probability-based
ones.
Differential revision: http://reviews.llvm.org/D14973
llvm-svn: 254348
|
| |
|
|
|
|
| |
They broke a bot and I am debugging why.
llvm-svn: 254347
|
| |
|
|
| |
llvm-svn: 254346
|
| |
|
|
| |
llvm-svn: 254345
|
| |
|
|
|
|
| |
Trying to figure out why it fails on a bot but passes locally.
llvm-svn: 254344
|
| |
|
|
|
|
|
|
| |
Contributed-by: Chris Jenneisch <chrisj@codeaurora.org>
Differential Revision: http://reviews.llvm.org/D15094
llvm-svn: 254343
|
| |
|
|
| |
llvm-svn: 254342
|
| |
|
|
| |
llvm-svn: 254341
|