e a good way to handle this correctly. But maybe Joseph has an idea.
>
> Richard.
>
> > On Mon, Jan 11, 2021 at 12:50 AM Richard Biener <
> richard.guent...@gmail.com> wrote:
> >>
> >> On Sat, Jan 9, 2021 at 12:24 AM Tucker Kern via Gcc
> wrote:
> &
space. This doesn't feel like a far fetched idea as GCC currently supports
address space specific legitimization and modes.
On Mon, Jan 11, 2021 at 12:50 AM Richard Biener
wrote:
> On Sat, Jan 9, 2021 at 12:24 AM Tucker Kern via Gcc
> wrote:
> >
> > Hi,
> >
Hi,
I'm implementing named addresses spaces for a Harvard architecture machine
to support copying data from instruction memory to data memory. This is
achieved via a special instruction. e.g. think AVR and progmem/__flash.
However, the instruction memory is narrower than the data memory (12 vs 16
iated!
-Tucker
On Tue, Oct 13, 2020 at 3:00 AM Richard Sandiford
wrote:
> Tucker Kern via Gcc writes:
> > TL;DR
> >
> > In GCC 9.3, I believe modified_between_p should return 1 if the memory
> > reference is volatile. My layman's understanding of volatile memory
TL;DR
In GCC 9.3, I believe modified_between_p should return 1 if the memory
reference is volatile. My layman's understanding of volatile memory is that
it could change at any time, and thus could be modified between any two
instructions.
Possible patch:
diff --git a/gcc/rtlanal.c b/gcc/rtlanal.c
