This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: ADDR_SPACE_CONVERT_EXPR always expanded to 0?

From: DJ Delorie <dj at redhat dot com>
To: Richard Biener <richard dot guenther at gmail dot com>
Cc: avr at gjlay dot de, gcc at gcc dot gnu dot org
Date: Tue, 12 Mar 2013 13:04:12 -0400
Subject: Re: ADDR_SPACE_CONVERT_EXPR always expanded to 0?
References: <5139EE3D.3030406@gjlay.de> <CAFiYyc1w_H_hpg7SnYGnW-xUTvq+PGdg4eWLevQb7yWAkpFCeg@mail.gmail.com> <CAFiYyc1SVS7Q80X8Fh_BV+7S0=3FDPo=sa5cyc8U8tTY2myUvA@mail.gmail.com> <513A0BDA.6030207@gjlay.de> <CAFiYyc3zU3c-Bq8VMf2DBtCBGRtbXtHY3SaSm0-=B1Lj9==yrQ@mail.gmail.com> <513E06B9.4070102@gjlay.de> <CAFiYyc3tOt8zKbe1ZReDY2qyueFYE3WZXj19piymAUScOjoFow@mail.gmail.com>

> A quick grep shows not many targets would be affected, AVR, m32c, rl78 and spu.
> You should work with the maintainers of those targets to see which approach
> would be the best.

For both m32c and rl78, one address space is a strict subset of the
other (16-bit "near" vs 20/24/32-bit "far" pointers, that's all) so
nothing magic there.

References:
- ADDR_SPACE_CONVERT_EXPR always expanded to 0?
  - From: Georg-Johann Lay
- Re: ADDR_SPACE_CONVERT_EXPR always expanded to 0?
  - From: Richard Biener
- Re: ADDR_SPACE_CONVERT_EXPR always expanded to 0?
  - From: Richard Biener
- Re: ADDR_SPACE_CONVERT_EXPR always expanded to 0?
  - From: Georg-Johann Lay
- Re: ADDR_SPACE_CONVERT_EXPR always expanded to 0?
  - From: Richard Biener
- Re: ADDR_SPACE_CONVERT_EXPR always expanded to 0?
  - From: Georg-Johann Lay
- Re: ADDR_SPACE_CONVERT_EXPR always expanded to 0?
  - From: Richard Biener

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]