Hi there,
I maintain a GCC port for a small 16 bit processor called XAP2+. I'm
having problems with strings of wide characters.
I have the following defines, among others:
#define BITS_PER_UNIT 16
...
#define WCHAR_TYPE "int"
#define WCHAR_TYPE_SIZE 16
So, I'm ex
On Fri, Mar 30, 2007 at 09:52:22AM -0700, Richard Henderson wrote:
> I think the problem is that we've not told libcpp what the correct
> narrow character set is. I suggest adding something like
>
> if (BITS_PER_UNIT >= 32)
> cpp_opts->narrow_charset = BYTES_BIG_ENDIAN ? "UTF-32BE" : "UTF-
Hi all.
I'm working on a GCC backend for a small embedded processor. We've got a
Harvard architecture with 16 bit data addresses and 24 bit code
addresses. How well does GCC support having different sized pointers for
this sort of thing? The macros POINTER_SIZE and Pmode seem to suggest
that ther
Paul Schlie wrote:
With the arguable exception of function pointers (which need not be literal
address) all pointers are presumed to point to data, not code; therefore
may be simplest to define pointers as being 16-bits, and call functions
indirectly through a lookup table constructed at link time
Paul Schlie wrote:
the target ports are in gcc/config/...
Sure, I mean which target should I be looking at?
Ned.
**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or
Julian Brown wrote:
FWIW, a port I did used indirection for all function pointers, albeit
for a different reason, and I can report that it seems to work OK in
practice with a little linker magic. It wasn't really production-quality
code though, I admit.
Perhaps the indirection table can safely hold
