| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
llvm-svn: 76775
|
| |
|
|
| |
llvm-svn: 76769
|
| |
|
|
| |
llvm-svn: 76767
|
| |
|
|
|
|
| |
complex types.
llvm-svn: 76765
|
| |
|
|
|
|
| |
This fixes unittest failure.
llvm-svn: 76764
|
| |
|
|
| |
llvm-svn: 76762
|
| |
|
|
| |
llvm-svn: 76761
|
| |
|
|
|
|
|
| |
Derive MDString directly from MetadataBase.
Introduce new bitcode block to hold metadata.
llvm-svn: 76759
|
| |
|
|
| |
llvm-svn: 76750
|
| |
|
|
| |
llvm-svn: 76736
|
| |
|
|
|
|
| |
be placed in the standard data / bss sections.
llvm-svn: 76735
|
| |
|
|
|
|
|
|
| |
on linux platforms. The binutils assembler does not
recognize the "s" flag, see for example
http://sourceware.org/binutils/docs/as/Section.html
llvm-svn: 76733
|
| |
|
|
|
|
|
|
| |
functions with a single use; eliminating the single use may eliminate
the function from the current module, but usually doesn't eliminate
it from the final program.
llvm-svn: 76730
|
| |
|
|
| |
llvm-svn: 76729
|
| |
|
|
|
|
| |
pre-caution. r12 could be live once we have mixed 32-bit and 16-bit instructions.
llvm-svn: 76728
|
| |
|
|
| |
llvm-svn: 76727
|
| |
|
|
| |
llvm-svn: 76725
|
| |
|
|
| |
llvm-svn: 76713
|
| |
|
|
|
|
| |
assembler / disassembler.
llvm-svn: 76712
|
| |
|
|
| |
llvm-svn: 76711
|
| |
|
|
|
|
| |
only caller.
llvm-svn: 76710
|
| |
|
|
|
|
| |
updating a mips testcase to expect it.
llvm-svn: 76707
|
| |
|
|
| |
llvm-svn: 76706
|
| |
|
|
|
|
|
|
| |
a new getSectionForMergableConstant hook. This removes one dependence
of TAI on Type, and provides the hook with enough info to make the
right decision based on whether the global has relocations etc.
llvm-svn: 76705
|
| |
|
|
|
|
|
|
| |
that allows late codeine passes to delete it.
This is considered a workaround. The problem is some targets are not modeling side effects correctly. PPC is apparently one of those. This patch allows ppc llvm-gcc to bootstrap on Darwin. Once we find out which instruction definitions are wrong, we can remove the PPCInstrInfo workaround.
llvm-svn: 76703
|
| |
|
|
| |
llvm-svn: 76702
|
| |
|
|
|
|
|
|
|
| |
Constant::getRelocationInfo(), which has a much simpler
to use API. It still should not be part of libvmcore, but
is better than it was. Also teach it to be smart about
hidden visibility.
llvm-svn: 76700
|
| |
|
|
|
|
|
| |
negative on an individual bases rather than basing on whether it's in thumb
mode.
llvm-svn: 76698
|
| |
|
|
| |
llvm-svn: 76693
|
| |
|
|
| |
llvm-svn: 76689
|
| |
|
|
| |
llvm-svn: 76688
|
| |
|
|
|
|
|
| |
virtual. Just inline it into its two current call sites in preparation
for simplifying the code.
llvm-svn: 76686
|
| |
|
|
| |
llvm-svn: 76683
|
| |
|
|
| |
llvm-svn: 76682
|
| |
|
|
|
|
|
|
|
|
| |
range's weight properly. This is turned off right now in the sense that
you'll get an assert if you get into a situation that can only be caused
by an iterative coalescer. All other code paths operate exactly as
before so there is no functional change with this patch. The asserts
should be disabled if/when an iterative coalescer gets added to trunk.
llvm-svn: 76680
|
| |
|
|
| |
llvm-svn: 76679
|
| |
|
|
|
|
|
|
| |
pool entry will require relocations against it. I implemented this
conservatively for ARM, someone who is knowledgable about it should
see if this can be improved.
llvm-svn: 76678
|
| |
|
|
|
|
| |
getAnalysisIfAvailable<TargetData>.
llvm-svn: 76676
|
| |
|
|
|
|
| |
to help support use when TargetData is not available.
llvm-svn: 76675
|
| |
|
|
|
|
|
|
| |
their appropriate sections before the code itself. They need to be emitted
before the function because on some targets (x86 but not x86_64) the later
may reference a JT or CP entry address
llvm-svn: 76672
|
| |
|
|
|
|
|
|
| |
(x pred y) with more thorough code that does more complete canonicalization
before resorting to range checks. This helps it find more cases where
the canonicalized expressions match.
llvm-svn: 76671
|
| |
|
|
|
|
|
|
|
| |
depends on XS1A, but I think the ReadOnlySection is already set up for this
and there is no testcase that this breaks. If this is really needed, we can
add the appropriate parameterization to TargetAsmInfo in the future to support
this.
llvm-svn: 76667
|
| |
|
|
| |
llvm-svn: 76666
|
| |
|
|
|
|
| |
LLVM IR, it should be rejected by a front-end.
llvm-svn: 76665
|
| |
|
|
|
|
| |
to twist your brain to see it, I believe it is the same as ELFTargetAsmInfo::SelectSectionForGlobal.
llvm-svn: 76664
|
| |
|
|
| |
llvm-svn: 76662
|
| |
|
|
| |
llvm-svn: 76661
|
| |
|
|
|
|
|
|
| |
the generic ELF version instead. This will result in its mergable constant
sections getting named ".rodata.cst4" instead of ".cp.const4", but the
linker looks at the section flags, not the name of the section AFAICT.
llvm-svn: 76659
|
| |
|
|
| |
llvm-svn: 76654
|
| |
|
|
|
|
|
| |
implemented exactly the same way as its ELFTargetAsmInfo subclass
has them.
llvm-svn: 76653
|