Re: [Gems-users] Problem building GEMS 2.0 for x86 target

[Jayaram Bobba <bobba@xxxxxxxxxxx>]

GEMS 2.0 has the necessary changes to port Ruby (without LogTM features) 
to x86. However the port had some bugs.
We have incorporated fixes in the forthcoming version (which will be 
released soon).
Meanwhile, you could comment out the troublesome lines of code or use 
macros to remove those lines for x86. For eg.,
#ifdef SPARC
typedef v9_memory_transaction_t memory_transaction_t;
#else
typedef x86_memory_transaction_t memory_transaction_t;

I believe the SPARC specific features that throw up errors are used only 
by LogTM.
So commenting them out should be safe if you only use non-LogTM features 
on x86.
Jayaram

Dan Gibson wrote:
> I would suggest using GEMS 2.0 and manually porting Ruby to x86. It is 
> really not all that difficult, and the x86 patch for the prior version 
> makes a pretty good guide.
> Regards,
> Dan
>
> divya ramakrishnan wrote:
> > Hi,
> >
> > I am using GEMS 2.0 with Simics 3.0.30. I was able to compile and 
> > load ruby with the target as SPARC. But when I try it for a x86 
> > target I get the following error  in ruby/simcis/SimicsProcessor.C. I 
> > made the changes for x86 in the common/Makefile_simicsversion
> >  simics/SimicsProcessor.C: In member function `CacheRequestType 
> > SimicsProcessor::getRequestType(const 
> > memory_transaction_t*)':simics/SimicsProcessor.C:650: error: 'const 
> > struct x86_memory_transaction' has no member named 'address_space'
> > simics/SimicsProcessor.C:687: error: `SIMICS_is_ldda' was not 
> > declared in this scope
> > make[1]: *** 
> > [amd64-linux/generated/MOESI_CMP_token/obj/SimicsProcessor.o] Error 1
> > make[1]: Leaving directory `/home/simics/GEMS/gems-2.0/ruby'
> > make: *** [all] Error 2
> >
> > I know there is a patch for SPARC to x86 target on the website, but 
> > that is under version 1.1. The files replaced by the patch are for 
> > the previous version of GEMS. Those files do not have some changes 
> > that have been made in the 2.0 version. Is there a patch for the 
> > conversion in GEMS 2.0? Or should I manually read the files in the 
> > patch and make the changes to the 2.0 version?
> > Please help me out with this problem.
> >
> > Thank you,
> > Divya Ramakrishnan
> > University of Cincinnati
> >
> >
> > ------------------------------------------------------------------------
> > Get the freedom to save as many mails as you wish. Click here to know 
> > how. 
> > <http://in.rd.yahoo.com/tagline_mail_5/*http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/> 
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Gems-users mailing list
> > Gems-users@xxxxxxxxxxx
> > https://lists.cs.wisc.edu/mailman/listinfo/gems-users
> > Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/"; to your search.
> >
> >   
> --
> http://www.cs.wisc.edu/~gibson [esc]:wq!
>   
> ------------------------------------------------------------------------
> _______________________________________________
> Gems-users mailing list
> Gems-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
> Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/"; to your search.
>
>