This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug tapsets/17242] tapsets should avoid delayed-init globals


https://sourceware.org/bugzilla/show_bug.cgi?id=17242

Josh Stone <jistone at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|systemtap at sourceware dot org    |jistone at redhat dot com

--- Comment #1 from Josh Stone <jistone at redhat dot com> ---
PR6466's commit ba6f838d2471 reveals one hiccup in this idea.  If the init+read
function isn't referenced, but something else pulls that tapset file in, then
the global array would be created, but then it would be noticed as unreferenced
and get elided.  Now with a begin probe also getting pulled in to initialize
the global, that's an independent reference to keep it around.

I think that's an acceptable tradeoff, but if we can detect and remove the
only-written global too, we'll get the best of both worlds.

-- 
You are receiving this mail because:
You are the assignee for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]