Update split marker for split-input-file option to be more restrictive
This is to allow usage of comment blocks along with splits in test cases. For example, "Function Control Flow Lowering" comment block in raise-control-flow.mlir TESTED with existing unit tests PiperOrigin-RevId: 221214451
This commit is contained in:
parent
be6ea23aee
commit
a894bfdfd6
|
@ -332,7 +332,7 @@ static OptResult processFile(std::unique_ptr<MemoryBuffer> ownedBuffer) {
|
|||
/// single test, but could be used for other purposes as well.
|
||||
static OptResult
|
||||
splitAndProcessFile(std::unique_ptr<MemoryBuffer> originalBuffer) {
|
||||
const char marker[] = "-----";
|
||||
const char marker[] = "// -----\n";
|
||||
auto *origMemBuffer = originalBuffer.get();
|
||||
SmallVector<StringRef, 8> sourceBuffers;
|
||||
origMemBuffer->getBuffer().split(sourceBuffers, marker);
|
||||
|
|
Loading…
Reference in a new issue