|
From: Philippe W. <phi...@sk...> - 2015-03-29 21:15:50
|
On Sun, 2015-03-29 at 22:46 +0200, Florian Krohm wrote: > Julian can give the full history. > There is plenty of evidence that the original VEX design goal was to > support host != guest. But when I began looking at V code in 2006 the > code wasn't clean in that respect. And it hasn't gone any better. > Here is a quote from Julian from Dec 2014 clarifying: > > This guest-vs-host stuff is still partly alive as a result of a > hope I had that someone might want to do a cross-valgrind one day, > eg ARM32 guest on AMD64 host. But it's been 12+ years and I've > never once heard any mention of such a thing. So perhaps it's > time to give up on that one. > > I think that settles your question :) Yes :). > > > If VEX host and guest are in any case supposed to be the same, > > then solution 1 is the easiest. > > Yes. > > It's funny.. I looked at this very same issue a few weeks back but could > not figure out the autotools stuff. > Note, though, that we still want to compile all VEX sources and not just > the ones pertaining to the current architecture. Yes, for sure, that is the idea. I am busy now doing the solution 1. I have already eliminated s390 :). Philippe |