Is it possible to make any tree visible to GCC (ie. BIND_EXPR) or it must
be specific tree type like tree_common? How would the code for adding
BIND_EXPR look, if vec_safe_push() doesn't work?
Thanks,
Martin
If a target (rl78-elf in my case) has a named address space larger
than the generic address space (__far in my case), why is pointer math
in that named address space still truncated to sizetype?
N1275 recognizes that named address spaces might be a different size
than the generic address space, b
Snapshot gcc-4.9-20141203 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.9-20141203/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.9 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
On Wed, 3 Dec 2014, DJ Delorie wrote:
> If a target (rl78-elf in my case) has a named address space larger
> than the generic address space (__far in my case), why is pointer math
> in that named address space still truncated to sizetype?
>
> N1275 recognizes that named address spaces might be a
> However, pointer subtraction still returns ptrdiff_t, and sizeof still
> returns size_t,
Why?
On Wed, 3 Dec 2014, DJ Delorie wrote:
> > However, pointer subtraction still returns ptrdiff_t, and sizeof still
> > returns size_t,
>
> Why?
Well, TR 18037 doesn't do anything to change that, so if you define some
target-specific way to use different types in certain circumstances then
you'r
