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, "Raúl Porcel" <armin76@gentoo.org>
Subject: Re: [PATCH, haifa-sched]: Fix PR56023, -fcompare-debug failure due to sched1 pass on 4.6 branch
Date: Mon, 21 Jan 2013 14:39:00 -0000	[thread overview]
Message-ID: <50FD5129.5060101@redhat.com> (raw)
In-Reply-To: <CAFULd4ae3+W4O6o8896EsEjEk2pagFu_ryQJRcdg4nRYUKqg5A@mail.gmail.com>

On 13-01-19 2:57 PM, Uros Bizjak wrote:
> Hello!
>
> We should not update ticks of instructions, dependent on debug
> instruction. Without the patch, the scheduling order depends on the
> presence of debug instructions and leads to -fcompare-debug failures.
>
> 2012-01-19  Uros Bizjak  <ubizjak@gmail.com>
>
> 	PR rtl-optimization/56023
> 	* haifa-sched.c (fix_inter_tick): Do not update ticks of instructions,
> 	dependent on debug instruction.
>
> testsuite/ChangeLog:
>
> 2012-01-19  Uros Bizjak  <ubizjak@gmail.com>
>
> 	PR rtl-optimization/56023
> 	* gcc.dg/pr56023.c: New test.
>
> Tested on 4.6 branch on alpha-linux-gnu, where it fixes the bootstrap
> failure and x86_64-pc-linux-gnu {,-m32}.
>
> The patch should be applied to 4.7 and 4.8 branches as well. Patch was
> also tested on mainline x86_64-pc-linux-gnu {,-m32}.
>
> OK for 4.6, 4.7 and mainline?
>
Ok. Thanks for working on this, Uros.

      parent reply	other threads:[~2013-01-21 14:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-19 19:57 Uros Bizjak
2013-01-21 12:27 ` [PATCH v2, " Uros Bizjak
2013-01-21 17:37   ` Uros Bizjak
2013-01-21 14:39 ` 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=50FD5129.5060101@redhat.com \
    --to=vmakarov@redhat.com \
    --cc=armin76@gentoo.org \
    --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).