llvm-svn: 76401

doesn't cause ".no_dead_strip" to be emitted on darwin.

llvm-svn: 76399

llvm-svn: 76397

llvm-svn: 76390

"private" symbols which the assember shouldn't strip, but which the linker may
remove after evaluation. This is mostly useful for Objective-C metadata.

This is plumbing, so we don't have a use of it yet. More to come, etc.

llvm-svn: 76385

llvm-svn: 76384

being more consistent with other backends, this makes the SPARC backend 
deal with functions with arguments with illegal types correctly, which 
fixes some tests in test/CodeGen/Generic.

llvm-svn: 76375

llvm-svn: 76374

Inline asm instructions may have additional <imp-def,kill> register operands.
These operands are not marked with a flag like the normal asm operands, so we
must not assert that there is a flag.

llvm-svn: 76373

return the smallest union of two ranges instead of just any range that happens
to contain the union.

llvm-svn: 76360

llvm-svn: 76356

llvm-svn: 76354

copied from the SystemZ target.  I don't think this causes any 
significant changes to the output (I compared the assembly, and the 
results appeared to be essentially unchanged), although I don't actually 
have an Alpha to test on.

I would appreciate if anyone with the appropriate hardware could test 
this. I'm not sure if that includes anyone subscribed to llvm-commits, 
though.

llvm-svn: 76353

 - What it doesn't have is the rest of its cmake files...

llvm-svn: 76352

 - We should canonicalize this and get rid of the cmake and llvm-config hacks to
   support both variants.

llvm-svn: 76350

 - Shouldn't really be necessary, but currently .inc files get included into
   some main target headers.

llvm-svn: 76349

Use R_X86_64_32S to handle Jump Table Index relocation entries. Hide TAI usage inside getSection* functions

llvm-svn: 76347

llvm-svn: 76346

insertelement/extractelement.

I'm not entirely sure this is precisely what we want to do: should we 
prefer bitcast(insertelement) or insertelement(bitcast)?  Similarly. should we 
prefer extractelement(bitcast) or bitcast(extractelement)?

llvm-svn: 76345

llvm-svn: 76344

Implemented by moving the code out of static functions into methods of Program
class.

llvm-svn: 76340

llvm-svn: 76334

Use proper relocation type to build relocations for JumpTables (rodata
sections).

llvm-svn: 76326

way (bitcast -> insert/extractelement).

llvm-svn: 76325

llvm-svn: 76324

llvm-svn: 76316

llvm-svn: 76315

llvm-svn: 76314

llvm-svn: 76313

llvm-svn: 76312

llvm-svn: 76311

llvm-svn: 76310

sign bit set.

llvm-svn: 76304

llvm-svn: 76302

llvm-svn: 76301

bitcasts.

It would also be possible to canonicalize the other way; does anyone 
have a preference?

llvm-svn: 76300

where int is 32 bits.

llvm-svn: 76293

all values belonging to the intersection will belong to the resulting range.
The former was inconsistent about that point (either way is fine, just pick
one.) This is part of PR4545.

llvm-svn: 76289

which cannot be folded even if they have constant operands. Significantly
helps if_spppsubr.c attached to PR4573.

llvm-svn: 76285

llvm-svn: 76284