public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hongtao Liu <crazylht@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Thomas Schwinge <thomas@codesourcery.com>,
	"H.J. Lu" <hjl.tools@gmail.com>, 	Ilya Verbin <iverbin@gmail.com>,
	gcc@gcc.gnu.org, Jan Hubicka <jh@suse.cz>
Subject: Re: [9/10 Regression] [PR87833] Intel MIC (emulated) offloading still broken (was: GCC 9.0.1 Status Report (2019-04-25))
Date: Tue, 07 May 2019 08:03:00 -0000	[thread overview]
Message-ID: <CAMZc-bw-oh=_OG=eaw7rEDeCx+7sf1O1GXsRmFS+P2YVZqETyw@mail.gmail.com> (raw)
In-Reply-To: <20190430113113.GE2706@tucnak>

On Tue, Apr 30, 2019 at 7:31 PM Jakub Jelinek <jakub@redhat.com> wrote:
>
> On Tue, Apr 30, 2019 at 01:02:40PM +0200, Thomas Schwinge wrote:
> > Hi Jakub!
> >
> > On Tue, 30 Apr 2019 12:56:52 +0200, Jakub Jelinek <jakub@redhat.com> wrote:
> > > On Tue, Apr 30, 2019 at 12:47:54PM +0200, Thomas Schwinge wrote:
> > > > Email to <ilya.verbin@intel.com> apparently is no longer gets delivered.
> > > > Is there anyone else from Intel who'd take over maintenance?
> > >
> > > As your patch is to LTO option handling, I think you want a review from
> > > Honza.
> >
> > Well, I'm actually not asking for review of the WIP patch, but rather
> > looking for someone to take on ownership/maintenance of the functionality
> > of Intel MIC offloading.
>
> That would be indeed greatly appreciated.
>
>         Jakub

I don't konw this guy ilya.verbin@intel.com.
Do you know him/her, H.J?

-- 
BR,
Hongtao

  reply	other threads:[~2019-05-07  8:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 18:38 GCC 9.0.1 Status Report (2019-04-25) Jakub Jelinek
2019-04-25 21:32 ` Jonathan Wakely
2019-04-30 10:37 ` [9/10 Regression] [PR87833] Intel MIC (emulated) offloading still broken (was: GCC 9.0.1 Status Report (2019-04-25)) Thomas Schwinge
2019-04-30 10:48   ` Thomas Schwinge
2019-04-30 10:57     ` Jakub Jelinek
2019-04-30 11:02       ` Thomas Schwinge
2019-04-30 11:31         ` Jakub Jelinek
2019-05-07  8:03           ` Hongtao Liu [this message]
2019-05-09 12:46             ` Ilya Verbin
2019-05-29 14:32               ` [9/10 Regression] [PR87833] Intel MIC (emulated) offloading still broken Thomas Schwinge
2019-05-29 15:50                 ` Jeff Law
2019-11-11  9:13                   ` [8/9/10 " Thomas Schwinge

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='CAMZc-bw-oh=_OG=eaw7rEDeCx+7sf1O1GXsRmFS+P2YVZqETyw@mail.gmail.com' \
    --to=crazylht@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=iverbin@gmail.com \
    --cc=jakub@redhat.com \
    --cc=jh@suse.cz \
    --cc=thomas@codesourcery.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).