summaryrefslogtreecommitdiffstats
path: root/clang/test/CodeGenCXX/debug-info-zero-length-arrays.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Revert "DI: LLVM schema change: fold constants into string"Duncan P. N. Exon Smith2014-10-021-2/+2
| | | | | | This reverts commit r218913 while I investigate some bots. llvm-svn: 218917
* DI: LLVM schema change: fold constants into stringDuncan P. N. Exon Smith2014-10-021-2/+2
| | | | | | | | | Update debug info testcases for an LLVM metadata schema change to fold metadata constant operands into a single `MDString`. Part of PR17891. llvm-svn: 218913
* Debug Info: follow-up patch to r189283.Manman Ren2013-08-261-1/+1
| | | | | | | Thanks David for his suggestion. This commit updates testing cases to have more specific CHECKs. llvm-svn: 189286
* Debug Info: add an identifier field to DICompositeType.Manman Ren2013-08-261-1/+1
| | | | | | | Paired with llvm r189282. Update testing cases to handle an extra field for DICompositeType. llvm-svn: 189283
* Simplify/generalize some debug info test casesDavid Blaikie2013-03-191-3/+2
| | | | | | | | | Mostly, try to depend on the annotation comments more so these tests are more legible, brief, and agnostic to schema changes in the future (sure, they're not agnostic to changes to the comment annotations but since they're easier to read they should be easier to update if that happens). llvm-svn: 177457
* Generalize DebugInfo tests by avoiding explicit metadata numbersDavid Blaikie2013-02-021-1/+1
| | | | | | | | | | | | | | | This addresses several (not all) debug info tests that use explicit metadata numbers. Wherever the same number appeared more than once in a test I used a named match to ensure the same number appeared in all those cases (this may still be overly constraining test cases as they may not have actually cared about that relationship). For one-off numbers I just replaced them with an unnamed regex. This may underconstrain poorly written test cases that were interested in checking that certain metadata nodes were related but didn't actually match on all the related nodes numbers. llvm-svn: 174247
* Fix name. The array is unboundED.Bill Wendling2012-12-051-1/+1
| | | | llvm-svn: 169429
* Use the 'count' attribute to calculate the upper bound of an array.Bill Wendling2012-12-041-1/+1
| | | | | | | | | The count attribute is more accurate with regards to the size of an array. It also obviates the upper bound attribute in the subrange. We can also better handle an unbound array by setting the count to -1 instead of the lower bound to 1 and upper bound to 0. llvm-svn: 169311
* Don't test for ASM output but for IR output.Bill Wendling2012-12-041-9/+6
| | | | llvm-svn: 169232
* clang/test/CodeGenCXX/debug-info-zero-length-arrays.cpp: Add explicit ↵NAKAMURA Takumi2012-12-041-1/+1
| | | | | | triple, x86_64-unknown-unknown. It was incompatible to i686. llvm-svn: 169220
* Add a 'count' field to the DWARF subrange.Bill Wendling2012-12-041-0/+16
The count field is necessary because there isn't a difference between the 'lo' and 'hi' attributes for a one-element array and a zero-element array. When the count is '0', we know that this is a zero-element array. When it's >=1, then it's a normal constant sized array. When it's -1, then the array is unbounded. llvm-svn: 169219
OpenPOWER on IntegriCloud