| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
llvm-svn: 251279
|
| |
|
|
| |
llvm-svn: 251278
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
Per discussions on the mailing list, I have implemented a decorator which annotates individual
test methods with categories. I have used this framework to replace the '-a' and '+a'
command-line switches (now '-G pyapi' and '--skip-category pyapi') and the @python_api_test
decorator (now @add_test_categories('pyapi')). The test suite now gives an error message
suggesting the new options if the user specifies the deprecated +/-a switches. If the general
direction is good, I will follow this up with other switches.
Reviewers: tberghammer, tfiala, granata.enrico, zturner
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D14020
llvm-svn: 251277
|
| |
|
|
|
|
| |
to ‘bool’ from ‘std::nullptr_t’
llvm-svn: 251276
|
| |
|
|
|
|
|
|
|
|
| |
Otherwise value can be reused , despite its value could be changed - produces incorrect assembler.
https://llvm.org/bugs/show_bug.cgi?id=25270
Differential Revision: http://reviews.llvm.org/D14057
llvm-svn: 251275
|
| |
|
|
| |
llvm-svn: 251274
|
| |
|
|
|
|
|
|
|
|
|
|
| |
the module pointer type passed in by the user.
The previous ownership scheme, where the user pointer was always moved into a
std::shared_ptr, breaks if the user passes in a raw pointer.
Discovered while working on the Orc C API, which should be landing shortly.
I expect to include a test-case with that.
llvm-svn: 251273
|
| |
|
|
| |
llvm-svn: 251272
|
| |
|
|
|
|
|
|
|
|
| |
GNU as and Darwin give the various binary operators different
precedence. LLVM's MC supported the Darwin semantics but not the GNU
semantics.
This fixes PR25311.
llvm-svn: 251271
|
| |
|
|
|
|
|
|
|
|
| |
We didn't validate that the .word directive was given a sane value,
leading to crashes when we attempt to write out the object file.
Instead, perform some validation and issue a diagnostic pointing at the
start of the diagnostic.
llvm-svn: 251270
|
| |
|
|
|
|
|
| |
This is just a trivial patch that corrects a couple of return value account to function's return type.
Also corrects typo in hardware breakpoint handler.
llvm-svn: 251269
|
| |
|
|
|
|
| |
This fixes llvm.org/PR25242
llvm-svn: 251268
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of playing around with dominance to verify if the possible expansion of
a scop region is indeed a single entry single exit region, we now distinguish
two cases. In case we only append a basic block, all edges entering this basic
block need to have come from within the region that is expanded. In case we join
two regions, the source basic blocks of the edges that end at the entry node of
the region that is appended most be part of either the original region or the
region that is appended.
This change will be tested through Polly.
This fixes llvm.org/PR25242
llvm-svn: 251267
|
| |
|
|
| |
llvm-svn: 251266
|
| |
|
|
| |
llvm-svn: 251265
|
| |
|
|
| |
llvm-svn: 251264
|
| |
|
|
| |
llvm-svn: 251263
|
| |
|
|
| |
llvm-svn: 251262
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
directory.
Also added a placeholder Editline gtest for some code that I'll add as soon
as I make sure this addition doesn't break any of the build bots.
This change also introduces some Xcode user-defined variables that I've used
to attempt to isolate the way Python is integrated into the build. I don't have
the rest of LLDB using it yet, I'm using the gtests as my guinea pig on that.
Currently these are:
PYTHON_FRAMEWORK_PATH
PYTHON_VERSION_MAJOR
PYTHON_VERSION_MINOR
I will convert the rest over to it after this gets a little time to bake
and any kinks are worked out of it.
llvm-svn: 251261
|
| |
|
|
|
|
|
| |
Windows has two different mangling specifiers. `x` is used on x86 for the `_`
UserLabelPrefix. Others use `w` for the no UserLabelPrefix.
llvm-svn: 251260
|
| |
|
|
| |
llvm-svn: 251259
|
| |
|
|
| |
llvm-svn: 251258
|
| |
|
|
| |
llvm-svn: 251257
|
| |
|
|
| |
llvm-svn: 251256
|
| |
|
|
| |
llvm-svn: 251255
|
| |
|
|
| |
llvm-svn: 251254
|
| |
|
|
| |
llvm-svn: 251253
|
| |
|
|
|
|
| |
incorrect
llvm-svn: 251252
|
| |
|
|
|
|
| |
The build broke in r251248.
llvm-svn: 251251
|
| |
|
|
| |
llvm-svn: 251250
|
| |
|
|
| |
llvm-svn: 251249
|
| |
|
|
| |
llvm-svn: 251248
|
| |
|
|
| |
llvm-svn: 251247
|
| |
|
|
| |
llvm-svn: 251246
|
| |
|
|
|
|
| |
Incorrect range test - found during fuzz testing.
llvm-svn: 251245
|
| |
|
|
|
|
|
|
|
| |
I totally forgot that char can be defined as unsigned on some platforms.
Now I made explicit mention of signed type where necessary in tests.
Also fixed '//RUN: ' header of cxx98 test to correct format.
llvm-svn: 251244
|
| |
|
|
|
|
|
|
| |
I am also letting a debugserver-related project entry slide in
since Xcode seems to insist on inserting it, and when I remove it
the new files don't show up.
llvm-svn: 251243
|
| |
|
|
| |
llvm-svn: 251242
|
| |
|
|
| |
llvm-svn: 251241
|
| |
|
|
| |
llvm-svn: 251240
|
| |
|
|
| |
llvm-svn: 251239
|
| |
|
|
| |
llvm-svn: 251238
|
| |
|
|
|
|
|
|
|
|
| |
When the target does not support these intrinsics they should be converted to a chain of scalar load or store operations.
If the mask is not constant, the scalarizer will build a chain of conditional basic blocks.
I added isLegalMaskedGather() isLegalMaskedScatter() APIs.
Differential Revision: http://reviews.llvm.org/D13722
llvm-svn: 251237
|
| |
|
|
| |
llvm-svn: 251236
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
This is another check that I ported to clang-tidy from colobot-lint tool.
As previously discussed on cfe-dev mailing list, this is one of those
checks that I think is general and useful enough for contribution to
clang-tidy.
This patch contains implementation of check taken from colobot-lint, but
it is extended a great deal, including FixIt hints for automated
refactoring, exhaustive testcases, and user documentation.
Reviewers: sbenza, aaron.ballman, alexfh
Subscribers: Eugene.Zelenko
Differential Revision: http://reviews.llvm.org/D13635
llvm-svn: 251235
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Volatile or atomic memory accesses are currently not supported. Neither did
we think about any special handling needed nor do we support the unknown
instructions the alias set tracker turns them into sometimes. Before this
patch, us not supporting unkown instructions in an alias set caused the
following assertion failures:
Assertion `AG.size() > 1 && "Alias groups should contain at least two accesses"'
failed
llvm-svn: 251234
|
| |
|
|
| |
llvm-svn: 251233
|
| |
|
|
|
|
| |
regenerate/cleanup
llvm-svn: 251232
|
| |
|
|
| |
llvm-svn: 251231
|
| |
|
|
| |
llvm-svn: 251230
|