Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFC] Make tflite frontend more data driven / improve errors. #5519

Closed
wants to merge 2 commits into from

Commits on May 5, 2020

  1. Proof of concept data driven tflite frontend with 2 operators.

    The idea here is to minimise the code duplication for
    asserting that the number of input_tensors and output_tensors
    is as expected for the operator.
    Ramana Radhakrishnan committed May 5, 2020
    Configuration menu
    Copy the full SHA
    05bb3ce View commit details
    Browse the repository at this point in the history

Commits on May 6, 2020

  1. Replace asserts in the tflite frontend with tvm.error

    There are a number of places in the tflite frontend where we use
    asserts to issue an error to the user about something not working.
    
    Instead of using asserts these should be raising a proper
    error that can be caught.
    
    This is an example of how this restructure can happen over
    time and for something to be done around this in the future.
    Ramana Radhakrishnan committed May 6, 2020
    Configuration menu
    Copy the full SHA
    e8b8cf5 View commit details
    Browse the repository at this point in the history