Fast register pressure tracking currently only takes effect during
bottom up scheduling. Forcing this is a bit faster and simpler for
targets that don't have many scheduling constraints and don't need
top-down scheduling.

llvm-svn: 190014

llvm-svn: 190013

llvm-svn: 190012

than the spec dwarf constants.

llvm-svn: 190011

representation. Don't emit comparisons on them as 'icmp ult'!

llvm-svn: 190010

llvm-svn: 190009

have a certain name, not just the first.  This
is useful if a class method and an instance
method have the same name.

<rdar://problem/14872081>

llvm-svn: 190008

by appending the thread ID to the test packet when
debugserver requires it.

This allows register writing (and, by extension,
expressions) to work on Mac OS X.

llvm-svn: 190007

 * In C, as before, if the "warning flag" is enabled, warnings are produced by
   forcing string literals to have const-qualified types (the produced warnings
   are *not* -Wwrite-strings warnings). However, more recent GCCs (at least 4.4
   onwards) now take -w into account here, so we now do the same.

 * In C++, this flag is entirely sane: it behaves just like any other warning
   flag. Stop triggering -fconst-strings here. This is a bit cleaner, but there's
   no real functionality change except in the case where -Xclang -fno-const-strings
   is also specified.

llvm-svn: 190006

to Method/functions returning ObjC objects. wip.

llvm-svn: 190005

llvm-svn: 190004

llvm-svn: 190003

without a limiting factor.

Update all testcases accordingly.

llvm-svn: 190002

Reapply r189013 (reverted in r189906) now that the underlying issue is fixed and tested (in r189996)

Debug info emission was tripping over an IRGen bug (fixed in r189996)
that was resulting in duplicate emission of static data members of class
templates in namespaces.

We could add more test coverage to debug info for this issue
specifically, but I think the underlying IRGen test is more targeted and
sufficient for the issue.

llvm-svn: 190001

Needs testcase updates.

llvm-svn: 190000

llvm-svn: 189999

llvm-svn: 189998

llvm-svn: 189997

A quirk of AST representation leads to class template static data member
definitions being visited twice during Clang IRGen resulting in
duplicate (benign) initializers.

Discovered while investigating a possibly-related debug info bug tickled
by the duplicate emission of these members & their associated debug
info.

With thanks to Richard Smith for help investigating, understanding, and
helping with the fix.

llvm-svn: 189996

llvm-svn: 189995

llvm-svn: 189994

llvm-svn: 189993

llvm-svn: 189992

If the instruction window is < NumRegs/2, pressure tracking is not
likely to be effective. The scheduler has to process a very large
number of tiny blocks. We want this to be fast.

llvm-svn: 189991

llvm-svn: 189990

llvm-svn: 189989

llvm-svn: 189988

Register pressure tracking is half the complexity of the
scheduler. It's useful to be able to turn it off for compile time and
performance comparisons.

llvm-svn: 189987

'Force' values in registers using the calling convention. Now, we only depend on
the calling convention and that the allocator performs copy coalescing.

llvm-svn: 189985

llvm-svn: 189984

llvm-svn: 189983

I am about to patch this code, and this makes the diff far more readable.

llvm-svn: 189982

llvm-svn: 189981

llvm-svn: 189980

llvm-svn: 189979

llvm-svn: 189978

llvm-svn: 189977

* It was redundant with -flto.
* It was confusing since -uAnythingElse is a different option.
* GCC uses -fuse-linker-plugin, so it was not even a compatibility option.

llvm-svn: 189976

llvm-svn: 189975

llvm-svn: 189974