You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tvm.apache.org by GitBox <gi...@apache.org> on 2021/02/02 20:25:13 UTC

[GitHub] [tvm] cbalint13 commented on pull request #7392: Fix rand_r() proper inclusion

cbalint13 commented on pull request #7392:
URL: https://github.com/apache/tvm/pull/7392#issuecomment-771956316


   > and to clarify--i'd love to improve the documentation/tutorial, if there are specific parts you found confusing, i'd definitely be interested to learn that.
   
   @areusch ,
   
   First thank you for taking your time into the problem !
   
   To not mix up things:
   
     **A.** we could forbid  (+message) if target ```micro('host')``` is used with cross/remote ```ZephyrCompiler``` & vice versa ? 
     **B.** what if someone don't want ```ZephyrCompiler``` but  a ```DefaultCompiler``` instead ?
      
     By ```DefaultCompiler``` i meant my own installed cross ```arm-none-eabi-g++``` in our case (which seems to be invoked at all).
     By *local/generic* vs *remote/specific* terms i meant ```micro('host')``` vs ```micro(<device>)```
   
   So,
   
     * Should we introduce a ```CrossCompiler``` too for such purposes  (as a more generic form) ?
     * Then should we forbid ```local``` target to generate remote/cross target  except ```CrossCompiler``` ?
   
   
   ----
   
    Would like to understand and see your reasoning on the subject first.
   
   
   
   


----------------------------------------------------------------
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:
users@infra.apache.org