public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/98519] New: rs6000: @pcrel unsupported on this instruction error in pveclib
Date: Mon, 04 Jan 2021 22:12:55 +0000 [thread overview]
Message-ID: <bug-98519-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98519
Bug ID: 98519
Summary: rs6000: @pcrel unsupported on this instruction error
in pveclib
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: bergner at gcc dot gnu.org
Target Milestone: ---
Using latest GCC trunk and binutils trunk from today, we see the following
error on a reduced test case from pveclib:
bergner@pike:~/gcc/BUGS/PVECLIB$ cat bug.i
typedef __attribute__((altivec(vector__))) double vf64_t;
static double test_f64[16];
vf64_t
bug (void)
{
vf64_t j0;
__asm__("lxsd%X1 %0,%1;" : "=v" (j0) : "m" (test_f64));
return j0;
}
bergner@pike:~/gcc/BUGS/PVECLIB$
/home/bergner/gcc/build/gcc-fsf-mainline-pveclib-debug/gcc/xgcc
-B/home/bergner/gcc/build/gcc-fsf-mainline-pveclib-debug/gcc -c -O2
-mcpu=power10 bug.i
/tmp/ccNVSo9c.s: Assembler messages:
/tmp/ccNVSo9c.s:15: Warning: @pcrel unsupported on this instruction
/tmp/ccNVSo9c.s:15: Error: unsupported relocation for DS offset field
/tmp/ccNVSo9c.s:15: Error: missing operand
The problematic insn is:
lxsd 2,.LANCHOR0@pcrel;
next reply other threads:[~2021-01-04 22:12 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 22:12 bergner at gcc dot gnu.org [this message]
2021-01-04 22:19 ` [Bug target/98519] " bergner at gcc dot gnu.org
2021-01-04 23:08 ` meissner at gcc dot gnu.org
2021-01-04 23:23 ` bergner at gcc dot gnu.org
2021-01-04 23:49 ` segher at gcc dot gnu.org
2021-01-05 1:18 ` munroesj at gcc dot gnu.org
2021-01-05 1:23 ` segher at gcc dot gnu.org
2021-01-05 1:55 ` munroesj at gcc dot gnu.org
2021-01-05 3:09 ` segher at gcc dot gnu.org
2021-01-05 3:28 ` meissner at gcc dot gnu.org
2021-01-05 14:13 ` wschmidt at gcc dot gnu.org
2021-01-05 15:01 ` segher at gcc dot gnu.org
2021-01-05 16:45 ` wschmidt at gcc dot gnu.org
2021-01-05 17:31 ` bergner at gcc dot gnu.org
2021-01-05 21:08 ` wschmidt at gcc dot gnu.org
2021-01-05 22:07 ` meissner at gcc dot gnu.org
2021-01-13 22:07 ` segher at gcc dot gnu.org
2021-01-13 23:40 ` segher at gcc dot gnu.org
2021-01-22 6:14 ` amodra at gmail dot com
2021-01-22 18:07 ` segher at gcc dot gnu.org
2021-01-23 23:48 ` bergner at gcc dot gnu.org
2021-02-02 4:17 ` meissner at gcc dot gnu.org
2021-02-02 4:34 ` meissner at gcc dot gnu.org
2021-02-02 21:30 ` segher at gcc dot gnu.org
2021-02-02 23:28 ` meissner at gcc dot gnu.org
2021-02-16 16:45 ` meissner at gcc dot gnu.org
2021-02-16 16:48 ` meissner at gcc dot gnu.org
2021-02-16 16:49 ` meissner at gcc dot gnu.org
2021-02-16 23:06 ` segher at gcc dot gnu.org
2022-10-03 19:49 ` bergner at gcc dot gnu.org
2022-10-03 21:07 ` segher at gcc dot gnu.org
2022-10-03 22:18 ` bergner at gcc dot gnu.org
2022-10-03 22:41 ` segher at gcc dot gnu.org
2022-10-03 23:54 ` bergner at gcc dot gnu.org
2022-10-10 16:00 ` 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-98519-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: link
Be 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).