Skip to content
  1. Mar 09, 2009
  2. Mar 08, 2009
  3. 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
    • Gabor Greif's avatar
      simplify the way how traits get hold of the symbol table · 51bbcf83
      Gabor Greif authored
      llvm-svn: 66336
      51bbcf83
    • Gabor Greif's avatar
      6e1ca84d
    • Chris Lattner's avatar
      When a crash signal is delivered do two things: remove all of our · 6acb4d6f
      Chris Lattner authored
      signal handlers to prevent reentrance on unrelated things (a sigabort
      where the handle bus errors) also, clear the signal mask so that the
      signal doesn't infinitely reissue.  This fixes rdar://6654827 -
      Crash causes clang to loop
      
      llvm-svn: 66330
      6acb4d6f
    • Nate Begeman's avatar
      Finish cross-process JIT work, and clean up previous work. · 52b696c7
      Nate Begeman authored
      1. When the JIT is asked to remove a function, updating it's
         mapping to 0, we invalidate any function stubs used only 
         by that function.  Now, also invalidate the JIT's mapping
         from the GV the stub pointed to, to the address of the GV.
      
      2. When dlsym stubs for cross-process JIT are enabled, do not
         abort just because a named function cannot be found in the
         JIT's process.
      
      3. Fix various assumptions about when it is ok to use the lazy
         resolver when non-lazy JITing is enabled.
      
      llvm-svn: 66324
      52b696c7
    • Dan Gohman's avatar
      Arithmetic instructions don't set EFLAGS bits OF and CF bits · ff659b5b
      Dan Gohman authored
      the same say the "test" instruction does in overflow cases,
      so eliminating the test is only safe when those bits aren't
      needed, as is the case for COND_E and COND_NE, or if it
      can be proven that no overflow will occur. For now, just
      restrict the optimization to COND_E and COND_NE and don't
      do any overflow analysis.
      
      llvm-svn: 66318
      ff659b5b
  4. Mar 06, 2009
Loading