public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/94710] New: [8/9/10 Regression] Assembler messages: Error: operand out of range (4 is not between 0 and 3) (xxsldwi 0,32,33,4) Date: Wed, 22 Apr 2020 10:18:55 +0000 [thread overview] Message-ID: <bug-94710-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94710 Bug ID: 94710 Summary: [8/9/10 Regression] Assembler messages: Error: operand out of range (4 is not between 0 and 3) (xxsldwi 0,32,33,4) Product: gcc Version: 10.0 Status: UNCONFIRMED Keywords: assemble-failure Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: zsojka at seznam dot cz Target Milestone: --- Host: x86_64-pc-linux-gnu Target: powerpc64le-unknown-linux-gnu Created attachment 48350 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48350&action=edit reduced testcase Compiler output: $ powerpc64le-unknown-linux-gnu-gcc testcase.c /tmp/ccL15VfZ.s: Assembler messages: /tmp/ccL15VfZ.s:19: Error: operand out of range (4 is not between 0 and 3) $ powerpc64le-unknown-linux-gnu-gcc -v Using built-in specs. COLLECT_GCC=/repo/gcc-trunk/binary-latest-powerpc64le/bin/powerpc64le-unknown-linux-gnu-gcc COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r10-7838-20200420212053-g8e841bd419f-checking-yes-rtl-df-extra-powerpc64le/bin/../libexec/gcc/powerpc64le-unknown-linux-gnu/10.0.1/lto-wrapper Target: powerpc64le-unknown-linux-gnu Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++ --enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra --with-cloog --with-ppl --with-isl --with-sysroot=/usr/powerpc64le-unknown-linux-gnu --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --target=powerpc64le-unknown-linux-gnu --with-ld=/usr/bin/powerpc64le-unknown-linux-gnu-ld --with-as=/usr/bin/powerpc64le-unknown-linux-gnu-as --disable-libsanitizer --disable-libstdcxx-pch --prefix=/repo/gcc-trunk//binary-trunk-r10-7838-20200420212053-g8e841bd419f-checking-yes-rtl-df-extra-powerpc64le Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 10.0.1 20200421 (experimental) (GCC)
next reply other threads:[~2020-04-22 10:18 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-22 10:18 zsojka at seznam dot cz [this message] 2020-04-22 11:11 ` [Bug target/94710] " rguenth at gcc dot gnu.org 2020-04-22 12:20 ` marxin at gcc dot gnu.org 2020-04-22 15:29 ` jakub at gcc dot gnu.org 2020-04-22 15:52 ` jakub at gcc dot gnu.org 2020-04-22 16:36 ` segher at gcc dot gnu.org 2020-04-22 17:12 ` jakub at gcc dot gnu.org 2020-04-23 9:54 ` jakub at gcc dot gnu.org 2020-04-23 19:59 ` cvs-commit at gcc dot gnu.org 2020-04-24 8:50 ` segher at gcc dot gnu.org 2020-04-24 13:34 ` segher at gcc dot gnu.org 2020-04-24 18:56 ` cvs-commit at gcc dot gnu.org 2020-04-24 19:06 ` [Bug target/94710] [8/9 " segher at gcc dot gnu.org 2020-09-16 19:20 ` cvs-commit at gcc dot gnu.org 2020-09-17 17:36 ` jakub at gcc dot gnu.org 2020-09-17 21:50 ` cvs-commit at gcc dot gnu.org 2020-09-17 21:52 ` cvs-commit at gcc dot gnu.org 2020-09-17 21:54 ` jakub at gcc dot gnu.org 2020-09-17 21:55 ` segher 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-94710-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).