type-nsobject-attribute.m in the dejagnu test suite
in the nonfragile abi mode.

llvm-svn: 64233

in preparation for nonfragile ivar offset work.

llvm-svn: 64225

llvm-svn: 64221

llvm-svn: 64205

llvm-svn: 64203

Function parameters for PIC16 are like local variables. So use the keyword ".auto." to mangle their names. The working of PIC16AsmPrinter relies on that keyword currently.

llvm-svn: 64198

gcc compat test suite results (Darwin x86-32 & -64):
--
# of expected passes		1110
# of unexpected failures	74
# of unresolved testcases	168
# of unsupported tests		2

llvm-svn: 64197

memory representation (e.g., bool).
 - This upgrades (downgrades) MultiSource/Applications/ClamAV/clamscan
   to a miscompile and fixes
   SingleSource/UnitTests/2003-05-31-CastToBool.

llvm-svn: 64194

from LLVM memory type to/from LLVM temporary type.
 - No intended functionality change.

llvm-svn: 64191

ABI.

llvm-svn: 64187

Use the new cleanup infrastructure for VLAs. The next iteration of patches will remove the old Obj-C EH cleanup code.

llvm-svn: 64161

llvm-svn: 64160

llvm-svn: 64159

llvm-svn: 64157

llvm-svn: 64156

to a class template. For example, the template-id 'vector<int>' now
has a nice, sugary type in the type system. What we can do now:

  - Parse template-ids like 'vector<int>' (where 'vector' names a
    class template) and form proper types for them in the type system.
  - Parse icky template-ids like 'A<5>' and 'A<(5 > 0)>' properly,
    using (sadly) a bool in the parser to tell it whether '>' should
    be treated as an operator or not.

This is a baby-step, with major problems and limitations:
  - There are currently two ways that we handle template arguments
  (whether they are types or expressions). These will be merged, and,
  most likely, TemplateArg will disappear.
  - We don't have any notion of the declaration of class template
  specializations or of template instantiations, so all template-ids
  are fancy names for 'int' :)

llvm-svn: 64153

llvm-svn: 64105

llvm-svn: 64100

llvm-svn: 64099

Add a simplified EmitJumpThroughFinally and use it in CGObjC in preparation of making it use the cleanup stack.

llvm-svn: 64098

llvm-svn: 64096

llvm-svn: 64095

If people could beat on it and let me know if there are any new
semantics required by newer language standards or DRs or any little
details I goofed on, I'd be happy to fix any issues found.

llvm-svn: 64079

llvm-svn: 64072

llvm-svn: 64069

llvm-svn: 64068

llvm-svn: 64064

llvm-svn: 64059

llvm-svn: 64053

llvm-svn: 64052

Add support for emitting cleanup blocks. Make EmitCompoundStatement emit cleanup blocks if necessary

llvm-svn: 64051

Add a simple RAII object, to be used for pushing a cleanup entry and make the insertion point be the cleanup block.

llvm-svn: 64048

correctly.  This should lay the ground work to throw the big switch
and start code gening break and continue in the presense of vlas.

llvm-svn: 64046

llvm-svn: 64043

llvm-svn: 64032

llvm-svn: 64031

llvm-svn: 64030

This will allow us to generate break and continue even if vlas are
involved without worry that we'll silently generate bad code.

llvm-svn: 64028

llvm-svn: 64021

llvm-svn: 64020