On 4 August 2017 at 00:23, Mike Stump wrote:
> On Jul 27, 2017, at 2:07 AM, Pierre-Marie de Rodat
> wrote:
>> On 07/27/2017 09:52 AM, Richard Biener wrote:
I'm fine with the direction if a reviewer wants to go in that
direction. I wish python didn't have a built-in speed penalty,
On Jul 27, 2017, at 2:07 AM, Pierre-Marie de Rodat wrote:
> On 07/27/2017 09:52 AM, Richard Biener wrote:
>>> I'm fine with the direction if a reviewer wants to go in that
>>> direction. I wish python didn't have a built-in speed penalty,
>>> that's the only downside I don't like about it. Aside
On 08/03/2017 02:27 AM, Pierre-Marie de Rodat wrote:
> On 08/02/2017 05:43 PM, Jeff Law wrote:
>> I hate to throw in a wrench at this point, but has anyone looked at
>> dwgrep from Petr Machata? He's not doing much with it anymore, but it
>> might provide enough of a dwarf scanning framework to be
On 08/02/2017 05:43 PM, Jeff Law wrote:
I hate to throw in a wrench at this point, but has anyone looked at
dwgrep from Petr Machata? He's not doing much with it anymore, but it
might provide enough of a dwarf scanning framework to be useful for
testing purposes.
Sure, no problem: I first star
On 07/27/2017 01:52 AM, Richard Biener wrote:
> On Wed, Jul 26, 2017 at 11:25 PM, Mike Stump wrote:
>> On Jul 26, 2017, at 9:00 AM, Pierre-Marie de Rodat
>> wrote:
>>> At the last GNU Cauldron, Richard Biener and I talked about DWARF output
>>> testing. Except for guality tests, which are disabl
On 07/26/2017 10:00 AM, Pierre-Marie de Rodat wrote:
> Hello,
>
> At the last GNU Cauldron, Richard Biener and I talked about DWARF output
> testing. Except for guality tests, which are disabled on several
> targets, the only way tests check the DWARF is scanning the annotated
> assembly (-dA), ma
Thank you for your feedback.
On 07/27/2017 09:52 AM, Richard Biener wrote:
I'm fine with the direction if a reviewer wants to go in that
direction. I wish python didn't have a built-in speed penalty,
that's the only downside I don't like about it. Aside from that,
even switching all of the tes
On Wed, Jul 26, 2017 at 11:25 PM, Mike Stump wrote:
> On Jul 26, 2017, at 9:00 AM, Pierre-Marie de Rodat
> wrote:
>> At the last GNU Cauldron, Richard Biener and I talked about DWARF output
>> testing. Except for guality tests, which are disabled on several
>> targets, the only way tests check t
On Jul 26, 2017, at 9:00 AM, Pierre-Marie de Rodat wrote:
> At the last GNU Cauldron, Richard Biener and I talked about DWARF output
> testing. Except for guality tests, which are disabled on several
> targets, the only way tests check the DWARF is scanning the annotated
> assembly (-dA), making i
On 07/26/2017 06:15 PM, David Malcolm wrote:
(FWIW I'm a big fan of Python, so am happy to see this proposal)
Me too. :-)
Which version of Python did you test against? As far as I can see
you've coded this using the common subset of Python 2 and Python 3;
it's worth spelling out what the as
On Wed, 2017-07-26 at 18:00 +0200, Pierre-Marie de Rodat wrote:
> Hello,
>
> At the last GNU Cauldron, Richard Biener and I talked about DWARF
> output
> testing. Except for guality tests, which are disabled on several
> targets, the only way tests check the DWARF is scanning the annotated
> assem
11 matches
Mail list logo
