[LLVMbugs] [Bug 16527] New: fp128 constants in llvm assembly are not written or parsed as per the language reference

bugzilla-daemon at llvm.org bugzilla-daemon at llvm.org
Tue Jul 2 13:00:14 PDT 2013


http://llvm.org/bugs/show_bug.cgi?id=16527

            Bug ID: 16527
           Summary: fp128 constants in llvm assembly are not written or
                    parsed as per the language reference
           Product: libraries
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: LLVM assembly language parser
          Assignee: unassignedbugs at nondot.org
          Reporter: flld0 at greynode.net
                CC: llvmbugs at cs.uiuc.edu
    Classification: Unclassified

Created attachment 10808
  --> http://llvm.org/bugs/attachment.cgi?id=10808&action=edit
source code to print an fp128 with just a sign bit

fp128 constants, when printed in llvm assembly, come out in neither big nor
little endian order, but rather with the sign bit in the middle.

According to the language reference, fp128 constants should be represented in
big-endian order: "All hexadecimal formats are big-endian (sign bit at the
left)."

I believe the problem is in the AsmWriter, where printing of long constants is
handled by iterating over the 64-bit words of an APInt in order of increasing
address.

Parsing is consistent with printing, so one's as broken as the other (however
broken you might judge that to be).


Please note: The "component" field of the bug submission form seems to be
somewhat out of data with respect to the current state of the code. This is a
bug in the AsmParser and AsmWriter.

-- 
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/20130702/100c63e3/attachment.html>


More information about the llvm-bugs mailing list