https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90812
--- Comment #3 from Jozef Lawrynowicz <jozefl.gcc at gmail dot com> --- (In reply to Richard Biener from comment #2) > I think most tests like this end up using 'long long' and use > __SIZEOF_LONG_LONG__ to guard code. There's a dejagnu effective target for > long long support. The problem is that the effective target keyword that checks that long long is 64-bits, also checks that int and long are 32-bits: > llp64 Target has 32-bit int and long, 64-bit long long and pointers. msp430-elf has 16-bit int, 32-bit long and 64-bit long long. And whilst almost all targets have 64-bit long long, avr can have 32-bit long long in one configuration. So I think an effective target to solely check that __INT64_TYPE__ is supported would be useful. I prefer this to guarding the code with sizeof(long long), as with "dg-require-effective target int64type", the testsuite will recognize the test is unsupported, rather than doing nothing and passing.
