[PATCH v2] tsan: Add param to disable func-entry-exit instrumentation

Marco Elver elver@google.com
Fri Jun 12 15:33:19 GMT 2020


On Fri, 12 Jun 2020 at 17:27, Martin Liška <mliska@suse.cz> wrote:
>
> On 6/12/20 4:19 PM, Marco Elver wrote:
> > On Fri, 12 Jun 2020, Jakub Jelinek wrote:
> >
> >> On Fri, Jun 12, 2020 at 04:07:57PM +0200, Marco Elver wrote:
> >>> gcc/ChangeLog:
> >>>
> >>>     * params.opt: Add --param=tsan-instrument-func-entry-exit=.
> >>>     * tsan.c (instrument_gimple): Make return value if func entry
> >>>     and exit should be instrumented dependent on param.
> >>>
> >>> gcc/testsuite/ChangeLog:
> >>>
> >>>     * c-c++-common/tsan/func_entry_exit.c: New test.
> >>>     * c-c++-common/tsan/func_entry_exit_disabled.c: New test.
> >>
> >> Ok.
> >
> > Thanks!
> >
> > Somehow the commit message contained the old changelog entry, this is
> > the new one:
> >
> > gcc/ChangeLog:
> >
> >       * gimplify.c (gimplify_function_tree): Optimize and do not emit
> >       IFN_TSAN_FUNC_EXIT in a finally block if we do not need it.
> >       * params.opt: Add --param=tsan-instrument-func-entry-exit=.
> >       * tsan.c (instrument_memory_accesses): Make
> >       fentry_exit_instrument bool depend on new param.
> >
> > gcc/testsuite/ChangeLog:
> >
> >       * c-c++-common/tsan/func_entry_exit.c: New test.
> >       * c-c++-common/tsan/func_entry_exit_disabled.c: New test.
> >
> >
> > -- Marco
> >
>
> Do you already have a write access or should I install the patch?

I do -- I just pushed it.

Thanks,
-- Marco


More information about the Gcc-patches mailing list