2552 2012-06-06 22:52:34 +0000 x32: identify workload & collect benchmark data to show value of x32 2018-07-09 01:39:10 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core unspecified x86 Multiple RESOLVED DUPLICATE 4578 Low normal Future 1 nitin.a.kamble anuj.mittal alejandro.hernandez meta.mr.watcher meta.watcher rebecca.swee.fun.chang sgw --- --- Don't know oldest_to_newest 21896 0 nitin.a.kamble 2012-06-06 22:52:34 +0000 We need to identify a workload which can show value of x32 to customers. It will help customers to switch to x32 ABI for production use. 21897 1 nitin.a.kamble 2012-06-06 23:25:20 +0000 spec CPU is coined as a good candidate for this purpose So need to collect data on a real hardware for spec CPU benchmark for x32, i686 & x86-64 ABIs 22130 2 nitin.a.kamble 2012-06-13 14:27:03 +0000 Bogdan, You can use a core i5 system with sugarbay bsp for this work. 27887 3 radu.moisan 2012-12-03 09:46:47 +0000 I will be taking care of this one. Nitin can you give me a hint about the workload for this bug, I need to fill in some estimate to help Song plan stuff for 1.4 I'll go for now with 5days. 27912 4 nitin.a.kamble 2012-12-03 17:10:47 +0000 Radu, The workload is already identified for this purpose. It is Spec CPU as seen in the comment 1 bellow. Now next part is running it in 3 different configurations. 1st with a x86 image, 2nd with x86_64 iamge & 3rd with x32 image. And all this on the same hardware, so that other than the ABI all other parameters are the same. Also you need to collect 3 sets of the same data, to understand any variation in the collected data. I am changing the title of this bug to reflect the current work involved. And I think 5 days will be highly optimistic estimate. If you don't encounter any build or runtime issues, then 5 days may be right. But I am not sure the current state of x32 support. If the current x32 support is broken then that need to be fixed 1st. Any way, you can open bugs for such blocking issues and mark this bug dependent on those. so you can go with the 5 days or add 1 or 2 more days to be more safe. I am also sending you instructions I received from HJ Lu for obtaining the benchmark files. Nitin 27938 5 radu.moisan 2012-12-04 07:47:24 +0000 thanks Nitin, I'm going with 6 days and update appropriately once I get into the problem. 71456 6 sgw 2017-03-20 17:08:20 +0000 This could be similar to phoronix work also 81042 7 anuj.mittal 2018-07-09 01:39:10 +0000 Duplicate of 4578. *** This bug has been marked as a duplicate of bug 4578 ***