llvm-svn: 100858

llvm-svn: 100856

llvm-svn: 100852

llvm-svn: 100850

llvm-svn: 100849

llvm-svn: 100848

llvm-svn: 100846

a separate function.

llvm-svn: 100845

integrated into the llvm-mc testing tool.

llvm-svn: 100842

llvm-svn: 100841

be sent to LSR, which it isn't prepared to handle.

llvm-svn: 100839

llvm-svn: 100838

forced constant is changed to a constant, we would end
up adding the instruction to the wrong worklist, 
preventing it from being properly revisited.  This fixes
rdar://7832370

llvm-svn: 100837

valid instantiations.

llvm-svn: 100836

destination type for initialization, assignment, parameter-passing,
etc. The main issue fixed here is that we used rather confusing
wording for diagnostics such as

t.c:2:9: warning: initializing 'char const [2]' discards qualifiers,
      expected 'char *' [-pedantic]
  char *name = __func__;
        ^      ~~~~~~~~

We're not initializing a 'char const [2]', we're initializing a 'char
*' with an expression of type 'char const [2]'. Similar problems
existed for other diagnostics in this area, so I've normalized them all
with more precise descriptive text to say what we're
initializing/converting/assigning/etc. from and to. The warning for
the code above is now:

t.c:2:9: warning: initializing 'char *' from an expression of type
      'char const [2]' discards qualifiers [-pedantic]
  char *name = __func__;
        ^      ~~~~~~~~

Fixes <rdar://problem/7447179>.

llvm-svn: 100832

state was being executed too lazily, and the LLVM
assembly syntax for the disassembler was not being
written into the proper disassembler state variable.

llvm-svn: 100830

inputs happen to negate each other.

llvm-svn: 100828

platforms (for this test).

llvm-svn: 100827

llvm-svn: 100825

llvm-svn: 100824

This is still not an ideal solution, but should disable the check for other
targets where the value of O_CREAT is different.

llvm-svn: 100818

llvm-svn: 100817

looking into an alternate fix right now.

llvm-svn: 100816

llvm-svn: 100815

warning. It's not harmful to have such pointless declarations, and GCC
does not diagnose this issue consistently.

llvm-svn: 100814

of c-style arguments. Completes radar 7445205.

llvm-svn: 100813

merge XCore's section into MCSectionELF

llvm-svn: 100812

to avoid memcpy() call is no longer necessary.

llvm-svn: 100811

llvm-svn: 100810

variable declarations.

llvm-svn: 100809

api and update clients to use MCContext instead.

llvm-svn: 100808

the compiler and asmparser now unique to the same sections.  This fixes
rdar://7835021.

llvm-svn: 100807

Fixes PR6752.

llvm-svn: 100806

%RDI<def,dead> = MOV64rr %RAX<kill>, %EDI<imp-def>

llvm-svn: 100804

automatic storage.  This matches the corresponding check for 'dispatch_once()'.

llvm-svn: 100803

llvm-svn: 100802

llvm-svn: 100801

unless they are used.  I discussed this with Daniel Dunbar, and we agreed that this
provides an inconsistent warnings experience for the user and that there were
genuine cases where we wouldn't want to do this optimization.

llvm-svn: 100800

llvm-svn: 100799

unintended behavior.

llvm-svn: 100798