[llvm-bugs] [Bug 44464] New: Assertion `Changes[i - 1].OriginalWhitespaceRange.getBegin() != C.OriginalWhitespaceRange.getBegin() && "Generating two replacements for the same location"' failed.
via llvm-bugs
llvm-bugs at lists.llvm.org
Sun Jan 5 14:51:04 PST 2020
https://bugs.llvm.org/show_bug.cgi?id=44464
Bug ID: 44464
Summary: Assertion `Changes[i -
1].OriginalWhitespaceRange.getBegin() !=
C.OriginalWhitespaceRange.getBegin() && "Generating
two replacements for the same location"' failed.
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Formatter
Assignee: unassignedclangbugs at nondot.org
Reporter: pablomg+llvm at eskapa.be
CC: djasper at google.com, klimek at google.com,
llvm-bugs at lists.llvm.org
Created attachment 22989
--> https://bugs.llvm.org/attachment.cgi?id=22989&action=edit
Stack trace
While blindly applying clang-format on all .cpp files inside the llvm-project
tree, I stumbled upon this assertion fail.
The fail appears while running clang-format on the following comments in
clang/test/CodeGenCXX/constructor-destructor-return-this.cpp:
//RUN: %clang_cc1 %s -emit-llvm -o - -triple=i686-unknown-linux| FileCheck
--check-prefix=CHECKGEN %s
//RUN: %clang_cc1 %s -emit-llvm -o - -triple=thumbv7-apple-ios6.0 -target-abi
apcs-gnu | FileCheck --check-prefix=CHECKARM %s
//RUN: %clang_cc1 %s -emit-llvm -o - -triple=thumbv7-apple-ios5.0 -target-abi
apcs-gnu | FileCheck --check-prefix=CHECKIOS5 %s
//RUN: %clang_cc1 %s -emit-llvm -o - -triple=wasm32-unknown-unknown \
//RUN: | FileCheck --check-prefix=CHECKARM %s
//RUN: %clang_cc1 %s -emit-llvm -o - -triple=x86_64-unknown-fuchsia | FileCheck
--check-prefix=CHECKFUCHSIA %s
//RUN: %clang_cc1 %s -emit-llvm -o - -triple=aarch64-unknown-fuchsia |
FileCheck --check-prefix=CHECKFUCHSIA %s
//RUN: %clang_cc1 %s -emit-llvm -o - -triple=i386-pc-win32 -fno-rtti |
FileCheck --check-prefix=CHECKMS %s
I can avoid the assertion fail either by setting the column limit to 0 (but
setting it to 500 doesn't work) or by inserting an empty line after each
comment line. This issue didn't exist on clang-format 9.
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20200105/478d33f5/attachment.html>
More information about the llvm-bugs
mailing list