public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tom de Vries <Tom_deVries@mentor.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Jan Hubicka <hubicka@ucw.cz>, Richard Biener <rguenther@suse.de>,
	"gcc-patches@gnu.org" <gcc-patches@gnu.org>,
	Ilya Enkovich	<enkovich.gnu@gmail.com>
Subject: Re: [PING][PATCH, PR67709 ] Don't call call_cgraph_insertion_hooks in simd_clone_create
Date: Tue, 16 Feb 2016 11:10:00 -0000	[thread overview]
Message-ID: <56C303A5.5050105@mentor.com> (raw)
In-Reply-To: <20160216100428.GN3017@tucnak.redhat.com>

On 16/02/16 11:04, Jakub Jelinek wrote:
> On Tue, Feb 16, 2016 at 10:56:58AM +0100, Tom de Vries wrote:
>> >AFAIU, it's not a release regression given that:
>> >- this has failed since 4.9.0, and
>> >- the test-case is not supported in 4.8,
>> >so we're not required to fix it in 4.9 and 5 branches.
>> >
>> >But, the test-case does fail in 5 and 4.9 branches, and the fix seems simple
>> >enough to not have the risk of introducing breakage in the release branches.
>> >
>> >OK for 4.9/5 branch?
> Okay.
>

Hmm, it doesn't apply cleanly.

The trunk version of simd_clone_create also contains: 'Fix ICE for SIMD 
clones usage in LTO' ( 
https://gcc.gnu.org/ml/gcc-patches/2015-10/msg00434.html ), which adds 
the 'in_other_partition' propagation in simd_clone_create.

That's also not a release regression (reproduces with 4.9.0 release, not 
supported in 4.8), and still reproduces on 4.9 and 5 branches.

OK to backport 'Fix ICE for SIMD clones usage in LTO' to 4.9/5 branch?

Thanks,
- Tom


  reply	other threads:[~2016-02-16 11:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 12:47 [PATCH, " Tom de Vries
2016-02-08 12:55 ` Jakub Jelinek
2016-02-15  9:38   ` [PING][PATCH, " Tom de Vries
2016-02-16  2:22     ` Jan Hubicka
2016-02-16  9:57       ` Tom de Vries
2016-02-16 10:04         ` Jakub Jelinek
2016-02-16 11:10           ` Tom de Vries [this message]
2016-02-16 11:12             ` Jakub Jelinek
2016-02-16 16:53               ` Tom de Vries
2016-02-16 16:55                 ` Jakub Jelinek
2016-02-16 20:52                   ` Tom de Vries

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=56C303A5.5050105@mentor.com \
    --to=tom_devries@mentor.com \
    --cc=enkovich.gnu@gmail.com \
    --cc=gcc-patches@gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=jakub@redhat.com \
    --cc=rguenther@suse.de \
    /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).