public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/96265] New: building nvptx-none on platforms other than x86_64-linux-gnu, e.g. aarch64-linux-gnu and powerpc64le-linux-gnu Date: Tue, 21 Jul 2020 11:55:22 +0000 [thread overview] Message-ID: <bug-96265-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96265 Bug ID: 96265 Summary: building nvptx-none on platforms other than x86_64-linux-gnu, e.g. aarch64-linux-gnu and powerpc64le-linux-gnu Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: doko at debian dot org Target Milestone: --- The nvptx-target usually is built on x86_64-linux-gnu, but searching the web you'll see that these GPUs are also used in aarch64-linux-gnu and powerpc64le-linux-gnu systems. building the nvptx offload compiler on powerpc64le, you see reasonable test results for libgomp, and I see at last one powerpc64le related commit: 2015-10-09 James Norris <jnorris@codesourcery.com> * config/rs6000/rs6000.c (rs6000_offload_options): New. (TARGET_OFFLOAD_OPTIONS): New. However adding an aarch64_offload_options hook doesn't look that well for AArch64, there are still two type of issues triggered in the testsuite: FAIL: libgomp.c/../libgomp.c-c++-common/for-11.c (test for excess errors) Excess errors: lto1: fatal error: nvptx-none - 0-bit integer numbers unsupported (mode 'SI') and: NRESOLVED: libgomp.c/../libgomp.c-c++-common/for-9.c compilation failed to produce executable UNSUPPORTED: libgomp.c/../libgomp.c-c++-common/function-not-offloaded-aux.c spawn -ignore SIGHUP /home/ubuntu/gcc-10-10.1.0/build/./gcc/xgcc -B/home/ubuntu/gcc-10-10.1.0/build/./gcc/ -B/usr/aarch64-linux-gnu/b in/ -B/usr/aarch64-linux-gnu/lib/ -isystem /usr/aarch64-linux-gnu/include -isystem /usr/aarch64-linux-gnu/sys-include -isystem /home/ ubuntu/gcc-10-10.1.0/build/sys-include -fchecking=1 offload_device_nonshared_as411951.c -B/home/ubuntu/gcc-10-10.1.0/build/aarch64-li nux-gnu/./libgomp/ -B/home/ubuntu/gcc-10-10.1.0/build/aarch64-linux-gnu/./libgomp/.libs -I/home/ubuntu/gcc-10-10.1.0/build/aarch64-li nux-gnu/./libgomp -I../../../../src/libgomp/testsuite/../../include -I../../../../src/libgomp/testsuite/.. -Lno -fmessage-length=0 -f no-diagnostics-show-caret -Wno-hsa -fdiagnostics-color=never -B/home/ubuntu/gcc-10-10.1.0/debian/tmp-nvptx/usr/libexec/gcc/aarch64-li nux-gnu/10 -B/home/ubuntu/gcc-10-10.1.0/debian/tmp-nvptx/usr/bin -fopenmp -L/home/ubuntu/gcc-10-10.1.0/build/aarch64-linux-gnu/./libg omp/.libs -lm -o offload_device_nonshared_as411951.exe lto1: internal compiler error: bytecode stream: string too long for the string table 0x62559f string_for_index ../../src-nvptx/gcc/data-streamer-in.c:53 0x62559f bp_unpack_indexed_string(data_in*, bitpack_d*, unsigned int*) ../../src-nvptx/gcc/data-streamer-in.c:97 0x87a39b lto_input_mode_table(lto_file_decl_data*) ../../src-nvptx/gcc/lto-streamer-in.c:1685 0x5a076f lto_file_finalize ../../src-nvptx/gcc/lto/lto-common.c:2217 0x5a076f lto_create_files_from_ids ../../src-nvptx/gcc/lto/lto-common.c:2240 0x5a076f lto_file_read ../../src-nvptx/gcc/lto/lto-common.c:2295 0x5a076f read_cgraph_and_symbols(unsigned int, char const**) ../../src-nvptx/gcc/lto/lto-common.c:2747 0x58f523 lto_main() ../../src-nvptx/gcc/lto/lto.c:625 Please submit a full bug report, with preprocessed source if appropriate.
next reply other threads:[~2020-07-21 11:55 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-21 11:55 doko at debian dot org [this message] 2020-07-23 13:58 ` [Bug target/96265] " doko at debian dot org 2020-11-13 9:12 ` [Bug target/96265] building nvptx-none on aarch64-linux-gnu burnus at gcc dot gnu.org 2023-10-23 14:30 ` mxlol233 at outlook dot com 2024-02-29 17:50 ` pinskia at gcc dot gnu.org 2024-04-09 1:14 ` [Bug ipa/96265] offloading to nvptx-none from aarch64-linux-gnu (and riscv*-linux-gnu) does not work pinskia at gcc dot gnu.org 2024-04-09 1:14 ` pinskia at gcc dot gnu.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-96265-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).