This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Basic Block Statistics
- From: Jeff Law <law at redhat dot com>
- To: Will Hawkins <whh8b at virginia dot edu>
- Cc: GCC Development <gcc at gcc dot gnu dot org>
- Date: Tue, 16 May 2017 12:54:35 -0600
- Subject: Re: Basic Block Statistics
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx03.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx03.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=law at redhat dot com
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 56C8A80042
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 56C8A80042
- References: <CAE+MWFunCPEWzhmvOtuwo6L4C1vaS9r_L_eSHANx0fY8N2xgMw@mail.gmail.com> <60ef0242-a3ef-9d0c-5c9b-6cbe9c35305f@redhat.com> <CAE+MWFsUPwVY8V+edrEyS=1NWi_EZFQRE=QCUsjVwyGtDr=EHw@mail.gmail.com>
On 05/16/2017 12:37 PM, Will Hawkins wrote:
> On Tue, May 16, 2017 at 2:33 PM, Jeff Law <law@redhat.com> wrote:
>> On 05/16/2017 12:24 PM, Will Hawkins wrote:
>>> Hello everyone!
>>>
>>> I apologize if this is not the right venue to ask this question and/or
>>> this is a waste of your time.
>>>
>>> I was just wondering if there are statistics that gcc can emit that
>>> includes either a) the average number of instructions per basic block
>>> and/or b) the average size (in bytes) per basic block in a compilation
>>> unit.
>>>
>>> If nothing like this exists, I am more than happy to code something up
>>> if people besides me think that it might be interesting.
>>>
>>> I promise that I googled for information before asking, but I can't
>>> guarantee that I didn't miss anything. Again, I apologize if I just
>>> needed to RTFM better.
>> I don't think we have anything which inherently will give you this
>> information.
>>
>> It'd be a useful thing to have though. Implementation may be made more
>> difficult by insns that generate > 1 instruction.
>>
>> Jeff
>
> Thank you, Mr. Law. I think that this is something I'd really like to
> work on. As I start to take a peak into how hard/easy this is to
> implement, I may circle back and ask some additional technical
> questions.
Sure. On-list is best.
Jeff