From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 62807 invoked by alias); 26 Apr 2019 17:35:33 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 62790 invoked by uid 89); 26 Apr 2019 17:35:32 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.9 required=5.0 tests=AWL,BAYES_00,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.1 spammy=HX-Languages-Length:726, H*F:D*ru X-HELO: mail.ispras.ru Received: from mail.ispras.ru (HELO mail.ispras.ru) (83.149.199.45) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 26 Apr 2019 17:35:31 +0000 Received: from mail-lj1-f170.google.com (mail-lj1-f170.google.com [209.85.208.170]) by mail.ispras.ru (Postfix) with ESMTPSA id A361054070D for ; Fri, 26 Apr 2019 20:35:29 +0300 (MSK) Received: by mail-lj1-f170.google.com with SMTP id i186so3638235lji.9 for ; Fri, 26 Apr 2019 10:35:29 -0700 (PDT) MIME-Version: 1.0 References: <06c5e43724c4964b455a41c32626115c@ispras.ru> <7f134ab7-4386-a734-aa86-d30f1fa12d7b@redhat.com> In-Reply-To: <7f134ab7-4386-a734-aa86-d30f1fa12d7b@redhat.com> From: Roman Zhuykov Date: Fri, 26 Apr 2019 17:41:00 -0000 Message-ID: Subject: Re: [3/4][PATCH] Fix PR90001 To: Jeff Law Cc: gcc-patches Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2019-04/txt/msg01086.txt.bz2 > So just an FYI. If ddg.c is only used by the modulo scheduler, then it > falls under your maintainership and you can decide when to install this > patch. Yes, I understand about ddg.c and ddg.h. I also studied everything about loop-doloop.c because it is connected. Will try to participate in doloop discussions, and soon present some (mostly refactoring) doloop patch for approval. > We generally try to avoid major changes right after the branch is cut, > but I doubt we'll be doing a lot of backporting in this code, so I think > you can go whenever you're ready. I'll now wait the "not disrupting code RC phase" to finish, and than will commit it together with posting my next patchset.