llvm-svn: 203017

llvm-svn: 203016

On cores without fpcvt support, we cannot promote int_to_fp i1 operations,
because there is nothing to promote them to. The most straightforward
implementation of this uses a select to choose between the two possible
resulting floating-point values (and that's what is done here).

llvm-svn: 203015

Updating this test case to appease build bots which support ANSI escape sequences (unlike my dev box).

llvm-svn: 203014

llvm-svn: 203013

Capabilities are required to pass a name specifying what type of capability is being annotated. There are currently only two supported names: mutex and role. Adding functionality to check for the capability name and diagnose when it's unexpected.

Note that for backwards compatibility, an unnamed capability will default to being a "mutex." This allows the deprecated lockable attribute to continue to function.

llvm-svn: 203012

llvm-svn: 203011

Using a //net/ path to hopefully avoid problems with non-absolute paths
on Windows.

llvm-svn: 203010

Provide triple and data layout as well as module names (or empty string) when there's a mismatch.

Differential Revision: http://llvm-reviews.chandlerc.com/D2971

llvm-svn: 203009

Fixes PR19045.

llvm-svn: 203008

Fixes pr19007.

llvm-svn: 203007

the module build stack for the module being built, so we can correctly detect
recursive module builds.

llvm-svn: 203006

whether it's part of a module.

llvm-svn: 203005

llvm-svn: 203004

llvm-svn: 203003

llvm-svn: 203002

Before llvm-mc would print it, but llc was assuming that it would produce
another section changing directive before one was needed. That assumption is
false with inline asm.

Fixes PR19049.

Another option would be to always create the section, but in the asm printer
avoid printing sections changes during initialization. That would work, but
* We do use the fact that llvm-mc prints it in testing. The tests can be changed
  if needed.
* A quick poll on IRC suggest that most developers prefer the implicit .text to
  be printed.

llvm-svn: 203001

llvm-svn: 203000

When using a //net/ path, we were transforming the trailing / into a '.'
when the path was just the root path and we were iterating backwards.
Forwards iteration and other kinds of root path (C:\, /) were already
correct.

llvm-svn: 202999

llvm-svn: 202998

llvm-svn: 202997

llvm-svn: 202996

llvm-svn: 202995

Implement LWG 2193. Default constructors for standard library containers are explicit. Note that libc++ already did this for string/deque/forward_list/list/vector and the unordered containers; implement it for set/multiset/map/multimap. Add tests for all the containers. Two drive-by fixes as well: add a missing explicit in <deque>, and remove a tab that snuck into a container test. This issue is also LLVM bug 15724, and resolves it.

llvm-svn: 202994

Scope lives in Sema and cannot be used in AST. Shuffle things around.

llvm-svn: 202993

Originally committed in r202985.

llvm-svn: 202992

llvm-svn: 202991

Remove definition of std::fmaf from libc++. Fixes bug #18910. This function should come from the C standard library. As a drive-by fix, update the tests to remove a warning from -Wabsolute-value

llvm-svn: 202990

[C++11] Using std::unique_ptr to ensure that Argument objects do not leak (since clang-tblgen isn't long-lived, the old leak is probably acceptable, but it offended my senses nonetheless).

llvm-svn: 202989

The build was failing with:

  error C2664: 'std::atomic_int::atomic_int(const std::atomic_int &)' : cannot convert argument 1 from 'int' to 'const std::atomic_int &'

Apparently "std::atomic_int x(0)" doesn't work, but "std::atomic<int> x(0)"
does.

llvm-svn: 202988

llvm-svn: 202987

Allow trivial read-only filesystems such as RealFileSystem to be shared
between threads.

llvm-svn: 202986

llvm-svn: 202985

A version of RefCountedBase that uses std::atomic_int to store its
reference count.

llvm-svn: 202984

llvm-svn: 202983

llvm-svn: 202982

llvm-svn: 202981

llvm-svn: 202980

llvm-svn: 202979

llvm-svn: 202978