From: Jeff Law <law@redhat.com>
To: Roman Zhuykov <zhroma@ispras.ru>, gcc-patches@gcc.gnu.org
Subject: Re: [0/4] Addressing modulo-scheduling bugs
Date: Fri, 26 Apr 2019 15:45:00 -0000 [thread overview]
Message-ID: <e3f0a464-26b4-4a7d-03e1-45941494cbce@redhat.com> (raw)
In-Reply-To: <7f3d315e7de0aeedc65ab7225a3ee794@ispras.ru>
On 4/22/19 10:45 AM, Roman Zhuykov wrote:
> As a freshly appointed maintainer Iâm ready to commit my own
> modulo-sched patches, but decide to ask here if there are any
> objections. Maybe I should ask any additional approval at this stage?Â
> If no, Iâll start tomorrow with committing patches 1/4 and 2/4 which are
> well-formed regression fixes. Patch 3/4 doesnât include test example,
> and I donât know how to add it there, so I am ready to postpone it to
> stage 1. Patch 4/4 is not solving a regression technically.
>
> First two patches can be also committed into 8 branch. If no discussion
> occurs, Iâll commit them later this week, e.g. on friday.
As a maintainer we trust you to make these decisions. Though if you
want guidance, mine would have been to go with #1 and #2 immediately and
postpone #3 and #4 for gcc-10. THat appears to be precisely what you've
done.
Jeff
next prev parent reply other threads:[~2019-04-26 15:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 11:59 zhroma
2019-04-16 12:03 ` [1/4][PATCH] Fix PR84032 Roman Zhuykov
2019-04-16 12:05 ` [2/4][PATCH] Fix PR87979 Roman Zhuykov
2019-04-16 12:08 ` [3/4][PATCH] Fix PR90001 Roman Zhuykov
2019-04-26 15:42 ` Jeff Law
2019-04-26 17:41 ` Roman Zhuykov
2019-04-16 12:26 ` [4/4][PATCH] Discussing PR83507 Roman Zhuykov
2019-04-16 15:10 ` Segher Boessenkool
2019-04-22 16:45 ` Roman Zhuykov
2019-04-23 15:55 ` Segher Boessenkool
2019-04-29 16:56 ` Roman Zhuykov
2019-04-29 17:51 ` Segher Boessenkool
2019-04-30 11:35 ` Roman Zhuykov
2019-04-30 15:14 ` Jeff Law
2019-04-22 19:16 ` [0/4] Addressing modulo-scheduling bugs Roman Zhuykov
2019-04-26 15:45 ` Jeff Law [this message]
2019-04-26 16:41 ` Roman Zhuykov
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=e3f0a464-26b4-4a7d-03e1-45941494cbce@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=zhroma@ispras.ru \
/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).