From: Hongtao Liu <crazylht@gmail.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>,
Vladimir Makarov <vmakarov@redhat.com>
Cc: Jakub Jelinek <jakub@redhat.com>, tdevries@suse.de
Subject: [PATCH][PR target/97532] Fix invalid address for special memory constraint.
Date: Tue, 27 Oct 2020 14:52:54 +0800 [thread overview]
Message-ID: <CAMZc-byYb4BdJu_AQq8Q-2MLFsRGeGcRkqBd6h3ymYB3YxfK-A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 497 bytes --]
Hi:
Sorry for Incomplete test for my last patch at
https://gcc.gnu.org/pipermail/gcc-patches/2020-October/555948.html.
This patch should fix invalid address introduced by special memory constraint.
Bootstrap is ok, regression test is ok for make check
RUNTESTFLAGS="--target_board='unix{-m32,}'"
gcc/ChangeLog
PR target/97532
* gcc/lra-constraints.c (valid_address_p): Handle operand of
special memory constraint.
(process_address_1): Ditto.
--
BR,
Hongtao
[-- Attachment #2: 0001-Fix-invalid-address-for-special_memory_constraint.patch --]
[-- Type: application/x-patch, Size: 2710 bytes --]
next reply other threads:[~2020-10-27 6:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 6:52 Hongtao Liu [this message]
2020-11-02 19:47 ` Vladimir Makarov
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=CAMZc-byYb4BdJu_AQq8Q-2MLFsRGeGcRkqBd6h3ymYB3YxfK-A@mail.gmail.com \
--to=crazylht@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=tdevries@suse.de \
--cc=vmakarov@redhat.com \
/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).