[llvm-bugs] [Bug 28462] New: Assertion triggered in MCSymbol when redefining symbol with .set after a use

[via llvm-bugs]

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

            Bug ID: 28462
           Summary: Assertion triggered in MCSymbol when redefining symbol
                    with .set after a use
           Product: libraries
           Version: trunk
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: MC
          Assignee: unassignedbugs at nondot.org
          Reporter: aaron.smith at microsoft.com
                CC: llvm-bugs at lists.llvm.org
    Classification: Unclassified

This test case triggers an assertion in MCSymbol::setVariableValue because the
second .set directive redefines a symbol that was previously used.

save7:
.set _FpSaved, 7
.long _FpSaved
saveA:
.set _FpSaved, 0xa
.long _FpSaved

I believe this is okay. If I change the assert to check if the variable
IsRedefinable or not (as below), the test assembles and the values are encoded
as expected.

void MCSymbol::setVariableValue(const MCExpr *Value) {
  assert((!IsUsed || IsRedefinable) && "Cannot set a variable that has already
been used.");

-- 
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/20160707/0d19fcc3/attachment.html>