- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi guys,
I've tried the objdump on x86 and /usr/linux-k1om-4.7/bin/x86_64-k1om-linux-objdump to disassemble a program for Xeon Phi with/without the option --archietecture=l1om. However, the specific instructions for k1om can not be resolved.
I also cross-compiled a binutils tool train for Xeon Phi, and ran the objdump on mic(with or w/o --archietecture=l1om), but the result was the same.
Can anyone help, please?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I got it.
/usr/linux-k1om-4.7/bin/x86_64-k1om-linux-objdump with --architecture=k1om works.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It is not entirely clear what issue you faced and whether --architecture option is necessary and having any affect when using the appropriate /usr/linux-k1om-4.7/bin/x86_64-k1om-linux-objdump command.
The l1om machine architecture was created for the Larrabee implementation and for Xeon Phi™ the machine designation uses Intel k1om. Even when using the x86_64-k1om-linux-objdump on an object file created by the Intel C++/Fortran compilers with the -mmic option, --architecture=l1om does not yield the correct disassembly.
I realize you perhaps have moved past your issue but we want to ensure an understanding for everyone about what is or is not needed with x86_64-k1om-linux-objdump in terms of any --architecture option.
To help us better understand your issue, if you could possibly recreate your earlier problem, then for the object file in question can you execute the command readelf -h on the file and then paste that output into a reply?
Thank you.

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page