This is an archive of the discontinued LLVM Phabricator instance.

[OpenMP] Update CHECK-DAG usage in for_codegen.cpp
ClosedPublic

Authored by jdenny on Nov 20 2018, 11:52 AM.

Details

Summary

This patch adjusts a test not to depend on deprecated FileCheck
behavior that permits overlapping matches within a block of CHECK-DAG
directives. Thus, this patch also removes uses of FileCheck's
-allow-deprecated-dag-overlap command-line option.

Specifically, the FileCheck variables DBG_LOC_START, DBG_LOC_END, and
DBG_LOC_CANCEL were all set to the same value. As a result, three
TERM_DEBUG-DAG patterns, one for each variable, all matched the same
text under the old overlapping behavior. Under the new
non-overlapping behavior, that's not permitted. This patch's solution
is to replace these variables with one variable and replace these
patterns with one pattern.

While I have attempted to preserve this test's original intent, I
might have misunderstood something, so please point out any problems.
Your explanation might prove helpful as I address similar issues in
other tests.

Diff Detail

Repository
rC Clang

Event Timeline

jdenny created this revision.Nov 20 2018, 11:52 AM
ABataev accepted this revision.Nov 20 2018, 11:59 AM

I'm fine with the patch, the original intention was to handle a possible situation where we may have several debug locations with the same line numbers.

This revision is now accepted and ready to land.Nov 20 2018, 11:59 AM

I'm fine with the patch,

Thanks for the quick reviews. I'll push soon.

the original intention was to handle a possible situation where we may have several debug locations with the same line numbers.

We were afraid of that. If we find we really need this use case, we'll have to find a nicer way to express it. For reference, this use case is discussed under S1 here:

http://lists.llvm.org/pipermail/llvm-dev/2018-May/123258.html

I'm fine with the patch,

Thanks for the quick reviews. I'll push soon.

the original intention was to handle a possible situation where we may have several debug locations with the same line numbers.

We were afraid of that. If we find we really need this use case, we'll have to find a nicer way to express it. For reference, this use case is discussed under S1 here:

http://lists.llvm.org/pipermail/llvm-dev/2018-May/123258.html

Ok, got it. Thanks for the patch!

This revision was automatically updated to reflect the committed changes.