[llvm-bugs] [Bug 27672] New: Compiling a code using llvm + clang on s64fx machine

via llvm-bugs llvm-bugs at lists.llvm.org
Fri May 6 23:22:17 PDT 2016


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

            Bug ID: 27672
           Summary: Compiling a code using llvm + clang on s64fx machine
           Product: clang
           Version: trunk
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: -New Bugs
          Assignee: unassignedclangbugs at nondot.org
          Reporter: geniejhang at majimak.com
                CC: llvm-bugs at lists.llvm.org
    Classification: Unclassified

Hi.

I’m trying to check if llvm + clang with MCJIT backend supports the new system.
The system information is following.

========================================================
cpu      : FUJITSU SPARC64 XIfx
manufacture   : 4 (Fujitsu)
impl      : 12
mask      : 17
serial      : 0
fpu      : FUJITSU SPARC64 XIfx
pmu      : SPARC64XIfx
prom      : CPUFW-1.5.0
type      : s64fx
ncpus probed   : 34
ncpus active   : 34
L2$ size   : 12288 KB

uname -m = s64fx
uname -r = 2.6.32
uname -s = Linux
uname -v = #2 SMP Wed Dec 2 15:57:26 JST 2015
========================================================

It started from installing ROOT software in the system
https://root.cern.ch/phpBB3/viewtopic.php?p=94086#p94086

I was told to compile a simple test code with llvm + clang compiled on the
system.

#include <vector>
extern "C" in printf(const char*,...);
std::vector<int> v{12,13,14};
int main(int, char*[]) {
  printf("vector size: %d\n", (int)v.size());
  return 0;
}

with the following command

clang++ -x c++ -std=c++11 -Xclang -emit-llvm - -o jittest.cxx | lli
-jit-kind=orc-mcjit -

and then I got the following.
For your information, because I config.guess doesn’t recognize the system, I
changed the GetHostTarget.cmake a little bit
to recognize the system as sparc64-unknown-linux-gnu.

========================================================
#0 0x00000000035d929c llvm::sys::PrintStackTrace(llvm::raw_ostream&)
/home/genie/clangTest/llvm/lib/Support/Unix/Signals.inc:322:0
#1 0x00000000035d96a8 PrintStackTraceSignalHandler(void*)
/home/genie/clangTest/llvm/lib/Support/Unix/Signals.inc:379:0
#2 0x00000000035d758c llvm::sys::RunSignalHandlers()
/home/genie/clangTest/llvm/lib/Support/Signals.cpp:45:0
#3 0x00000000035d8b6c SignalHandler(int)
/home/genie/clangTest/llvm/lib/Support/Unix/Signals.inc:200:0
#4 0xffffffff003c1d88 __libc_sigaction (/lib64/libpthread.so.0+0x11d88)
#5 0x000000000554e1b0 clang::Sema::Sema(clang::Preprocessor&,
clang::ASTContext&, clang::ASTConsumer&, clang::TranslationUnitKind,
clang::CodeCompleteConsumer*)
/home/genie/clangTest/llvm/tools/clang/lib/Sema/Sema.cpp:126:0
#6 0x0000000003ed5710
clang::CompilerInstance::createSema(clang::TranslationUnitKind,
clang::CodeCompleteConsumer*)
/home/genie/clangTest/llvm/tools/clang/lib/Frontend/CompilerInstance.cpp:537:0
#7 0x0000000003f36364 clang::ASTFrontendAction::ExecuteAction()
/home/genie/clangTest/llvm/tools/clang/lib/Frontend/FrontendAction.cpp:554:0
#8 0x00000000044637a4 clang::CodeGenAction::ExecuteAction()
/home/genie/clangTest/llvm/tools/clang/lib/CodeGen/CodeGenAction.cpp:844:0
#9 0x0000000003f35c18 clang::FrontendAction::Execute()
/home/genie/clangTest/llvm/tools/clang/lib/Frontend/FrontendAction.cpp:457:0
#10 0x0000000003ed8268
clang::CompilerInstance::ExecuteAction(clang::FrontendAction&)
/home/genie/clangTest/llvm/tools/clang/lib/Frontend/CompilerInstance.cpp:874:0
#11 0x0000000004095ee0
clang::ExecuteCompilerInvocation(clang::CompilerInstance*)
/home/genie/clangTest/llvm/tools/clang/lib/FrontendTool/ExecuteCompilerInvocation.cpp:241:0
#12 0x00000000013b9660 cc1_main(llvm::ArrayRef<char const*>, char const*,
void*) /home/genie/clangTest/llvm/tools/clang/tools/driver/cc1_main.cpp:116:0
#13 0x00000000013ac8b4 ExecuteCC1Tool(llvm::ArrayRef<char const*>,
llvm::StringRef)
/home/genie/clangTest/llvm/tools/clang/tools/driver/driver.cpp:301:0
#14 0x00000000013ad574 main
/home/genie/clangTest/llvm/tools/clang/tools/driver/driver.cpp:381:0
#15 0xffffffff00b7d9d8 __libc_start_main (/lib64/libc.so.6+0x2d9d8)
#16 0x00000000013a9a74 _start
(/gwfefs/home/genie/clangTest/install/bin/clang-3.9+0x13a9a74)
Stack dump:
0.   Program arguments: /gwfefs/home/genie/clangTest/install/bin/clang-3.9 -cc1
-triple sparc64-unknown-linux-gnu -S -disable-free -main-file-name -
-mrelocation-model static -mthread-model posix -mdisable-fp-elim -fmath-errno
-no-integrated-as -mconstructor-aliases -dwarf-column-info -debugger-tuning=gdb
-resource-dir /gwfefs/home/genie/clangTest/install/bin/../lib/clang/3.9.0
-I/data/Q16264/common/gw/local/include -c-isystem
/data/Q16264/common/gw/local/include -cxx-isystem
/data/Q16264/common/gw/local/include -internal-isystem /usr/local/include
-internal-isystem
/gwfefs/home/genie/clangTest/install/bin/../lib/clang/3.9.0/include
-internal-externc-isystem /include -internal-externc-isystem /usr/include
-std=c++11 -fdeprecated-macro -fno-dwarf-directory-asm -fdebug-compilation-dir
/home/genie/clangTest -ferror-limit 19 -fmessage-length 0 -fobjc-runtime=gcc
-fcxx-exceptions -fexceptions -fdiagnostics-show-option -emit-llvm -o
/tmp/--edd9e6.s -x c++ - 
clang-3.9: error: unable to execute command: Bus error
clang-3.9: error: clang frontend command failed due to signal (use -v to see
invocation)
clang version 3.9.0 (trunk 268212)
Target: sparc64-unknown-linux-gnu
Thread model: posix
InstalledDir: /home/genie/clangTest/install/bin
clang-3.9: 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-3.9: note: diagnostic msg: Error generating preprocessed source(s) -
ignoring input from stdin.
clang-3.9: note: diagnostic msg: Error generating preprocessed source(s) - no
preprocessable inputs.
'main' function not found in module.
========================================================

Any idea on this?

Thank you in advance.

Best regards,
Genie

-- 
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/20160507/7c317963/attachment.html>


More information about the llvm-bugs mailing list