Skip to content
  1. Mar 14, 2014
    • Simon Atanasyan's avatar
      a3130a4b
    • Simon Atanasyan's avatar
      [Mips] Add one more MIPS relocation type constant. · 23ace1f0
      Simon Atanasyan authored
      llvm-svn: 203896
      23ace1f0
    • Owen Anderson's avatar
      Revert r203883 (which was more of a bandaid) and fix the real underlying · ec5d4803
      Owen Anderson authored
      issue in that the new MachineRegisterInfo bundle iterators didn't
      dereference to the START of the bundle, while the old skipBundle()
      method did.
      
      llvm-svn: 203890
      ec5d4803
    • Sebastian Pop's avatar
      static link polly into tools · a59005be
      Sebastian Pop authored
      llvm-svn: 203886
      a59005be
    • Pete Cooper's avatar
      Fix issue with r203865. The old behaviour would get a MachineOperand then... · 7360280e
      Pete Cooper authored
      Fix issue with r203865.  The old behaviour would get a MachineOperand then find the MI for the bundle the MI was in.  The new behaviour was failing to get the parent bundle and instead just used the MI from the MachineOperand
      
      llvm-svn: 203883
      7360280e
    • Galina Kistanova's avatar
      Reverted r203879. · 1b6a6f16
      Galina Kistanova authored
      llvm-svn: 203880
      1b6a6f16
    • Galina Kistanova's avatar
      Fixed misuse of isascii. Also fixes mingw32 build, see... · a7419355
      Galina Kistanova authored
      Fixed misuse of isascii. Also fixes mingw32 build, see http://msdn.microsoft.com/en-us/library/ms235417.aspx
      
      llvm-svn: 203879
      a7419355
    • Eric Christopher's avatar
      Use DW_AT_linkage_name when we're emitting DWARF4 or above. · af7eca2d
      Eric Christopher authored
      llvm-svn: 203867
      af7eca2d
    • Rafael Espindola's avatar
      Remove the linker_private and linker_private_weak linkages. · 2fb5bc33
      Rafael Espindola authored
      These linkages were introduced some time ago, but it was never very
      clear what exactly their semantics were or what they should be used
      for. Some investigation found these uses:
      
      * utf-16 strings in clang.
      * non-unnamed_addr strings produced by the sanitizers.
      
      It turns out they were just working around a more fundamental problem.
      For some sections a MachO linker needs a symbol in order to split the
      section into atoms, and llvm had no idea that was the case. I fixed
      that in r201700 and it is now safe to use the private linkage. When
      the object ends up in a section that requires symbols, llvm will use a
      'l' prefix instead of a 'L' prefix and things just work.
      
      With that, these linkages were already dead, but there was a potential
      future user in the objc metadata information. I am still looking at
      CGObjcMac.cpp, but at this point I am convinced that linker_private
      and linker_private_weak are not what they need.
      
      The objc uses are currently split in
      
      * Regular symbols (no '\01' prefix). LLVM already directly provides
      whatever semantics they need.
      * Uses of a private name (start with "\01L" or "\01l") and private
      linkage. We can drop the "\01L" and "\01l" prefixes as soon as llvm
      agrees with clang on L being ok or not for a given section. I have two
      patches in code review for this.
      * Uses of private name and weak linkage.
      
      The last case is the one that one could think would fit one of these
      linkages. That is not the case. The semantics are
      
      * the linker will merge these symbol by *name*.
      * the linker will hide them in the final DSO.
      
      Given that the merging is done by name, any of the private (or
      internal) linkages would be a bad match. They allow llvm to rename the
      symbols, and that is really not what we want. From the llvm point of
      view, these objects should really be (linkonce|weak)(_odr)?.
      
      For now, just keeping the "\01l" prefix is probably the best for these
      symbols. If we one day want to have a more direct support in llvm,
      IMHO what we should add is not a linkage, it is just a hidden_symbol
      attribute. It would be applicable to multiple linkages. For example,
      on weak it would produce the current behavior we have for objc
      metadata. On internal, it would be equivalent to private (and we
      should then remove private).
      
      llvm-svn: 203866
      2fb5bc33
    • Owen Anderson's avatar
      Phase 2 of the great MachineRegisterInfo cleanup. This time, we're changing · 16c6bf49
      Owen Anderson authored
      operator* on the by-operand iterators to return a MachineOperand& rather than
      a MachineInstr&.  At this point they almost behave like normal iterators!
      
      Again, this requires making some existing loops more verbose, but should pave
      the way for the big range-based for-loop cleanups in the future.
      
      llvm-svn: 203865
      16c6bf49
  2. Mar 13, 2014
Loading