diff options
author | Josh Stone <jistone@redhat.com> | 2010-03-18 15:39:42 -0700 |
---|---|---|
committer | Josh Stone <jistone@redhat.com> | 2010-03-18 15:48:06 -0700 |
commit | 9fab2262961c9cd1ab3efea5d362b8a6a1c0c7c3 (patch) | |
tree | 4710c7737f853cc7d921e21ff1f9136ef32e991d /runtime/stack.c | |
parent | 8fb91f5fe6cdcab379144f4ebddae6f72816f2c3 (diff) | |
download | systemtap-steved-9fab2262961c9cd1ab3efea5d362b8a6a1c0c7c3.tar.gz systemtap-steved-9fab2262961c9cd1ab3efea5d362b8a6a1c0c7c3.tar.xz systemtap-steved-9fab2262961c9cd1ab3efea5d362b8a6a1c0c7c3.zip |
PR11346: Move the skip-badvars logic into const-folding
The const_folder is where we prune constant expressions, like
conditionals based on a @defined($foo), so we want to give this a chance
to work before skip-badvars comes in and throws a warning.
As an added bonus, this makes skip-badvars more generic, so it will work
even for non-dwarf $target variables.
* elaborate.cxx (const_folder::visit_target_symbol): Enact skip-badvars.
* tapsets.cxx (dwarf_var_expanding_visitor::visit_target_symbol): Don't
worry about badvars here anymore. Save the error now, clean up later.
* testsuite/semok/badvar_undefined.stp: Test that @defined with
skip-badvars doesn't throw any warnings.
Diffstat (limited to 'runtime/stack.c')
0 files changed, 0 insertions, 0 deletions