public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/65911] New: [6 Regression] r222508 breaks clang-tblgen Date: Tue, 28 Apr 2015 08:22:00 -0000 [thread overview] Message-ID: <bug-65911-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65911 Bug ID: 65911 Summary: [6 Regression] r222508 breaks clang-tblgen Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: trippels at gcc dot gnu.org CC: tbsaunde at gcc dot gnu.org Target Milestone: --- Starting with r222508 LLVM doesn't build anymore on ppc64le: trippels@gcc2-power8 llvm_build % ./bin/clang-tblgen -gen-clang-attr-impl -I /home/trippels/llvm/tools/clang/include/clang/AST/../../ -I /home/trippels/llvm/tools/clang/include/clang/AST -I /home/trippels/llvm/lib/Target -I /home/trippels/llvm/include /home/trippels/llvm/tools/clang/include/clang/AST/../Basic/Attr.td -o /home/trippels/llvm_build/tools/clang/include/clang/AST/AttrImpl.inc.tmp Program received signal SIGSEGV, Segmentation fault. 0x00003fffb79d1ee4 in __strcmp_power7 () from /lib64/libc.so.6 (gdb) bt #0 0x00003fffb79d1ee4 in __strcmp_power7 () from /lib64/libc.so.6 #1 0x000000001005c504 in llvm::cl::generic_parser_base::findOption(char const*) () #2 0x0000000010004f9c in _GLOBAL__sub_I_TableGen.cpp ()
next reply other threads:[~2015-04-28 8:22 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-28 8:22 trippels at gcc dot gnu.org [this message] 2015-04-28 9:29 ` [Bug other/65911] " trippels at gcc dot gnu.org 2015-04-28 9:36 ` rguenth at gcc dot gnu.org 2015-04-28 9:38 ` jakub at gcc dot gnu.org 2015-04-28 10:10 ` trippels at gcc dot gnu.org 2015-04-28 10:21 ` trippels at gcc dot gnu.org 2015-04-28 14:42 ` tbsaunde at tbsaunde dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-65911-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).