[llvm-bugs] [Bug 43803] New: "fatal error: error in backend: invalid number of bytes" using clang-cl on Windows
via llvm-bugs
llvm-bugs at lists.llvm.org
Fri Oct 25 03:15:21 PDT 2019
https://bugs.llvm.org/show_bug.cgi?id=43803
Bug ID: 43803
Summary: "fatal error: error in backend: invalid number of
bytes" using clang-cl on Windows
Product: libraries
Version: 9.0
Hardware: PC
OS: Windows XP
Status: NEW
Severity: normal
Priority: P
Component: MC
Assignee: unassignedbugs at nondot.org
Reporter: laudrup at stacktrace.dk
CC: llvm-bugs at lists.llvm.org
Created attachment 22727
--> https://bugs.llvm.org/attachment.cgi?id=22727&action=edit
Stack dump
I am trying to compile some rather large autogenerated C++ sources with
clang-cl on Windows 10 and compiling some of them fails with the rather cryptic
error (to me at least):
"fatal error: error in backend: invalid number of bytes"
The only place I have found this error referenced is in the MCAssembler.cpp
source file which unfortunately doesn't help me much. The only thing I can sort
of guess is that it might be some wrapping if the "Size" variable overflows.
I know I should try to create a small reproducible example, but that's rather
hard as I have no idea what could be the cause of this.
This exact same problem happened with LLVM, but I must admitted I haven't tried
with a fresh build from trunk.
As I mentioned the problematic files are rather large, but "only" around 15.000
lines so nothing really extreme.
I have provided the stack dump (which is basically the options given to the
compiler) in case that might help.
I know I haven't provided a lot of information and will of course be more than
happy to provide anything that might help resolve this, I'm just not sure what
that might be.
Thanks a lot and kind regards,
Kasper Laudrup
--
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/20191025/22f50576/attachment-0001.html>
More information about the llvm-bugs
mailing list