areusch commented on a change in pull request #7952: URL: https://github.com/apache/tvm/pull/7952#discussion_r638351376
########## File path: include/tvm/ir/instrument.h ########## @@ -0,0 +1,127 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one + * or more contributor license agreements. See the NOTICE file + * distributed with this work for additional information + * regarding copyright ownership. The ASF licenses this file + * to you under the Apache License, Version 2.0 (the + * "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, + * software distributed under the License is distributed on an + * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + * KIND, either express or implied. See the License for the + * specific language governing permissions and limitations + * under the License. + */ + +/*! + * \file tvm/ir/instrument.h + * + * This file introduces a pass instrument infrastructure, inspired by LLVM and MLIR. + * It inserts instrumentation points around passes. + */ +#ifndef TVM_IR_INSTRUMENT_H_ +#define TVM_IR_INSTRUMENT_H_ + +#include <tvm/node/reflection.h> +#include <tvm/runtime/container.h> + +#include <utility> +#include <vector> + +namespace tvm { + +class IRModule; + +// Forward class for PassInstrumentNode methods +namespace transform { +class PassInfo; +} // namespace transform + +namespace instrument { + +/*! + * \brief PassInstrumentNode forms an instrument implementation. + * It provides API for users to register callbacks at different instrumentation points. + * + * Within a pass context (tvm::transfom::PassContext), the instrumentation call sequence will like: + * + * Instrument SetUp() + * + * if (Instrument Before Pass()) Review comment: hi @zackcquic, here i'm referencing the python `__exit__` function signature. you can see it used in context as "exit" [here](https://www.python.org/dev/peps/pep-0343/#specification-the-with-statement). i'm speaking fairly broadly, though--in Python, sys.exc_info() captures any pending exception as a tuple (type, value, traceback) whereas in c++ the most we get is information from catching e.g. `std::runtime_error`. By "result notation," I mainly mean some appropriate argument to `after_pass` to indicate why the `after_pass` is being invoked--it could be because: 1. a following `before_pass` errored 2. pass() was invoked and threw an error 3. pass() was invoked and finished cleanly 4. a preceding after_pass errored -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
