public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Vladimir Makarov <vmakarov@redhat.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [committed] [PR105032] LRA: modify loop condition to find reload insns for hard reg splitting
Date: Wed, 30 Mar 2022 16:13:39 -0400	[thread overview]
Message-ID: <f8dacba2-ef19-b123-d623-1e6db64a4b4f@redhat.com> (raw)
In-Reply-To: <CAFULd4Y9oQir92WuXkH0NsM8hEYyJ46X3M1R1V4EW3RL+1whLg@mail.gmail.com>


On 2022-03-30 15:18, Uros Bizjak wrote:
> On Wed, Mar 30, 2022 at 7:15 PM Vladimir Makarov via Gcc-patches
> <gcc-patches@gcc.gnu.org> wrote:
>> The following patch fixes
>>
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105032
>>
>> The patch was successfully bootstrapped and tested on x86-64.
> diff --git a/gcc/testsuite/gcc.target/i386/pr105032.c
> b/gcc/testsuite/gcc.target/i386/pr105032.c
> new file mode 100644
> index 00000000000..57b21d3cd7a
> --- /dev/null
> +++ b/gcc/testsuite/gcc.target/i386/pr105032.c
> @@ -0,0 +1,36 @@
> +/* { dg-do compile } */
> +/* { dg-options "-w" } */
> +/* { dg-additional-options "-m32" { target x86_64-*-* } } */
>
> Please don't use -m32 in options, but instead conditionally compile
> the testcase with

Sorry for may be a stupid question.  I am interesting what are the 
reasons for this.  Is it just for saving computer cycles?

I think the test is important therefore I'd like to run the test on 
x86-64 too because people rarely test i686 target.

> /* { dg-do compile { target ia32 } } */


      reply	other threads:[~2022-03-30 20:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30 17:14 Vladimir Makarov
2022-03-30 19:18 ` Uros Bizjak
2022-03-30 20:13   ` Vladimir Makarov [this message]

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=f8dacba2-ef19-b123-d623-1e6db64a4b4f@redhat.com \
    --to=vmakarov@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ubizjak@gmail.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).