Skip to content
  1. Jul 03, 2013
    • Eric Christopher's avatar
      addConstantValue, addConstantFPValue never returned anything but · 78fcf490
      Eric Christopher authored
      true, so remove the return value and propagate accordingly.
      
      llvm-svn: 185490
      78fcf490
    • Manman Ren's avatar
      Trying to fix the bots · 94119cee
      Manman Ren authored
      llvm-svn: 185489
      94119cee
    • Greg Clayton's avatar
      Import the builtin type prefix before we import the user expression prefix so... · ddf976aa
      Greg Clayton authored
      Import the builtin type prefix before we import the user expression prefix so that the user expression prefix can use the uint, int, size_t, and other types without having to define them.
      
      llvm-svn: 185488
      ddf976aa
    • Kaelyn Uhrain's avatar
      Allow typo correction to try removing nested name specifiers. · 10413a46
      Kaelyn Uhrain authored
      The removal is tried by retrying the failed lookup of a correction
      candidate with either the MemberContext or SS (CXXScopeSpecifier) or
      both set to NULL if they weren't already. If the candidate identifier
      is then looked up successfully, make a note in the candidate that the
      SourceRange should include any existing nested name specifier even if
      the candidate isn't adding a different one (i.e. the candidate has a
      NULL NestedNameSpecifier).
      
      Also tweak the diagnostic messages to differentiate between a suggestion
      that just replaces the identifer but leaves the existing nested name
      specifier intact and one that replaces the entire qualified identifier,
      in cases where the suggested replacement is unqualified.
      
      llvm-svn: 185487
      10413a46
    • Kaelyn Uhrain's avatar
      Look for corrections in enclosing namespaces that require a global NestedNameSpecifier. · b18b0c0f
      Kaelyn Uhrain authored
      CorrectTypo will now see and consider those corrections that are effectively
      shadowed by other declarations in a closer context when resolved via an
      unqualified lookup. This involves adding any parent namespaces to the set of
      namespaces as fully-qualified name specifiers, and also adding potential
      corrections that passed name lookup but were rejected by the given
      CorrectionCandidateCallback into the set of failed corrections that should be
      tried with the set of namespace specifiers.
      
      llvm-svn: 185486
      b18b0c0f
    • Manman Ren's avatar
      Debug Info: use module flag to set up Dwarf version. · ac8062bb
      Manman Ren authored
      Correctly handles ref_addr depending on the Dwarf version. Emit Dwarf with
      version from module flag.
      
      TODO: turn on/off features depending on the Dwarf version.
      llvm-svn: 185484
      ac8062bb
    • Manman Ren's avatar
      Debug Info: set default to gdwarf-2 for Darwin. · 38db0920
      Manman Ren authored
      Darwin systems currently do not support dwarf version 3 or above. When we are
      ready, we can bump the default to gdwarf-4 for Darwin.
      
      For other systems, the default is dwarf version 3, if everything goes smoothly,
      we can bump the version to 4.
      
      rdar://13591116
      
      llvm-svn: 185483
      38db0920
  2. Jul 02, 2013
Loading