From: Pedro Alves <palves@redhat.com>
To: Ofir Cohen <ofircohenn@gmail.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: False positive permanent breakpoints
Date: Wed, 26 Oct 2016 14:50:00 -0000 [thread overview]
Message-ID: <0c2c2c0f-bb51-7124-8a6d-d3d633788471@redhat.com> (raw)
In-Reply-To: <CAHOBVAfaS61M8Gb9ZzgpGM65RNnXN0jcoRwxq4=2jnKVgvZOOA@mail.gmail.com>
On 10/26/2016 03:42 PM, Ofir Cohen wrote:
> Hi Pedro,
> Thanks for the reply.
> Let me provide some clarifications :-).
>
> 1) The product is part of the "Intel SDK for OpenCL" [1] for Windows and Linux.
> You can see how it looks in [2].
Ah, OK.
>
> 2) iGPU - Yes, Integrated GPU
>
> 3) Upstream is in our plans and actually we are preparing a clean
> series of patches on top of 7.12 (currently we are rebased on top
> of 7.6, yeah I know...).
Nice!
(FAOD, for upstream you'll need to rebase on master.)
>
> 4) Software breakpoints are officially supported by the HW, but
> haven't been tested and used yet, so we're OK with them being
> "disabled" at the moment.
>
> The sources for gdb (as well as other components) are provided with
> the installer script,
> which can be downloaded _free of charge_ via [1] --> "Download" .
>
> Is that good enough for making an upstream change?
>
> I can try and prepare a small patch.
I'd rather that upstreaming that bit was done when the
rest of the port is submitted as well.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-10-26 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 14:04 Ofir Cohen
2016-10-26 14:28 ` Pedro Alves
2016-10-26 14:42 ` Ofir Cohen
2016-10-26 14:50 ` Pedro Alves [this message]
2016-10-26 15:02 ` Ofir Cohen
2016-10-26 15:14 ` Pedro Alves
2016-10-26 15:25 ` Ofir Cohen
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=0c2c2c0f-bb51-7124-8a6d-d3d633788471@redhat.com \
--to=palves@redhat.com \
--cc=gdb@sourceware.org \
--cc=ofircohenn@gmail.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