From: Tucker Kern <tuckkern@gmail.com>
To: Tucker Kern via Gcc <gcc@gcc.gnu.org>
Subject: Adjust offset of array reference in named address space
Date: Fri, 8 Jan 2021 16:23:19 -0700 [thread overview]
Message-ID: <CAAKLm8ZCRpJX8ekfQZSc6Eep=eJbjraRk1QvyAm4XZssF2jwOw@mail.gmail.com> (raw)
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
bits) on this machine. So a single data word is split across 2 instruction
words. When copied from IMEM to DMEM the two parts are combined via SHIFT +
OR patterns.
This is all working fine for regular variables (i.e. int som_var), but it
falls apart for array references (i.e. some_array[1]). Since the data is
stored across 2 IMEM words, I need to scale the calculated offset of each
array reference by 2. e.g. array[0] is actually stored in imem[0] & imem[1]
and array[1] is stored in imem[2] & imem[3].
e.g.
static __imem int imem_array[2];
return imem_array[1];
// needs to generate a symbol reference like
&imem_array.869+2
Similarly if the array index was a function parameter, I need to scale the
parameter by 2.
__imem int imem_array[2];
int some_func(int a)
{
// a needs to be scaled by 2 when generating RTL/ASM
return imem_array[a];
}
I haven't found any target hooks that would allow me to override the offset
calculation. Originally I thought I could handle it in a splitter but this
approach didn't work for the function parameter example as I ended up
scaling the entire address instead of just the offset.
I had another thought of using a combo of
TARGET_ADDR_SPACE_LEGITIMIZE_ADDRESS and
TARGET_ADDR_SPACE_LEGITIMATE_ADDRESS_P to scale the offset and mark it as
adjusted but I don't think this combo will work in the end.
Is there any way to achieve this?
Thanks,
Tucker
next reply other threads:[~2021-01-08 23:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 23:23 Tucker Kern [this message]
2021-01-11 7:49 ` Richard Biener
2021-01-12 15:28 ` Tucker Kern
2021-01-12 15:37 ` Richard Biener
2021-01-14 3:56 ` Tucker Kern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAKLm8ZCRpJX8ekfQZSc6Eep=eJbjraRk1QvyAm4XZssF2jwOw@mail.gmail.com' \
--to=tuckkern@gmail.com \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).