Page MenuHomePhabricator

[DAGCombine] Initialize the bytes offset vector as INT64_MAX to avoid inference the endian check

Authored by steven.zhang on Jun 5 2019, 3:37 AM.



This is a regression of found by the build bot. This is the narrow down case:

void foo(char *p, char v) {
        p[0] = v;
        p[1] = v;

We have a table ByteOffsets to map the offset in the combined value "v"(the vector index) to the offset in the store address "p" (the vector element value).

In this case, we will have:

ByteOffsets[0] = 0;     // The first byte of "v" is stored to p[0]              
ByteOffsets[0] = 1;     // The first byte of "v" is stored to p[1]

Therefore, at last, ByteOffsets[0] will be set as "1". However, as this vector is created with 2 elements that has "0" as its element default value, therefore, it will look like this:

ByteOffsets[0] = 1; // As described before.
ByteOffsets[1] = 0; // The ctor initialized it as 0.

And this match the endian check, so, we will do the transformation, which is wrong.

Therefore, we need to initialize the default value of the table as INT64_MAX to avoid this issue. In fact, the range of the value is, [-63, 63], as it is offset from the base ("p"). And we can only merge 64 stores at most.

I have run the check-all, llvm testsuite, spec2017, and bootstrap, all are clean.

Diff Detail


Event Timeline

steven.zhang created this revision.Jun 5 2019, 3:37 AM
Herald added a project: Restricted Project. · View Herald TranscriptJun 5 2019, 3:37 AM
Herald added a subscriber: hiraditya. · View Herald Transcript

Do we need an assert anywhere to ensure that the ByteOffsets element has been set to something else?

steven.zhang added a comment.EditedJun 5 2019, 7:04 PM

We cannot have the assertion, as it is possible that, it isn't set to something else(for example, this case). And the isBigEndian() check will fail if it isn't set to something else. However, this is a good point, we could do a check when each element is set, early return if it has been set before.

Address comments. Early return if it has been set before, to make the code more robust.

RKSimon accepted this revision.Jun 9 2019, 2:46 PM

LGTM cheers

This revision is now accepted and ready to land.Jun 9 2019, 2:46 PM

@RKSimon Thank you for your nice review!

recommit the patch together with this one.

This revision was automatically updated to reflect the committed changes.