Skip to content
  1. Aug 02, 2009
  2. Jul 31, 2009
  3. Jul 28, 2009
    • Chris Lattner's avatar
      Rip all of the global variable lowering logic out of TargetAsmInfo. Since · 5e693ed0
      Chris Lattner authored
      it is highly specific to the object file that will be generated in the end,
      this introduces a new TargetLoweringObjectFile interface that is implemented
      for each of ELF/MachO/COFF/Alpha/PIC16 and XCore.
      
      Though still is still a brutal and ugly refactoring, this is a major step
      towards goodness.
      
      This patch also:
      1. fixes a bunch of dangling pointer problems in the PIC16 backend.
      2. disables the TargetLowering copy ctor which PIC16 was accidentally using.
      3. gets us closer to xcore having its own crazy target section flags and
         pic16 not having to shadow sections with its own objects.
      4. fixes wierdness where ELF targets would set CStringSection but not
         CStringSection_.  Factor the code better.
      5. fixes some bugs in string lowering on ELF targets.
      
      llvm-svn: 77294
      5e693ed0
  4. Jul 27, 2009
  5. Jul 26, 2009
  6. Jul 25, 2009
    • Chris Lattner's avatar
      this is (unfortunately) several changes mixed together: · 60f3b73e
      Chris Lattner authored
      1. Spell SectionFlags::Writeable as "Writable".
      2. Add predicates for deriving SectionFlags from SectionKinds.
      3. Sink ELF-specific getSectionPrefixForUniqueGlobal impl into
         ELFTargetAsmInfo.
      4. Fix SectionFlagsForGlobal to know that BSS/ThreadBSS has the
         BSS bit set (the real fix for PR4619).
      5. Fix isSuitableForBSS to not put globals with explicit sections
         set in BSS (which was the reason #4 wasn't fixed earlier).
      6. Remove my previous hack for PR4619.
      
      llvm-svn: 77085
      60f3b73e
  7. Jul 24, 2009
  8. Jul 22, 2009
  9. Jul 21, 2009
  10. Jul 20, 2009
  11. Jul 17, 2009
    • Chris Lattner's avatar
      Untangle a snarl that I discovered when updating the mangler, · e79b2bc0
      Chris Lattner authored
      starting in getCurrentFunctionEHName.  Among other problems,
      we would try to privative a "foo.eh" label, but end up emitting
      the label as _Lfoo.eh instead of L_foo.eh on darwin.  This is really
      bad, and the linker has always tolerated these labels existing.
      For now, just emit them as _foo.eh.
      
      This patch also fixes problems with ".eh" labels on unnamed
      functions and eliminates two strangely defined TargetAsmInfo
      hooks.
      
      llvm-svn: 76231
      e79b2bc0
  12. Jul 15, 2009
  13. Jul 14, 2009
    • Chris Lattner's avatar
      Reapply my previous asmprinter changes now with more testing and two · 8c9a96b9
      Chris Lattner authored
      additional bug fixes:
      
      1. The bug that everyone hit was a problem in the asmprinter where it
         would remove $stub but keep the L prefix on a name when emitting the
         indirect symbol.  This is easy to fix by keeping the name of the stub
         and the name of the symbol in a StringMap instead of just keeping a
         StringSet and trying to reconstruct it late.
      
      2. There was a problem printing the personality function.  The current
         logic to print out the personality function from the DWARF information
         is a bit of a cesspool right now that duplicates a bunch of other 
         logic in the asm printer.  The short version of it is that it depends
         on emitting both the L and _ prefix for symbols (at least on darwin)
         and until I can untangle it, it is best to switch the mangler back to
         emitting both prefixes.
      
      llvm-svn: 75646
      8c9a96b9
    • Torok Edwin's avatar
      llvm_unreachable->llvm_unreachable(0), LLVM_UNREACHABLE->llvm_unreachable. · fbcc663c
      Torok Edwin authored
      This adds location info for all llvm_unreachable calls (which is a macro now) in
      !NDEBUG builds.
      In NDEBUG builds location info and the message is off (it only prints
      "UREACHABLE executed").
      
      llvm-svn: 75640
      fbcc663c
    • Daniel Dunbar's avatar
      Revert r7561{9,8,7,6}, which depend on r75610. · eb3e4271
      Daniel Dunbar authored
      --- Reverse-merging r75619 into '.':
      U    lib/Target/DarwinTargetAsmInfo.cpp
      U    lib/CodeGen/AsmPrinter/AsmPrinter.cpp
      --- Reverse-merging r75618 into '.':
      U    lib/CodeGen/ELFWriter.cpp
      U    lib/CodeGen/MachOCodeEmitter.cpp
      U    lib/CodeGen/MachOWriter.cpp
      --- Reverse-merging r75617 into '.':
      U    lib/Target/CBackend/CBackend.cpp
      --- Reverse-merging r75616 into '.':
      U    tools/bugpoint/Miscompilation.cpp
      U    tools/lto/LTOCodeGenerator.cpp
      U    tools/lto/LTOModule.cpp
      
      llvm-svn: 75638
      eb3e4271
    • Chris Lattner's avatar
      rename getValueName -> getMangledName. These two files have very · 3af24cc2
      Chris Lattner authored
      dubious looking things that I need to investigate in more detail.
      
      llvm-svn: 75619
      3af24cc2
  14. Jul 11, 2009
    • Torok Edwin's avatar
      assert(0) -> LLVM_UNREACHABLE. · 56d06597
      Torok Edwin authored
      Make llvm_unreachable take an optional string, thus moving the cerr<< out of
      line.
      LLVM_UNREACHABLE is now a simple wrapper that makes the message go away for
      NDEBUG builds.
      
      llvm-svn: 75379
      56d06597
  15. Jun 19, 2009
  16. May 09, 2009
  17. Mar 30, 2009
  18. Mar 07, 2009
    • Duncan Sands's avatar
      Introduce new linkage types linkonce_odr, weak_odr, common_odr · 12da8ce3
      Duncan Sands authored
      and extern_weak_odr.  These are the same as the non-odr versions,
      except that they indicate that the global will only be overridden
      by an *equivalent* global.  In C, a function with weak linkage can
      be overridden by a function which behaves completely differently.
      This means that IP passes have to skip weak functions, since any
      deductions made from the function definition might be wrong, since
      the definition could be replaced by something completely different
      at link time.   This is not allowed in C++, thanks to the ODR
      (One-Definition-Rule): if a function is replaced by another at
      link-time, then the new function must be the same as the original
      function.  If a language knows that a function or other global can
      only be overridden by an equivalent global, it can give it the
      weak_odr linkage type, and the optimizers will understand that it
      is alright to make deductions based on the function body.  The
      code generators on the other hand map weak and weak_odr linkage
      to the same thing.
      
      llvm-svn: 66339
      12da8ce3
  19. Jan 27, 2009
    • Anton Korobeynikov's avatar
      Treat [1 x i8] zeroinitializer as a C string, placing such stuff into · 70d4c08c
      Anton Korobeynikov authored
      mergeable string section. I don't see any bad impact of such decision
      (rather then placing it into mergeable const section, as it was before),
      but at least Darwin linker won't complain anymore.
      
      The problem in LLVM is that we don't have special type for string constants
      (like gcc does). Even more, we have two separate types: ConstatArray for non-null
      strings and ConstantAggregateZero for null stuff.... It's a bit weird :)
      
      llvm-svn: 63142
      70d4c08c
  20. Jan 15, 2009
Loading