This is already there, try using __attribute__((mode(DI) )).
-- Pinski

-

Hmm, unless this is a new feature in 4.3, I can't seem to get this to work on

either i386 (using mode DI) or x86-64 (using mode SI). Could you clarify? If

this worked consistently on at least all 64-bit architectures, I would have a

use for it in the kernel (cutting down the kernel size by perhaps several

pages). Btw., I continue to think that the error message 'initializer element

is not computable at load time' on 64-bit code like this
extern char array[];

unsigned int p = (unsigned long)array;
or 32-bit code like this
extern char array[];

unsigned long long p = (unsigned long)array;
is incorrect - the compiler generally has no knowledge what 'array' is (it may

know whether the architecture is generally capable of expressing the

necessary relocation, but if 'array' is really a placeholder for an assembly

level constant, possibly even defined through __asm__() in the same

translation unit, this diagnostic should at best be a warning). I'm pretty

sure I have an open bug for this, but the sad thing is that bugs like this

never appear to really get looked at.
Thanks, Jan
--

This only works when you add support for the different pointer modes.

I was saying the middle support for this feature was already there,

just the target support was not.
Also there are issues with mode on pointers for C++, I don't know what

they are though.
Note this feature is used on the s390 target and also the ia64-hpux targets.

--Pinski

--