- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The byte code of `vgatherdps zmm0{k1}, [rax + zmm0]` is 62F27D49920400.
But
>xed -d 62F27D49920400
>62F27D49920400
>ERROR: GATHER_REGS Could not decode at offset: 0x0 PC: 0x0: [62F27D499204000000000000000000]
The reason of this error may be that the index and the destination registers are the same and it results a UD fault.
But -d option is not to emutate the byte code but to decode one instruction, so I expect that xed shows the result of disassemble.
How about it?
verions of xed.
>Copyright (C) 2017, Intel Corporation. All rights reserved.
>XED version: [8.15.0-6-gb862fe0]
- Tags:
- Intel® Advanced Vector Extensions (Intel® AVX)
- Intel® Streaming SIMD Extensions
- Parallel Computing
Link Copied
4 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
A #UD is not a valid instruction so there is technically nothing to decode or disassemble here.
FWIW, I did try to give a helpful error indicator for this case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you. I see.
I would be happy if xed shows a helpful message in the same way that shows ud2 for 0f0b.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
UD2 is an instruction, that is different. You have a helpful error message already: "ERROR: GATHER_REGS"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
>You have a helpful error message already: "ERROR: GATHER_REGS"
I see. My understanding was wrong.

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