public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
To: gcc-patches@gcc.gnu.org, Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Subject: Re: [PATCH 1/2] s/390: Implement "target" attribute.
Date: Mon, 09 Nov 2015 13:09:00 -0000	[thread overview]
Message-ID: <56409B0B.2090405@linux.vnet.ibm.com> (raw)
In-Reply-To: <20151102084413.GA4147@linux.vnet.ibm.com>

On 11/02/2015 09:44 AM, Dominik Vogt wrote:
> (@Uli: I'd like to hear your opinion on this issue.
> Original message:
> https://gcc.gnu.org/ml/gcc-patches/2015-10/msg03403.html).
> 
> On Fri, Oct 30, 2015 at 03:09:39PM +0100, Andreas Krebbel wrote:
>> Why do we need x_s390_arch_specified and x_s390_tune_specified?  You
>> should be able to use opts_set->x_s390_arch and opts_set->x_s390_tune
>> instead? (patch attached, your tests keep working with that change).
> 
> The idea was that -mtune on the command line is *not* overridden
> by the "arch" target attribute.  This would allow to change the
> architecture for a specific function and keep the -mtune= option
> from the command line.  But as a matter of fact, the current patch
> doesn't do it either (bug?).

Your testcases even seem to check for this behavior so it looked intentional to me.  But I agree
that being able to keep the -mtune cmdline value for a function while only changing the used
instruction set would be good.

Could you please elaborate why implementing this requires the new flags?

-Andreas-

  reply	other threads:[~2015-11-09 13:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-25 14:16 [PATCH] " Dominik Vogt
2015-09-25 14:16 ` [PATCH 2/2] " Dominik Vogt
2015-12-04 14:36   ` Andreas Krebbel
2015-09-25 15:05 ` [PATCH 1/2] " Dominik Vogt
     [not found] ` <20150925140123.GB14892@linux.vnet.ibm.com>
2015-10-16 12:33   ` Dominik Vogt
2015-10-26 10:11     ` Dominik Vogt
2015-10-26 12:16       ` Dominik Vogt
2015-10-30 14:29       ` Andreas Krebbel
2015-10-31 18:01         ` Dominik Vogt
2015-11-09  7:10           ` Andreas Krebbel
2015-12-04 14:14           ` Dominik Vogt
2015-12-04 14:36             ` Andreas Krebbel
2015-11-02  8:44         ` Dominik Vogt
2015-11-09 13:09           ` Andreas Krebbel [this message]
2015-11-17 19:23             ` Dominik Vogt
2015-11-02 10:47         ` Dominik Vogt

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=56409B0B.2090405@linux.vnet.ibm.com \
    --to=krebbel@linux.vnet.ibm.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=gcc-patches@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).