Thanks!
| | G | | ginger...@163.com | ---- Replied Message ---- | From | Eliot Moss<m...@cs.umass.edu> | | Date | 3/10/2023 21:00 | | To | The gem5 Users mailing list<gem5-users@gem5.org> | | Cc | G<ginger...@163.com> | | Subject | Re: [gem5-users] Re: building of different GEM5 binary type | On 3/10/2023 2:18 AM, G via gem5-users wrote: Hello, I build binary of *gem5.opt*firstly output at build/RISCV/gem5.opt, then I build another binary of *gem5.debug*, but seems it's still at build/RISCV dir, looks like all the build outputs shares same directories. Even though I ran both with my workloads an they all worked properly, I'm still not sure if this is expected and would not causing any potential conflicting problems, or shall I specify another output directory for different binary flavor? Entirely normal. Opt builds result in gem5.opt, debug in gem5.debug, and fast in gem5.fast. Note that generated .cc and .hh files are shared, but object files are not - opt generates .o, debug generates .do, and fast generates .fo. All happily co-exist. It's perhaps unusual compared with other software with which I have worked, but it functions just fine and has its own logic. Where you get separate directories is for different ISAs (x86 vs RISCV, for example). Cheers - Eliot Moss
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org
