| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
This can actually be non-zero if you override a function from a virtual
base and you have forced the most_general pointer to member
representation.
llvm-svn: 205727
|
| |
|
|
|
|
|
| |
Using this file would result in an odr violation: it defines an llvm::Interval
class that conflicts with the one in Analysis/Interval.h.
llvm-svn: 205726
|
| |
|
|
|
|
| |
the non-matching next line in the diagnostic to make the problem more obvious.
llvm-svn: 205725
|
| |
|
|
| |
llvm-svn: 205723
|
| |
|
|
| |
llvm-svn: 205722
|
| |
|
|
|
|
| |
Found by Richard Osbourne!
llvm-svn: 205721
|
| |
|
|
|
|
| |
Thanks, Alex!
llvm-svn: 205720
|
| |
|
|
| |
llvm-svn: 205719
|
| |
|
|
|
|
| |
it is subsumed by r205521.
llvm-svn: 205718
|
| |
|
|
| |
llvm-svn: 205717
|
| |
|
|
|
|
| |
Note that /Gy no longer implies -fdata-sections.
llvm-svn: 205716
|
| |
|
|
| |
llvm-svn: 205715
|
| |
|
|
|
|
|
|
| |
member function or member function template is declared 'const'
Patch by Kevin Funk with testcase updates by me.
llvm-svn: 205714
|
| |
|
|
|
|
| |
change outside of the command line to enable it.
llvm-svn: 205713
|
| |
|
|
|
|
|
| |
Not yet root-caused, but I presume it is the same issue that affects
Linux.
llvm-svn: 205712
|
| |
|
|
|
|
| |
that at least failed reliably.
llvm-svn: 205711
|
| |
|
|
|
|
|
|
|
|
|
| |
into a constant size alloca by inlining.
Ran a run over the testsuite, no results out of the noise, fixes
the testcase in the PR.
PR19115.
llvm-svn: 205710
|
| |
|
|
| |
llvm-svn: 205709
|
| |
|
|
|
|
|
|
|
| |
cygwin has llvm-dwarfdump problems and isn't paying attention to the
specific xfail there.
s390x isn't matching for an unknown reason.
llvm-svn: 205708
|
| |
|
|
| |
llvm-svn: 205707
|
| |
|
|
| |
llvm-svn: 205706
|
| |
|
|
|
|
| |
Patch by Zinovy Nis.
llvm-svn: 205705
|
| |
|
|
|
|
| |
it's being investigated for those.
llvm-svn: 205704
|
| |
|
|
| |
llvm-svn: 205703
|
| |
|
|
| |
llvm-svn: 205702
|
| |
|
|
| |
llvm-svn: 205701
|
| |
|
|
|
|
| |
require no library work, and fixed a typo in index.html. Thanks to Tobias for pointing these out.
llvm-svn: 205700
|
| |
|
|
| |
llvm-svn: 205699
|
| |
|
|
| |
llvm-svn: 205698
|
| |
|
|
| |
llvm-svn: 205697
|
| |
|
|
| |
llvm-svn: 205696
|
| |
|
|
| |
llvm-svn: 205695
|
| |
|
|
| |
llvm-svn: 205694
|
| |
|
|
|
|
|
|
| |
GNU LD-comptaible driver wrongly requires a space after '=' for a few
options such as "-init=<symbol>" or "-entry=<symbol>". This patch is
to fix that bug and add a few tests for it.
llvm-svn: 205693
|
| |
|
|
|
|
| |
No functional changes.
llvm-svn: 205692
|
| |
|
|
|
|
|
|
| |
We already got the type alias correct (though I've included a test case
here) since Clang represents that like any other typedef - but type
alias templates weren't being handled.
llvm-svn: 205691
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- take->release: LLVM has moved to C++11. MockWrapper became an instance of unique_ptr.
- method symbol_iterator::increment disappeared recently, in this revision:
r200442 | rafael | 2014-01-29 20:49:50 -0600 (Wed, 29 Jan 2014) | 9 lines
Simplify the handling of iterators in ObjectFile.
None of the object file formats reported error on iterator increment. In
retrospect, that is not too surprising: no object format stores symbols or
sections in a linked list or other structure that requires chasing pointers.
As a consequence, all error checking can be done on begin() and end().
This reduces the text segment of bin/llvm-readobj in my machine from 521233 to
518526 bytes.
My change mimics the change that the revision made to lib/DebugInfo/DWARFContext.cpp .
- const_cast: Shut up a warning from gcc.
I ran unittests/ExecutionEngine/JIT/Debug+Asserts/JITTests to make sure it worked.
- Arch
llvm-svn: 205689
|
| |
|
|
|
|
|
|
| |
It affected callee's stack pop in x86. It is one of devergences between cygwin and mingw since mingw-gcc-4.6.
Added testcases to llvm/test/CodeGen/X86/win32_sret.ll for cygwin.
llvm-svn: 205688
|
| |
|
|
|
|
|
|
| |
be used for indexing not only section's names.
No functional changes.
llvm-svn: 205687
|
| |
|
|
|
|
|
|
| |
named imported entities
Apparently that's how DWARF4 suggests they be emitted. So let's do that.
llvm-svn: 205686
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
of DW_TAG_imported_module
I really should read the spec more often (and test GCC more often too).
I just assumed that namespace aliases would be the same as using
directives, except with a name. But apparently that's not how the DWARF
standards suggests they be implemented. DWARF4 provides an example and
other non-normative text suggesting that namespace aliases be
implemented by named imported declarations intsead of named imported
modules.
So be it.
llvm-svn: 205685
|
| |
|
|
|
|
| |
again. Needs llvm r205683.
llvm-svn: 205684
|
| |
|
|
|
|
| |
the lock was released.
llvm-svn: 205683
|
| |
|
|
|
|
|
|
|
|
|
| |
Also update a few null pointers in this function to be consistent with
new null pointers being added.
Patch by Robert Matusewicz!
Differential Revision: http://reviews.llvm.org/D3123
llvm-svn: 205682
|
| |
|
|
|
|
|
|
|
| |
This adds a warning when linker_private or linker_private_weak is provided and
we handle it in a compatible manner.
Suggested by Chris Lattner!
llvm-svn: 205681
|
| |
|
|
|
|
|
| |
Makes iteration over implicit and explicit machine operands more
explicit (har har). Insipired by code review discussion for r205565.
llvm-svn: 205680
|
| |
|
|
|
|
|
|
|
| |
Member functions defined within a class definition are implicitly
'inline' for linkage purposes. Compilers might slightly favor inlining
functions explicitly marked 'inline', but LLVM doesn't make a stylistic
habit of doing this generally.
llvm-svn: 205679
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This consolidates the duplicated MachO checks in the directive parsing for
various directives that are unsupported for Mach-O. The error message change is
unimportant as this restores the behaviour to that prior to the addition of the
new directive handling. Furthermore, use a more direct check for MachO
targeting rather than an indirect feature check of the assembler.
Also simplify the test execution command to avoid temporary files. Further more,
perform the check in both object and assembly emission.
Whether all non-applicable directives are handled is another question. .fnstart
is marked as being unsupported, however, the complementary .fnend is not. The
additional unwinding directives are also still honoured. This change does not
change that, though, it would be good to validate and mark them as being
unsupported if they are unsupported for the MachO emission.
llvm-svn: 205678
|
| |
|
|
|
|
|
|
| |
MemoryBuffer
This is the other half of r205676.
llvm-svn: 205677
|
| |
|
|
|
|
|
|
|
|
|
|
| |
MemoryBuffer
This avoids an extra copy during decompression and avoids the use of
MemoryBuffer which is a weirdly esoteric device that includes unrelated
concepts like "file name" (its rather generic name is a bit misleading).
Similar refactoring of zlib::compress coming up.
llvm-svn: 205676
|