StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18193402
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-08-12T17:49:02.580
FavoriteCount
0
LastActivityDate
2013-08-13T05:35:57.640
LastEditDate
2013-08-13T05:35:57.640
LastEditorUserId
948909
OwnerUserId
948909
ParentId
18192750
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
<pre><code>XOR CX, CX ;0x31 0xC9 </code></pre> Uses only two bytes: opcode <code>0x31</code> and ModR/M byte that stores source and destination register (in this case these two are same). <pre><code>MOV CX, 0 ;0xB8 0x08 0x00 0x00 </code></pre> Needs more bytes: opcode <code>0xB8</code>, ModR/M for destination (in this case CX) and two byte immediate filled with zeroes. There is no difference from clocking perspective (both take only one clock), but <code>mov</code> needs 4 bytes while <code>xor</code> uses only two. <pre><code>OR AX, AX ;0x0A 0xC0 </code></pre> again uses only opcode byte and ModRM byte, while <pre><code>CMP AX, 0 ;0x3D 0x00 0x00 <-- but usually 0x3B ModRM 0x00 0x00 </code></pre> uses three or four bytes. In this case it uses three bytes (opcode <code>0x3D</code>, word immediate representing zero) because x86 has special opcodes for some operations with Accumulator register, but normally it would use four bytes (opcode, ModR/M, word immediate). It's again the same when talking about CPU clocks. There's no difference to processor when executing <pre><code>AND AL, 0x0F ;0x24 0x0F <-- again special opcode for Accumulator </code></pre> and <pre><code>SUB AL, '0' ;0x2D 0x30 0x00 <-- again special opcode for Accumulator </code></pre> (only one byte difference), but when you substract ASCII zero, you can't be sure that there won't remain value greater than <code>9</code> in Accumulator. Also anding sets <code>OF</code> and <code>CF</code> to zero, while <code>sub</code> sets them according to the result <code>AND</code>ing can be safer, but my personal opinion is that this usage depends on context. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POIs there some benefit in the following assembly commands?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USuser35443
UserOwnerUserId
1. USuser35443
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POIs there some benefit in the following assembly commands?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.