public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/103085] [12 Regression] -fPIC and -fstack-protector-strong broken AArch64
Date: Thu, 04 Nov 2021 19:30:07 +0000 [thread overview]
Message-ID: <bug-103085-4-KipkqMKDBg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103085-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103085
Wilco <wilco at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2021-11-04
Assignee|unassigned at gcc dot gnu.org |wilco at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Wilco <wilco at gcc dot gnu.org> ---
Yes there is something hacky about the way the salt thingy works. It adds some
unspec around a memory operand and still expects the standard movdi pattern to
recognize it.
It looks like adding support for CONST in Usw constraint and stripping the salt
before checking the symbol in mov_operand_p fixes it. I'm testing a patch.
next prev parent reply other threads:[~2021-11-04 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 17:18 [Bug target/103085] New: " tnfchris at gcc dot gnu.org
2021-11-04 19:30 ` wilco at gcc dot gnu.org [this message]
2021-11-05 7:23 ` [Bug target/103085] " rguenth at gcc dot gnu.org
2021-11-05 15:37 ` cvs-commit at gcc dot gnu.org
2021-11-05 15:38 ` wilco 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-103085-4-KipkqMKDBg@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).