From: Alexander Monakov <amonakov@ispras.ru>
To: Andrey Belevantsev <abel@ispras.ru>
Cc: Marek Polacek <polacek@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [02/05] Fix PR 63384
Date: Tue, 15 Mar 2016 18:12:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.20.1603152111350.28602@monopod.intra.ispras.ru> (raw)
In-Reply-To: <2a1d2382-e8f1-d62f-952b-6518f558f28c@ispras.ru>
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
On Tue, 15 Mar 2016, Andrey Belevantsev wrote:
> On 15.03.2016 20:44, Alexander Monakov wrote:
> > On Tue, 15 Mar 2016, Marek Polacek wrote:
> > > This test fails for me due to
> > > cc1plus: warning: var-tracking-assignments changes selective scheduling
> >
> > Thanks for the heads-up Marek, and sorry for the trouble. Like I said in
> > the adjacent reply, the warning is expected (I didn't realize the
> > testsuite would notice that, though). I think the right fix is to simply
> > add "-w" to dg-options, and while we are at it, we should probably change
> > -fvta-toggle to just -fvta as well (because VTA is active either way,
> > right?).
>
> Yes, the -fvta should work. Sorry for the breakage, I guess I've misread the
> compare-tests output when also checking the run with forced sel-sched enabled.
>
> I can take care of the test tomorrow morning or you can do it now.
Thanks for confirming — committed rev. 234227.
Alexander
next prev parent reply other threads:[~2016-03-15 18:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 9:11 Various selective scheduling fixes Andrey Belevantsev
2016-03-14 9:22 ` [01/05] Fix PR 64411 Andrey Belevantsev
2016-03-14 16:23 ` Alexander Monakov
2016-03-14 16:45 ` Bernd Schmidt
2016-03-15 15:43 ` Andrey Belevantsev
2016-03-14 9:32 ` [02/05] Fix PR 63384 Andrey Belevantsev
2016-03-14 17:13 ` Alexander Monakov
2016-03-15 17:30 ` Marek Polacek
2016-03-15 17:44 ` Alexander Monakov
2016-03-15 18:00 ` Andrey Belevantsev
2016-03-15 18:12 ` Alexander Monakov [this message]
2016-03-14 9:36 ` [03/05] Fix PR 66660 Andrey Belevantsev
2016-03-14 17:37 ` Alexander Monakov
2016-03-14 9:40 ` [04/05] Fix PR 69032 Andrey Belevantsev
2016-03-14 18:15 ` Alexander Monakov
2016-03-14 9:53 ` [05/05] Fix PR 69102 Andrey Belevantsev
2016-03-15 15:55 ` Andrey Belevantsev
2016-03-17 16:39 ` Jeff Law
2016-03-31 14:55 ` Various selective scheduling fixes Andrey Belevantsev
2016-04-01 7:33 ` Christophe Lyon
2016-04-01 8:55 ` Andrey Belevantsev
2016-04-01 13:09 ` Christophe Lyon
2016-04-01 13:12 ` Kyrill Tkachov
2016-04-01 13:26 ` Christophe Lyon
2016-04-01 16:19 ` Jeff Law
2016-04-01 20:08 ` Christophe Lyon
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=alpine.LNX.2.20.1603152111350.28602@monopod.intra.ispras.ru \
--to=amonakov@ispras.ru \
--cc=abel@ispras.ru \
--cc=gcc-patches@gcc.gnu.org \
--cc=polacek@redhat.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).