Skip to content
  1. Jun 28, 2013
  2. Jun 27, 2013
    • Michael Gottesman's avatar
      Revert "Revert "[APFloat] Removed APFloat constructor which initialized to... · 79b09675
      Michael Gottesman authored
      Revert "Revert "[APFloat] Removed APFloat constructor which initialized to either zero/NaN but allowed you to arbitrarily set the category of the float.""
      
      This reverts commit r185099.
      
      Looks like both the ppc-64 and mips bots are still failing after I reverted this
      change.
      
      Since:
      
      1. The mips bot always performs a clean build,
      2. The ppc64-bot failed again after a clean build (I asked the ppc-64
      maintainers to clean the bot which they did... Thanks Will!),
      
      I think it is safe to assume that this change was not the cause of the failures
      that said builders were seeing. Thus I am recomitting.
      
      llvm-svn: 185111
      79b09675
    • Michael Gottesman's avatar
      Revert "[APFloat] Removed APFloat constructor which initialized to either... · ccaf3321
      Michael Gottesman authored
      Revert "[APFloat] Removed APFloat constructor which initialized to either zero/NaN but allowed you to arbitrarily set the category of the float."
      
      This reverts commit r185095. This is causing a FileCheck failure on
      the 3dnow intrinsics on at least the mips/ppc bots but not on the x86
      bots.
      
      Reverting while I figure out what is going on.
      
      llvm-svn: 185099
      ccaf3321
    • Arnold Schwaighofer's avatar
      LoopVectorize: Cache edge masks created during if-conversion · 38de7cd4
      Arnold Schwaighofer authored
      Otherwise, we end up with an exponential IR blowup.
      Fixes PR16472.
      
      llvm-svn: 185097
      38de7cd4
    • Michael Gottesman's avatar
      [APFloat] Removed APFloat constructor which initialized to either zero/NaN but... · 03255a16
      Michael Gottesman authored
      [APFloat] Removed APFloat constructor which initialized to either zero/NaN but allowed you to arbitrarily set the category of the float.
      
      The category which an APFloat belongs to should be dependent on the
      actual value that the APFloat has, not be arbitrarily passed in by the
      user. This will prevent inconsistency bugs where the category and the
      actual value in APFloat differ.
      
      I also fixed up all of the references to this constructor (which were
      only in LLVM).
      
      llvm-svn: 185095
      03255a16
    • Nadav Rotem's avatar
      Get rid of the unused class member. · 02dd93ec
      Nadav Rotem authored
      llvm-svn: 185086
      02dd93ec
Loading