[llvm-bugs] [Bug 46702] New: Illegal fragment fill size when using current address in size computation

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=46702

            Bug ID: 46702
           Summary: Illegal fragment fill size when using current address
                    in size computation
           Product: libraries
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: MC
          Assignee: unassignedbugs at nondot.org
          Reporter: jean-michel.gorius at ens-rennes.fr
                CC: llvm-bugs at lists.llvm.org

Created attachment 23723
  --> https://bugs.llvm.org/attachment.cgi?id=23723&action=edit
Backtrace

When trying to compile the following assembly code with clang, an assertion
triggers in the assembler:

> foo:
>    jmp .
> .fill 1024 - (. - foo), 0
produces

> clang-11: /mnt/llvm-dev/github-llvm-project/llvm/lib/MC/MCAssembler.cpp:585: void writeFragment(llvm::raw_ostream &, const llvm::MCAssembler &, const llvm::MCAsmLayout &, const llvm::MCFragment &): Assertion `0 < VSize && VSize <= MaxChunkSize && "Illegal fragment fill size"' failed.

gcc 10.1.0 compile foos.s without complaining. The complete backtrace is
attached to this message.

Note: Substituting .space for .fill makes the code compile with clang.

-- 
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/20200713/72c28f8c/attachment.html>