public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Richard Biener <richard.guenther@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Reset proper type on vector types (PR middle-end/88587).
Date: Mon, 15 Apr 2019 08:11:00 -0000	[thread overview]
Message-ID: <f43202fc-70ee-d1b1-728a-4a3a022eb1c6@suse.cz> (raw)
In-Reply-To: <CAFiYyc3QtYSPfeNrmcSt_AL7REuS52a_1TY21OKSyvKqRL+mhA@mail.gmail.com>

On 4/15/19 9:27 AM, Richard Biener wrote:
> On Mon, Apr 15, 2019 at 8:48 AM Martin Liška <mliska@suse.cz> wrote:
>>
>> Hi.
>>
>> Apparently, there's one another PR:
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90083
>>
>> May I backport the patch to GCC-8 branch?
> 
> Hmm, it isn't a regression, right?  But it only
> affects multi-versioning, so yes, go ahead.

No, it's not. The issue is very old.

> Might as well consider GCC 7 then - do you have
> an overall idea of the state of the MV stuff on branches?

Well, I've made quite some changes to target_clone pass
(multiple_target.c). Thus I would ignore GCC-7 if possible.

Martin

> IIRC you've done most of the "fixes"?
> 
> Richard.
> 
>> Thanks,
>> Martin

      reply	other threads:[~2019-04-15  8:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16  9:20 Martin Liška
2019-01-16  9:26 ` Martin Liška
2019-01-16 11:50   ` Richard Biener
2019-01-16 11:59     ` Jakub Jelinek
2019-01-16 12:01       ` Richard Biener
2019-01-16 12:06 ` Richard Biener
2019-01-17 11:21   ` Martin Liška
2019-01-17 12:51     ` Richard Biener
2019-01-18 14:25       ` H.J. Lu
2019-01-18 14:30         ` H.J. Lu
2019-04-15  6:50       ` Martin Liška
2019-04-15  7:50         ` Richard Biener
2019-04-15  8:11           ` Martin Liška [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=f43202fc-70ee-d1b1-728a-4a3a022eb1c6@suse.cz \
    --to=mliska@suse.cz \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.guenther@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).