> For the record, I have not been
able to get GEMS to work
> "just fine" with Simics 3.x. The main issue is the versions
> of compilers used to compile and link GEMS vs. what's used
> for Simics.
>
> I know others have had success, but my experience has not
> been good. I was hoping to make the move to 3.0 for my
> class this semester, but I ended up sticking with 2.x.
>
> So I'm unhappy to see 2.x go away, but I understand why and
> hopefully will figure out a way to work around it.
>
> ...Greg
>
> PS. I found the right mix of compilers to get everything to
> link, but then ruby0.init crashes immediately with a bad
> address passed to free(). If anyone has seen similar
> behavior and figured out a fix, let me know. I'm somewhat
> constrained by a university computing environment that's
> largely out of my control, so please don't send me fixes
> like "reinstall Linux with this patch."
>
>
>
> Abdullah Kayi wrote:
> > Hi Dan,
> >
> > FYI, Virtutech already suspended new Simics 2.x
licenses. However, as
> > you mentioned Simics 3.x works fine with GEMS, the only
problem
> would be
> > the checkpoint scripts.
> >
> > Regards,
> >
> > AK
> >
> > On 2/2/09 11:52 AM, "Dan Gibson" <
degibson@xxxxxxxx