llvm-svn: 193501

llvm-svn: 193500

llvm-svn: 193499

  - Mark tests as XFAIL:cygming in test/ExecutionEngine/MCJIT/remote.
    Rather to suppress them, I'd like to leave them running as XFAIL.
  - Revert r193472. RecordMemoryManager no longer resolves __main on cygming.

There are a couple of issues.

  - X86 Codegen emits "call __main" in @main for targeting cygming.
    It is useless in JIT. FYI, tests are passing when emitting __main is disabled.
  - Current remote JIT does not resolve any symbols in child context.

FIXME: __main should be disabled, or remote JIT should resolve __main.
llvm-svn: 193498

Patch by Cameron McInally <cameron.mcinally@nyu.edu>

llvm-svn: 193497

llvm-svn: 193496

Patch by Vassil Vassilev.
PR13435

llvm-svn: 193495

PR14039

llvm-svn: 193494

llvm-svn: 193493

PR15447

llvm-svn: 193492

PR17608

llvm-svn: 193491

PR17608

llvm-svn: 193490

llvm-svn: 193489

llvm-svn: 193488

intended for debugging and diagnostic output), just inspect the spelling
to check for specific prefixes in drectve section flags.

In addition to being significantly cheaper and not relying on
a debugging interface, this also avoids creating a temporary string and
binding it to StringRef variable. We then went on to access it after the
memory had been deallocated.

This bug too was caught by ASan. I love ASan so much. =]

llvm-svn: 193487

More important than any performance concerns, the code was dropping the
temporary string on the floor after assigning it to a StringRef, and
then used the StringRef later. Caught by running the LLD tests under
ASan.

llvm-svn: 193486

Registered targets don't matter for Sema tests, this passes fine.

llvm-svn: 193485

llvm-svn: 193484

llvm-svn: 193483

llvm-svn: 193482

llvm-svn: 193481

llvm-svn: 193480

llvm-svn: 193479

llvm-svn: 193478

llvm-svn: 193477

On discussing this with Nick, it looks like the StubAtoms
that contain a lazyImmediate reference kind should be null
and the location needs to be fixed up later with some value
that is an offset into the __LINKEDIT segment.

The drawback is that it allows yaml files with references
that expect a target to be considered without one.

This results in bad yaml files that would need to be handled
in the YAML Reader.

Inorder to fix this, the Stub Atoms use a dummy target such
as itself.

llvm-svn: 193476

Before:
  _versionLabel.text = [
    NSString stringWithFormat:NSLocalizedString(@"version: %@", @"Label"),
    [NSBundle mainBundle].infoDictionary[@"CFBundleShortVersionString"]
  ];

After:
  _versionLabel.text =
      [NSString stringWithFormat:NSLocalizedString(@"version: %@", @"Label"),
          [NSBundle mainBundle].infoDictionary[@"CFBundleShortVersionString"]];

This fixed llvm.org/PR17695.

llvm-svn: 193475

llvm-svn: 193474

The * could otherwise cause shell pathname expansion.

llvm-svn: 193473

llvm-svn: 193472

so try PATH next. Assume it is sane enough to cover the usual system
bash locations too, but the old list is not good enough for NetBSD.

llvm-svn: 193471

llvm-svn: 193470

llvm-svn: 193469

llvm-svn: 193468

Polly can now be compiled without explicitly linking to GMP licensed code.

This patch also contains some formatting improvements.

llvm-svn: 193467

llvm-svn: 193466

If multiprocessing was requested, detected as available and subsequently failed
to initialize it's worth letting the user know about it before falling back to
threads.

This condition can arise in certain OpenBSD / FreeBSD Python versions.

llvm-svn: 193465

Some versions of Python on the builders seem strict about this.

llvm-svn: 193464

This should be a better fix for lit multiprocessing failures, replacing the
OpenBSD and FreeBSD workarounds in r193413 and r193457.

Reference: http://bugs.python.org/issue3770
llvm-svn: 193463

Sema: Emit a nicer diagnostic when IndirectFieldDecls show up inappropriately in non-type template arguments

llvm-svn: 193462