1
0
mirror of https://github.com/RPCS3/llvm-mirror.git synced 2024-11-25 20:23:11 +01:00
llvm-mirror/test/FileCheck/bad-char.txt
Joel E. Denny d5b9bb2e37 [FileCheck] Fix isalpha/isalnum calls
D79276 caused the following builder to fail:

  http://lab.llvm.org:8011/builders/llvm-clang-x86_64-expensive-checks-win/builds/23489

Specifically, FileCheck dumped stack in the following tests:

  LLVM :: MC/Mips/micromips-jump-pc-region.s
  LLVM :: MC/Mips/mips-jump-pc-region.s

Those tests contained characters encoded as 160 but that render (at
least for me in vim) like a single space (32).  Those characters
appeared between the `#` and `RUN:` on several lines, and D79276
caused FileCheck to process those lines differently: `RUN:` is a
comment directive.  As a result, D79276 caused FileCheck to start
calling is `isalnum` on those characters.

The problem is that FileCheck calls `isalnum` on type `char` without
casting to `unsigned char` first, so it sign-extends 160 beyond what
`unsigned char` or `EOF` can represent.  C says that has undefined
behavior.  This problem is general to FileCheck's prefix parsing and
so exists independently of D79276.

524457edbc3d fixed the above tests.  This patch changes FileCheck to
use LLVM's replacements for `ctype.h` functions, and it adds tests for
cases that are representative with or without D79276.

Reviewed By: jhenderson, thopre, efriedma

Differential Revision: https://reviews.llvm.org/D79810
2020-05-14 20:24:09 -04:00

43 lines
1.5 KiB
Plaintext
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# This file contains characters that render as spaces (at least for me in vim)
# but are encoded as 160. Each is indicated with a "^" on the following line.
# FileCheck used to call functions like isalnum on each without casting to
# unsigned char first, so it sign-extended beyond what unsigned char or EOF can
# represent. C says that has undefined behavior, and it has caused stack dumps
# under Windows.
//------------------------------------------------
RUN: %ProtectFileCheckOutput \
RUN: not FileCheck -check-prefix=BEFORE-PREFIX %s < /dev/null 2>&1 | \
RUN: FileCheck -check-prefix=ERR-EMPTY-CHECK %s
 BEFORE-PREFIX:
^
ERR-EMPTY-CHECK: error: found empty check string
//------------------------------------------------
RUN: %ProtectFileCheckOutput \
RUN: not FileCheck -check-prefix=AFTER-PREFIX %s < /dev/null 2>&1 | \
RUN: FileCheck -check-prefix=ERR-NO-CHECK %s
AFTER-PREFIX :
^
ERR-NO-CHECK: error: no check strings found
//------------------------------------------------
RUN: %ProtectFileCheckOutput \
RUN: not FileCheck -check-prefix=BEFORE-VAR %s < /dev/null 2>&1 | \
RUN: FileCheck -check-prefix=ERR-BAD-VAR %s
BEFORE-VAR: [[ VAR:]]
^
ERR-BAD-VAR: error: invalid variable name
//------------------------------------------------
RUN: %ProtectFileCheckOutput \
RUN: not FileCheck -check-prefix=AFTER-VAR %s < /dev/null 2>&1 | \
RUN: FileCheck -check-prefix=ERR-BAD-STRING-VAR %s
AFTER-VAR: [[VAR :]]
^
ERR-BAD-STRING-VAR: error: invalid name in string variable definition