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

            Bug ID: 30383
           Summary: [MIPS] integrated-as doesn't parse FreeBSD's
                    exception.S and crashes
           Product: clang
           Version: trunk
          Hardware: Other
                OS: FreeBSD
            Status: NEW
          Severity: normal
          Priority: P
         Component: -New Bugs
          Assignee: unassignedclangb...@nondot.org
          Reporter: sbr...@freebsd.org
                CC: llvm-bugs@lists.llvm.org
    Classification: Unclassified

Created attachment 17262
  --> https://llvm.org/bugs/attachment.cgi?id=17262&action=edit
log output of build for FreeBSD mips kernel and diagnostic/crash files from
clang.

clang will fail to parse the nonsense we are doing in exception.S during out
mips builds and eventually will crash.  I've attached the full build output and
the diagnostic files to this ticket.  There's a lot going on here.

Function size must be evaluatable as absolute
UNREACHABLE executed at
/home/sbruno/clang/llvm/lib/Target/Mips/MCTargetDesc/MipsTargetStreamer.cpp:908!
clang-4.0: error: unable to execute command: Abort trap (core dumped)
clang-4.0: error: clang integrated assembler command failed due to signal (use
-v to see invocation)
clang version 4.0.0 (trunk 281458)
Target: mips64-unknown-freebsd12.0
Thread model: posix
InstalledDir: /home/sbruno/clang/build/bin
clang-4.0: note: diagnostic msg: PLEASE submit a bug report to
http://llvm.org/bugs/ and include the crash backtrace, preprocessed source, and
associated run script.
clang-4.0: note: diagnostic msg: 
********************

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang-4.0: note: diagnostic msg: /tmp/exception-9f94f0.S
clang-4.0: note: diagnostic msg: /tmp/exception-9f94f0.sh
clang-4.0: note: diagnostic msg: 

********************
--- exception.o ---
*** [exception.o] Error code 254

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

Reply via email to