[llvm-dev] Collecting some feedback on forward the scheduling state across machine basic block.

Sun Jun 16 19:49:02 PDT 2019

Hi, 

Sorry about that. I have updated my mail client configuration to sent it both HTML and plain text. This is the content of my last mail. Thank you!

"Hi, all,

I am trying to do some improvement to forward the scheduling state between MBB for MI scheduler. It is based on the idea that, if MBB2 has single pred MBB1, then, the MBB1's scheduling state is valid to MBB2. I have posted all the needed patches for months. I really need your input. Thank you!

https://reviews.llvm.org/D61248 is the 1st patch to allow the schedule strategy to forward the schedule state between MBB.
https://reviews.llvm.org/D61249 is the 2nd patch to update the schedule strategy for SystemZ target to adapt with 1st patch.
https://reviews.llvm.org/D59480 is the 3rd patch to add the scheduled state data structure, so that, it could be kept somewhere.
https://reviews.llvm.org/D61250 is the last patch to forward the scheduled state 3rd patch added for PostGenericScheduler and enable it for PowerPC target."

-----Alex Bradbury <asb at asbradbury.org> wrote: -----
To: Qing Shan Zhang <qshanz at cn.ibm.com>
From: Alex Bradbury <asb at asbradbury.org>
Date: 06/16/2019 10:54PM
Cc: llvm-dev <llvm-dev at lists.llvm.org>, flo at fhahn.com
Subject: [EXTERNAL] Re: [llvm-dev] Collecting some feedback on forward the scheduling state across machine basic block.

On Tue, 11 Jun 2019 at 10:21, Qing Shan Zhang via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
>
> Hi, all,
>
> I am trying to do some improvement to forward the scheduling state between MBB for MI scheduler. It is based on the idea that, if MBB2 has single pred MBB1, then, the MBB1's scheduling state is valid to MBB2. I have posted all the needed patches for months. I really need your input. Thank you!
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__reviews.llvm.org_D61248&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=4FedcNQfP4QcaBGfhp8oq2wPQHIv51RNpo7UEhopmZc&m=5lWEHS9vJLwK19WJPkjXRoGuGpw1_SXfBa9DclxtPS8&s=bXmgxmC6thWfYEh5-tKrKUSEWzQyzMM-0F9d30yIJP8&e=  is the 1st patch to allow the schedule strategy to forward the schedule state between MBB.
> https://urldefense.proofpoint.com/v2/url?u=https-3A__reviews.llvm.org_D61249&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=4FedcNQfP4QcaBGfhp8oq2wPQHIv51RNpo7UEhopmZc&m=5lWEHS9vJLwK19WJPkjXRoGuGpw1_SXfBa9DclxtPS8&s=hTJT6h6jpHiir7wnJHTXLMgySsN1jTSM4WxoILpAgx4&e=  is the 2nd patch to update the schedule strategy for SystemZ target to adapt with 1st patch.
> https://urldefense.proofpoint.com/v2/url?u=https-3A__reviews.llvm.org_D59480&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=4FedcNQfP4QcaBGfhp8oq2wPQHIv51RNpo7UEhopmZc&m=5lWEHS9vJLwK19WJPkjXRoGuGpw1_SXfBa9DclxtPS8&s=ElVYPA07HK8vpeeNR0pW4MHFydiKi5rZ2Qq4i_IuO10&e=  is the 3rd patch to add the scheduled state data structure, so that, it could be kept somewhere.
> https://urldefense.proofpoint.com/v2/url?u=https-3A__reviews.llvm.org_D61250&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=4FedcNQfP4QcaBGfhp8oq2wPQHIv51RNpo7UEhopmZc&m=5lWEHS9vJLwK19WJPkjXRoGuGpw1_SXfBa9DclxtPS8&s=ObgPCxnb1MH3qf3kuFzC7CTGAWDGBxy9D8aVOgDepC0&e=  is the last patch to forward the scheduled state 3rd patch added for PostGenericScheduler and enable it for PowerPC target.

Hi! I wanted to link this from tomorrow's LLVM Weekly, but your email
was sent HTML-only and doesn't appear up in a readable form in the
mailing list archives
(https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.llvm.org_pipermail_llvm-2Ddev_2019-2DJune_132953.html&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=4FedcNQfP4QcaBGfhp8oq2wPQHIv51RNpo7UEhopmZc&m=5lWEHS9vJLwK19WJPkjXRoGuGpw1_SXfBa9DclxtPS8&s=MQddJ4jeLo5a9mEo70aQwR9vuPsTzUeFVOnDjQmv0fo&e= ).
Responding with your email quoted so there's a plain-text form I can
link to.

Please look at configuring your email client to send plain text for
the llvm-dev list.

Best,

Alex

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190617/69a4cb74/attachment.html>