[Bug gprofng/30897] Support source view for "referenced" source (e.g. bison)

2023-11-15 Thread kurt.goebel at oracle dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30897

Kurt Goebel  changed:

   What|Removed |Added

 CC||kurt.goebel at oracle dot com
   Priority|P2  |P3

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug gprofng/30897] Support source view for "referenced" source (e.g. bison)

2023-09-26 Thread bugmenot at mailinator dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30897

--- Comment #3 from John Doe  ---
(In reply to Vladimir Mezentsev from comment #1)
> It is a bug.
> A workaround could be to look at the functions from QLParser.yy.
> For example:
> 
> gprofng display text -dis QL::yylex
> gprofng display text -source QL::yylex

This _kind of_ works but still shows the .tab.cc source, not the .yy one.

The point is that some people may are interested "in the whole package" - then
they inspect the tab.cc, but most will be only interested in "their code", so
looking at the .yy will be more useful.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug gprofng/30897] Support source view for "referenced" source (e.g. bison)

2023-09-26 Thread bugmenot at mailinator dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30897

--- Comment #2 from John Doe  ---
Please also consider that (depending on the generator) some functions don't
"start" in their "real sources". Actually this is also the case for
QLParser.yy, where yylex is declared at line 42 but actually defined in the
generated C source.
This is also similar for other generators which may translate


orig.def
~~~
MACRO1(a(4),b)
MACRO2(c,d(3))
~~~

to

program.c
~~~
MACRO1_
{
 int a;
 int b;
#line orig.def 1
 a = 4; b = (somefunc(a);
#line program.c 8
 assert (a == b);
}

MACRO02_
{
 int c;
 int d = 3:
#line orig.def 2
 c = otherfunc(d);
#line program.c 18
 assert (d == -c);
}
~~~

As the program.c file is generated its profiling is only minor interesting, but
it will be very good to have orig.def in the profiler (it is visible in GDB and
coredumps, too).

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug gprofng/30897] Support source view for "referenced" source (e.g. bison)

2023-09-25 Thread vladimir.mezentsev at oracle dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30897

Vladimir Mezentsev  changed:

   What|Removed |Added

 Status|UNCONFIRMED |ASSIGNED
   Last reconfirmed||2023-09-26
 Ever confirmed|0   |1

--- Comment #1 from Vladimir Mezentsev  
---
It is a bug.
A workaround could be to look at the functions from QLParser.yy.
For example:

gprofng display text -dis QL::yylex
gprofng display text -source QL::yylex

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug gprofng/30897] Support source view for "referenced" source (e.g. bison)

2023-09-25 Thread sam at gentoo dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=30897

Sam James  changed:

   What|Removed |Added

 CC||sam at gentoo dot org

-- 
You are receiving this mail because:
You are on the CC list for the bug.