mirror of
https://github.com/Gericom/teak-llvm.git
synced 2025-06-25 14:28:54 -04:00

This can happen as we look for '<<<<' while scanning tokens but then expect '<<<<\n' to tell apart perforce from diff3 conflict markers. Just harden the pointer arithmetic. Found by libfuzzer + asan! llvm-svn: 265125
11 lines
318 B
C
11 lines
318 B
C
// RUN: %clang_cc1 %s -verify -fsyntax-only
|
|
// vim: set binary noeol:
|
|
|
|
// This file intentionally ends without a \n on the last line. Make sure your
|
|
// editor doesn't add one.
|
|
|
|
>>>> ORIGINAL
|
|
// expected-error@-1 {{version control conflict marker in file}}
|
|
<<<<
|
|
// expected-error@-1 {{expected identifier or '('}}
|
|
<<<< |