public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	       Jeff Law <law@redhat.com>
Subject: Re: [PATCH][PR target/15184] Fix for direct byte access on x86
Date: Thu, 29 Jan 2015 16:23:00 -0000	[thread overview]
Message-ID: <20150129145628.GK1746@tucnak.redhat.com> (raw)
In-Reply-To: <CAFULd4ZEu==tvZs_kTf1F_k2yjsDF5wy81oDWp5OcBb6RmqaWg@mail.gmail.com>

On Thu, Jan 29, 2015 at 03:54:34PM +0100, Uros Bizjak wrote:
> On Thu, Jan 29, 2015 at 3:47 PM, Jakub Jelinek <jakub@redhat.com> wrote:
> 
> >> > So here's the updated patch which handles all 4 testcases from the PR as well as a couple of my own.
> >>
> >> @@ -0,0 +1,33 @@
> >> +/* PR 15184 first two tests, plus two addition ones.  */
> >> +/* { dg-do compile } */
> >> +/* { dg-options "-O2 -m32 -march=pentiumpro" } */
> >>
> >> No, we don't want -m32 in dg-options. Please write this part as:
> >>
> >> /* { dg-do compile { target ia32 } } */
> >> /* { dg-options "-O2 -march=pentiumpro" } */
> >
> > Or
> > /* { dg-do compile } */
> > /* { dg-options "-O2" } */
> > /* { dg-additional-options "-march=pentiumpro" { target ia32 } } */
> > if there is nothing ia32 specific on the testcase, just that you want
> > to use that -march option if you are compiling it as 32-bit.
> 
> In this case, you will need to add -mregparm=3 to
> dg-additional-options to avoid "attribute ... ignored" awarning. There
> are some examples in dg.target/i386/ testsuite directory.

Ah, then better limit that to just ia32 in dg-do.

	Jakub

  reply	other threads:[~2015-01-29 14:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29 15:51 Uros Bizjak
2015-01-29 16:06 ` Jakub Jelinek
2015-01-29 16:08   ` Uros Bizjak
2015-01-29 16:23     ` Jakub Jelinek [this message]
2015-01-29 21:42       ` H.J. Lu
2015-01-30  9:21 ` Jeff Law
2015-01-30 11:02   ` Uros Bizjak
2015-01-30 11:21     ` Jakub Jelinek
2015-01-30 11:21       ` Uros Bizjak
2015-01-30 11:46         ` Jakub Jelinek
2015-01-30 20:36           ` Jeff Law
2015-01-30 20:37     ` Jeff Law
  -- strict thread matches above, loose matches on Subject: below --
2015-01-30 11:01 Dominique Dhumieres
2015-01-29 15:21 Jeff Law
2015-01-29 20:50 ` Segher Boessenkool
2015-01-30  8:57   ` Jeff Law

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=20150129145628.GK1746@tucnak.redhat.com \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.com \
    --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).