| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
Each check can implement readOptions and storeOptions methods to read
and store custom options. Each check's options are stored in a local namespace
to avoid name collisions and provide some sort of context to the user.
Reviewers: bkramer, klimek
Reviewed By: klimek
Subscribers: cfe-commits
Differential Revision: http://reviews.llvm.org/D5296
llvm-svn: 217661
|
|
|
|
| |
llvm-svn: 217659
|
|
|
|
|
|
| |
Douglas Gregor and Ted Kremenek.
llvm-svn: 217658
|
|
|
|
| |
llvm-svn: 217657
|
|
|
|
| |
llvm-svn: 217656
|
|
|
|
|
|
| |
make_unique.
llvm-svn: 217655
|
|
|
|
|
|
|
|
|
|
|
|
| |
Deleted virtual functions get _purecall inserted into the vftable.
Earlier CTPs would simply stick nullptr in there.
N.B. MSVC can't handle deleted virtual functions which require return
adjusting thunks, they give an error that a deleted function couldn't be
called inside of a compiler generated function. We get this correct by
making the thunk have a __purecall entry as well.
llvm-svn: 217654
|
|
|
|
|
|
|
| |
TypeValidatorImpl, FileAction, and ProcessLaunchInfo to match the
lldb coding convention.
llvm-svn: 217653
|
|
|
|
| |
llvm-svn: 217652
|
|
|
|
|
|
| |
union containing either a member named __cc, or either of __cc and __nc (const vs. non-const). This level of wrapping is quite useless for LLDB to show to people, so try to detect it, and filter it out
llvm-svn: 217651
|
|
|
|
|
|
| |
This matches the strtoull() behavior in ld64.
llvm-svn: 217650
|
|
|
|
|
|
|
|
| |
ProcessStructReader instead of reading the structure out of libdispatch
by hand. I will convert more of the struct readers in SystemRuntimeMacOSX
over to use this class eventually.
llvm-svn: 217649
|
|
|
|
|
|
| |
NFC.
llvm-svn: 217648
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Sends a SIGSTOP to the process.
* Fixes busted SIGSTOP handling. Now builds a list of non-stopped
that we wait for the PTRACE group-stop for. When the final must-stop
tid gets its group stop, we propagate the process state change.
Only the signal receiving the notification of the pending SIGSTOP
is marked with the SIGSTOP signal. All the rest, if they weren't
already stopped, are marked as stopped with signal 0.
* Fixes a few broken tests.
* Marks the Linux test I added earlier as expect-pass (no longer XFAIL).
Implements fix for http://llvm.org/bugs/show_bug.cgi?id=20908.
llvm-svn: 217647
|
|
|
|
|
|
|
|
|
|
| |
This fixes a call to sys::fs::equivalent that should've been to
CodeCoverageTool::equivalentFiles, which lets us restore the test of
r217476 that was removed in r217478.
This reverts r217478, but the test works this time.
llvm-svn: 217646
|
|
|
|
| |
llvm-svn: 217645
|
|
|
|
|
|
|
|
|
|
| |
The purpose of a ProcessStructReader is to allow intelligent reading of data from the underlying process
Traditionally, the way this has been handled is to have a load_address and shuffle it around, and use Process::ReadMemory()-kind APIs
With a ProcessStructReader one can define a clang type that matches exactly the definition of the thing they are trying to ingest from the inferior process, and then just point LLDB at where the data is
Since this work is done in terms of clang types, one can honor packed/aligned attributes, sizes of types on the inferior architecture, and similar tricky caveats without having to hardcode them
llvm-svn: 217644
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A "stub found found" diagnostic is emitted when RuntimeDyldChecker's stub lookup
logic fails to find the requested stub. The obvious reason for the failure is
that no such stub has been created, but it can also fail for internal symbols if
the symbol offset is not computed correctly (E.g. due to a mangled relocation
addend). This patch adds a comment about the latter case so that it's not
overlooked.
Inspired by confusion experienced during test case construction for r217635.
llvm-svn: 217643
|
|
|
|
|
|
|
|
|
|
| |
We assumed that the incoming this argument would be the last argument.
However, this is not true under the MS ABI.
This fixes PR20897.
llvm-svn: 217642
|
|
|
|
|
|
| |
summary is a good candidate to ask. While in theory one could want one-liner printing with a non-one-liner summary, I don't see LLDB as the best place to solve such inner conflicts
llvm-svn: 217641
|
|
|
|
| |
llvm-svn: 217639
|
|
|
|
|
|
|
| |
This patch is to overload operator+= and operator-= for
{u}{little}{big}{16,32,64}_t.
llvm-svn: 217637
|
|
|
|
|
|
|
| |
The register numbers start at 0, so if only 1 register
was used, this was reported as 0.
llvm-svn: 217636
|
|
|
|
|
|
|
|
|
|
| |
symbols.
Previously we have only been testing these relocations with external symbols.
<rdar://problem/18308413>
llvm-svn: 217635
|
|
|
|
| |
llvm-svn: 217634
|
|
|
|
|
|
|
| |
Use llvm::COFF::BigObjMagic insetad of the string literal.
Also checks the version number.
llvm-svn: 217633
|
|
|
|
| |
llvm-svn: 217632
|
|
|
|
|
|
|
| |
The byte has no endianness, so these types don't make sense.
uint8_t should be used instead.
llvm-svn: 217631
|
|
|
|
| |
llvm-svn: 217630
|
|
|
|
|
|
| |
I.e., teach it about 'sext (zext a to ty) to ty2' => zext a to ty2.
llvm-svn: 217629
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
And since it /looked/ like the DwarfStrSectionSym was unused, I tried
removing it - but then it turned out that DwarfStringPool was
reconstructing the same label (and expecting it to have already been
emitted) and uses that.
So I kept it around, but wanted to pass it in to users - since it seemed
a bit silly for DwarfStringPool to have it passed in and returned but
itself have no use for it. The only two users don't handle strings in
both .dwo and .o files so they only ever need the one symbol - no need
to keep it (and have an unused symbol) in the DwarfStringPool used for
fission/.dwo.
Refactor a bunch of accelerator table usage to remove duplication so I
didn't have to touch 4-5 callers.
llvm-svn: 217628
|
|
|
|
|
|
|
| |
identify_magic recognized a COFF bigobj as an import library file.
This patch fixes that.
llvm-svn: 217627
|
|
|
|
|
|
| |
Also make it private as it doesn't have to be protected function.
llvm-svn: 217626
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The main difference is the removal of
std::error_code exists(const Twine &path, bool &result);
It was an horribly redundant interface since a file not existing is also a valid
error_code. Now we have an access function that returns just an error_code. This
is the only function that has to be implemented for Unix and Windows. The
functions can_write, exists and can_execute an now just wrappers.
One still has to be very careful using these function to avoid introducing
race conditions (Time of check to time of use).
llvm-svn: 217625
|
|
|
|
|
|
|
|
| |
* ssize_t isn't defined by default on Windows.
* New public API files need to be defined in a different file for
Windows.
llvm-svn: 217624
|
|
|
|
| |
llvm-svn: 217623
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Inline asm may specify 'U' and 'X' constraints to print a 'u' for an
update-form memory reference, or an 'x' for an indexed-form memory
reference. However, these are really only useful in GCC internal code
generation. In inline asm the operand of the memory constraint is
typically just a register containing the address, so 'U' and 'X' make
no sense.
This patch quietly accepts 'U' and 'X' in inline asm patterns, but
otherwise does nothing. If we ever unexpectedly see a non-register,
we'll assert and sort it out afterwards.
I've added a new test for these constraints; the test case should be
used for other asm-constraints changes down the road.
llvm-svn: 217622
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
r217556 introduced an operator<<(std::ostream &, StringRef) that seems
to self recurse on some systems, because str.data(), which is a char *,
was being implicitly converted back to StringRef in overload
resolution.
This manifested as SemaCXX/warn-thread-safety-analysis.cpp timing out
in release builds and overflowing the stack in debug builds. One of
the failing systems that saw this is here:
http://lab.llvm.org:8013/builders/clang-x86_64-darwin11-nobootstrap-RAincremental/builds/4636
Using ostream's write method instead of operator<< should get the bots
going again.
llvm-svn: 217621
|
|
|
|
|
|
| |
Fixes <rdar://problem/18297804>.
llvm-svn: 217620
|
|
|
|
|
|
|
|
|
| |
off by default, issue a warning if %s directive is used
in formart argument of a function/method declared as
__attribute__((format(CF/NSString, ...)))
To complete rdar://18182443
llvm-svn: 217619
|
|
|
|
| |
llvm-svn: 217618
|
|
|
|
| |
llvm-svn: 217617
|
|
|
|
|
|
| |
UBSan is combined with ASan.
llvm-svn: 217616
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
preprocessor output
Summary:
cl.exe recognizes /o as a deprecated and undocumented option similar to
/Fe. This patch adds support for this option to clang-cl for /Fe, /Fo
and /Fi. It also ensures that the last option among /o and /F* wins,
if both specified.
This is required at least for building autoconf based software, since
autoconf uses -o to specify the executable output.
This fixes http://llvm.org/PR20894.
Test Plan: The patch includes automated tests.
Reviewers: rnk
Subscribers: cfe-commits
Differential Revision: http://reviews.llvm.org/D5308
llvm-svn: 217615
|
|
|
|
|
|
|
| |
In all these cases it looks like the intention was to handle error in a similar
way to the file not existing.
llvm-svn: 217614
|
|
|
|
|
|
|
|
|
|
| |
app is interrupted.
The Linux version is marked XFAIL for the moment, fixing next.
Related to http://llvm.org/bugs/show_bug.cgi?id=20908.
llvm-svn: 217613
|
|
|
|
| |
llvm-svn: 217612
|
|
|
|
| |
llvm-svn: 217611
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Do
(shl (add x, c1), c2) -> (add (shl x, c2), c1 << c2)
This is already done for multiplies, but since multiplies
by powers of two are turned into shifts, we also need
to handle it here.
This might want checks for isLegalAddImmediate to avoid
transforming an add of a legal immediate with one that isn't.
llvm-svn: 217610
|
|
|
|
| |
llvm-svn: 217609
|