From: Yvan Roux <yvan.roux@linaro.org>
To: Vladimir Makarov <vmakarov@redhat.com>, Jakub Jelinek <jakub@redhat.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: patch for PR65729
Date: Tue, 14 Apr 2015 08:08:00 -0000 [thread overview]
Message-ID: <CAD57uCezAGmX_ag9kaEdKLUEyLSzeDaFdBbfwgZWG6bZHo3P6w@mail.gmail.com> (raw)
In-Reply-To: <5527FCAC.3090205@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1606 bytes --]
Hi,
here is the patch that restore the assertion and swap its arguments as
discussed in the PR.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65729
Bootstrapped and regtested on x86_64, cross built and regtested on
i686, aarch64, arm and armeb. Is it ok for trunk (maybe after 5.1 is
released) ?
Thanks,
Yvan
gcc/
2015-04-13 Yvan Roux <yvan.roux@linaro.org>
PR target/65729
* lra-constraints.c (prohibited_class_reg_set_mode_p): Restore and fix
the assertion.
gcc/testsuite/
2015-04-13 Yvan Roux <yvan.roux@st.com>
PR target/65729
* gcc.target/arm/pr65729.c: New test.
On 10 April 2015 at 18:39, Vladimir Makarov <vmakarov@redhat.com> wrote:
> I've committed the following patch for
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65729
>
> The assert is definitely wrong. We will work for the right one for
> GCC-5.1.
>
> Committed as rev. 221975.
>
> 2015-04-10 Vladimir Makarov <vmakarov@redhat.com>
>
> PR target/65729
> * lra-constraints.c (prohibited_class_reg_set_mode_p): Comment the
> assert.
>
> Index: lra-constraints.c
> ===================================================================
> --- lra-constraints.c (revision 221949)
> +++ lra-constraints.c (working copy)
> @@ -1656,7 +1656,8 @@
> {
> HARD_REG_SET temp;
>
> - lra_assert (hard_reg_set_subset_p (set, reg_class_contents[rclass]));
> + // ??? Is this assert right
> + // lra_assert (hard_reg_set_subset_p (set, reg_class_contents[rclass]));
> COPY_HARD_REG_SET (temp, set);
> AND_COMPL_HARD_REG_SET (temp, lra_no_alloc_regs);
> return (hard_reg_set_subset_p
>
[-- Attachment #2: pr65729.diff --]
[-- Type: text/plain, Size: 954 bytes --]
diff --git a/gcc/lra-constraints.c b/gcc/lra-constraints.c
index 7353e7c..c51a25b 100644
--- a/gcc/lra-constraints.c
+++ b/gcc/lra-constraints.c
@@ -1656,8 +1656,7 @@ prohibited_class_reg_set_mode_p (enum reg_class rclass,
{
HARD_REG_SET temp;
- // ??? Is this assert right
- // lra_assert (hard_reg_set_subset_p (set, reg_class_contents[rclass]));
+ lra_assert (hard_reg_set_subset_p (reg_class_contents[rclass],set));
COPY_HARD_REG_SET (temp, set);
AND_COMPL_HARD_REG_SET (temp, lra_no_alloc_regs);
return (hard_reg_set_subset_p
diff --git a/gcc/testsuite/gcc.target/arm/pr65729.c b/gcc/testsuite/gcc.target/arm/pr65729.c
new file mode 100644
index 0000000..0d7e3c1
--- /dev/null
+++ b/gcc/testsuite/gcc.target/arm/pr65729.c
@@ -0,0 +1,9 @@
+/* { dg-do compile } */
+/* { dg-options "-O2 -march=armv7-a -mfloat-abi=hard -mfpu=vfpv3-d16" } */
+
+int foo (void)
+{
+ double x = 0.0;
+ asm volatile ("" : "+gw" (x));
+ return x;
+}
next prev parent reply other threads:[~2015-04-14 8:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 16:39 Vladimir Makarov
2015-04-14 8:08 ` Yvan Roux [this message]
2015-04-14 8:11 ` Jakub Jelinek
2015-04-14 15:36 ` Vladimir Makarov
2015-04-15 12:51 ` Yvan Roux
2015-04-18 14:22 ` Richard Earnshaw
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=CAD57uCezAGmX_ag9kaEdKLUEyLSzeDaFdBbfwgZWG6bZHo3P6w@mail.gmail.com \
--to=yvan.roux@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--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).