Another question/clarification: Does any data actually get shared between the two rename modes? I think you said there is not, but now I can't find that. Would it work just as well to have two register files which operate entirely independently? From what I can tell the "V" registers of Neon in aarch64 overlap with the SVE registers, and the "Q" registers of armv7 Neon overlap with the "S", "D", "Q" registers of the same, but I think "V" and "Q" are independent? Maybe reused but not guaranteed to alias?
BTW, test cases would be very helpful if possible. I've made good progress cleaning away debris and am getting to the point where I'll want to make changes which I'm a lot less comfortable making blind. Gabe On Thu, Feb 25, 2021 at 10:40 PM Gabe Black <[email protected]> wrote: > I will ask within Arm if there's something we can provide to you. >>> In the meantime I gave a quick look at NEON enabled libraries [1]; the >>> Ne10 library provides a set of functions optimized for NEON and a set >>> of examples making use of it [2] (e.g FIR filter, GEMM etc etc). >>> >>> You could probably cross-compile those examples and use them in SE mode >>> (recommending to use the O3 model) >>> >> >> >> Ok, thanks, I'll take a look. This might even be something we want in the >> testing infrastructure? I might look into that when I have a chance. >> > > I took a look at this, and unfortunately I don't think I can use it. The > example only builds for armv7 and not aarch64, and when I tried to build it > for armv7 I get a bunch of compiler errors. Do you have any other > suggestions? > > Gabe > >>
_______________________________________________ gem5-dev mailing list -- [email protected] To unsubscribe send an email to [email protected] %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
