Hi Wenqi. The updated libm5.a should be used in basically the same way as the old version. Just link against the library, include the header file, and call into the op you want using the normal function call syntax.
Hoa, the documentation you've linked to is a little out of date. How can it be updated? Gabe On Sun, Oct 25, 2020 at 9:31 PM Hoa Nguyen via gem5-users < gem5-users@gem5.org> wrote: > Hi Wenqi, > > We have some documentation about the new m5 utility here: > https://www.gem5.org/documentation/general_docs/m5ops/ > > The following link is an example of annotating PARSEC: > https://github.com/darchr/parsec-benchmark/commits/gem5-20-annotations > > Regards, > Hoa Nguyen > > On 10/25/20, wqyin--- via gem5-users <gem5-users@gem5.org> wrote: > > Hello all, > > > > I noticed the util/m5 has big changes since this > > commit:26454e8072e607d54ac67c42b33355d7c94d6d60 around Apr 27. I am > > wondering how should I use this new interface/implementation to call > > m5ops in my program? Shall I also instantiate a default CallType and > > then use it to obtain the dispatch table and finally pass it to > > Command::run? Also is there any examples which use the new > > implementation to annotate any benchmarks running inside gem5? Thanks > > > > Best, > > > > Wenqi > > > > > _______________________________________________ > gem5-users mailing list -- gem5-users@gem5.org > To unsubscribe send an email to gem5-users-le...@gem5.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s >
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
