StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1673385
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-11-04T12:06:12.777
FavoriteCount
0
LastActivityDate
2009-11-04T12:18:59.847
LastEditDate
2009-11-04T12:18:59.847
LastEditorUserId
201633
OwnerUserId
201633
ParentId
1516622
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
Vectorization need not be limited to single register which can hold large data. Like using '128' bit register to hold '4 x 32' bit data. It depends on architectural limitations. Some architecture have different execution units which have registers of their own. In that case, a part of the data can be fed to that execution unit and the result can be taken from a register corresponding to that execution unit. For example, consider the below case. <blockquote> for(i=0; i < N; i++) { a[i] = a[i] + b[i]; } </blockquote> If I am working on an architecture which has two execution units, then my vector size is defined as two. The loop mentioned above will be reframed as <blockquote> for(i=0; i<(N/2); i+=2) { a[i] = a[i] + b[i] ; a[i+1] = a[i+1] + b[i+1]; } NOTE: The 2 inside the for statement is derived from the vector size. </blockquote> As I am having two execution units the two statements inside the loop will be fed into the two execution units. The sum will be accumulated in the execution units separately. Finally the sum of accumulated values (from two execution units) will be carried out. The good practices are 1. The constraints like dependency (between different iterations of the loop) needs to be checked before vectorizing the loop. 2. Function calls needs to be prevented. 3. Pointer access can create aliasing and it needs to be prevented. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat does vectorization mean?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USGanesh Gopalasubramanian
UserOwnerUserId
1. USGanesh Gopalasubramanian
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
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.