Re: Symbol Size Variance

On 25/05/18 07:54, Sebastian Huber wrote: On 24/05/18 17:46, Gedare Bloom wrote: On Thu, May 24, 2018 at 9:05 AM, Joel Sherrill wrote: On Thu, May 24, 2018, 8:04 AM Gedare Bloom wrote: On Wed, May 23, 2018 at 2:28 AM, Sebastian Huber wrote: On 23/05/18 01:06, Joel Sherrill wrote: Or we m

Re: Symbol Size Variance

On 24/05/18 17:46, Gedare Bloom wrote: On Thu, May 24, 2018 at 9:05 AM, Joel Sherrill wrote: On Thu, May 24, 2018, 8:04 AM Gedare Bloom wrote: On Wed, May 23, 2018 at 2:28 AM, Sebastian Huber wrote: On 23/05/18 01:06, Joel Sherrill wrote: Or we may need to limit ourselves to source line m

Re: Symbol Size Variance

On Thu, May 24, 2018, 10:46 AM Gedare Bloom wrote: > On Thu, May 24, 2018 at 9:05 AM, Joel Sherrill wrote: > > > > > > On Thu, May 24, 2018, 8:04 AM Gedare Bloom wrote: > >> > >> On Wed, May 23, 2018 at 2:28 AM, Sebastian Huber > >> wrote: > >> > On 23/05/18 01:06, Joel Sherrill wrote: > >> >>

Re: Symbol Size Variance

On Thu, May 24, 2018 at 9:05 AM, Joel Sherrill wrote: > > > On Thu, May 24, 2018, 8:04 AM Gedare Bloom wrote: >> >> On Wed, May 23, 2018 at 2:28 AM, Sebastian Huber >> wrote: >> > On 23/05/18 01:06, Joel Sherrill wrote: >> >> >> >> Or we may need to limit ourselves to source line mapping on a pe

Re: Symbol Size Variance

On Thu, May 24, 2018, 8:04 AM Gedare Bloom wrote: > On Wed, May 23, 2018 at 2:28 AM, Sebastian Huber > wrote: > > On 23/05/18 01:06, Joel Sherrill wrote: > >> > >> Or we may need to limit ourselves to source line mapping on a per > >> executable > >> basis. And generate reports using gcov output

Re: Symbol Size Variance

On Wed, May 23, 2018 at 2:28 AM, Sebastian Huber wrote: > On 23/05/18 01:06, Joel Sherrill wrote: >> >> Or we may need to limit ourselves to source line mapping on a per >> executable >> basis. And generate reports using gcov output if we see methods change >> between executables. I have shied awa

Re: Symbol Size Variance

On 23/5/18 11:06 am, Joel Sherrill wrote: > On Tue, May 22, 2018 at 5:45 PM, Chris Johns > wrote: > On 22/5/18 11:14 pm, Joel Sherrill wrote: > > On Mon, May 21, 2018, 7:44 PM Chris Johns > >

Re: Symbol Size Variance

On 23/05/18 01:06, Joel Sherrill wrote: Or we may need to limit ourselves to source line mapping on a per executable basis. And generate reports using gcov output if we see methods change between executables. I have shied away from gcov as the primary format because I don't see how to do subexpr

Re: Symbol Size Variance

On Tue, May 22, 2018 at 5:45 PM, Chris Johns wrote: > On 22/5/18 11:14 pm, Joel Sherrill wrote: > > On Mon, May 21, 2018, 7:44 PM Chris Johns > > wrote: > > On 22/5/18 9:12 am, Joel Sherrill wrote: > > > > > > Attached is a shell script (pokes Chris) which ca

Re: Symbol Size Variance

On 22/5/18 11:14 pm, Joel Sherrill wrote: > On Mon, May 21, 2018, 7:44 PM Chris Johns > wrote: > On 22/5/18 9:12 am, Joel Sherrill wrote: > > > > Attached is a shell script (pokes Chris) which calculates the size of  > > the specified symbol across a set of

Re: Symbol Size Variance

On Mon, May 21, 2018, 7:44 PM Chris Johns wrote: > On 22/5/18 9:12 am, Joel Sherrill wrote: > > > > Attached is a shell script (pokes Chris) which calculates the size of > > the specified symbol across a set of .exe files. > > > > [joel@rtbf64c samples]$ /tmp/cmp_sizes -a sparc -s > > _Workspace_

Re: Symbol Size Variance

On 22/5/18 9:12 am, Joel Sherrill wrote: > > Attached is a shell script (pokes Chris) which calculates the size of  > the specified symbol across a set of .exe files.  > > [joel@rtbf64c samples]$ /tmp/cmp_sizes -a sparc -s > _Workspace_Allocate_or_fatal_error *.exe > Size report for _Workspace_Al

Symbol Size Variance

Hi Attached is a shell script (pokes Chris) which calculates the size of the specified symbol across a set of .exe files. [joel@rtbf64c samples]$ /tmp/cmp_sizes -a sparc -s _Workspace_Allocate_or_fatal_error *.exe Size report for _Workspace_Allocate_or_fatal_error base_sp.exe - 0x4000c5a