Re: [apache/incubator-tvm] [VOTE] Release Apache TVM (incubating) v0.7.0.rc0 (#6622)

2020-10-05 Thread Byung-Gon Chun
+1 (binding)

- I checked the signature and hash. 
- DISCLAIMER, LICENSE, and NOTICE look good
- No unexpected binary files
- The code compiles and runs

Thanks.
-Gon

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-tvm/issues/6622#issuecomment-703514088

[Apache TVM Discuss] [Development] Creating store_at in TVM

2020-10-05 Thread Matt Barrett via Apache TVM Discuss


Halide provides the scheduling primitive `store_at` (as well as `store_root`) 
to move where the storage of a tensor happens independent of the compute. This 
is very useful for when we want to make use of the sliding window optimization 
and create rolling buffers - both of which can be critical in reducing memory 
usage on memory constrained devices. For examples of how this is used in 
Halide, you can reference the tutorial on multi-stage pipelines: 
https://halide-lang.org/tutorials/tutorial_lesson_08_scheduling_2.html.

Is this something we can emulate in TVM with the existing scheduling 
intrinsics? And if not, is this something the design of TE would permit? In the 
latter case, I'd be interested to know whether it would currently be worth 
implementing in TE given the change of approach in TensorIR, or whether it 
would be better to wait.

Thanks

cc @junrushao1994 @tqchen  @manupa-arm





---
[Visit Topic](https://discuss.tvm.apache.org/t/creating-store-at-in-tvm/8083/1) 
to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, [click 
here](https://discuss.tvm.apache.org/email/unsubscribe/b2f67173b676bcd17bdbfae4fbc081207956e35c0740a6e5cebdd664bd29a2a3).


[Apache TVM Discuss] [Development] Creating store_at in TVM

2020-10-05 Thread Manupa Karunaratne via Apache TVM Discuss


Yes definitely useful to have! might save a lot of hacks/workarounds that would 
otherwise needed to get the same functionality. Also cc : @spectrometerHBH 
@merrymercy





---
[Visit Topic](https://discuss.tvm.apache.org/t/creating-store-at-in-tvm/8083/2) 
to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, [click 
here](https://discuss.tvm.apache.org/email/unsubscribe/6cae5932ea4e8f2728287de6973573b60848301b4819919a3a8e3366d875b1d9).


Re: [apache/incubator-tvm] [VOTE] Release Apache TVM (incubating) v0.7.0.rc0 (#6622)

2020-10-05 Thread Zhao Wu
+1, I checked

- signature and hash
- LICENSE, DISCLAIMER and NOTICE
- Version
- Code compiles


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-tvm/issues/6622#issuecomment-703569247

Re: [apache/incubator-tvm] [VOTE] Release Apache TVM (incubating) v0.7.0.rc0 (#6622)

2020-10-05 Thread Zhi
+1 (binding)

- Checked the signature and hash
- The code compiles
- Checked LICESE and NOTICE

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-tvm/issues/6622#issuecomment-703743085

Re: [apache/incubator-tvm] [VOTE] Release Apache TVM (incubating) v0.7.0.rc0 (#6622)

2020-10-05 Thread Thierry Moreau
+1 (binding):

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-tvm/issues/6622#issuecomment-703874194

Re: [apache/incubator-tvm] [VOTE] Release Apache TVM (incubating) v0.7.0.rc0 (#6622)

2020-10-05 Thread Jared Roesch
+1 (binding)
* Checked the code compiles
* Checked License and Notice
* Version

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-tvm/issues/6622#issuecomment-703882812

Re: [apache/incubator-tvm] [RFC] Move to use main as default branch (#6623)

2020-10-05 Thread Chris Hoge
This change would be in accordance with the [Apache Code of 
Conduct](https://www.apache.org/foundation/policies/conduct.html) across 
several dimensions.

1. It creates a more open community.
2. It shows empathy for the diverse open source community.
3. It encourages collaboration.
4. It is being careful with the words we choose.
5. It aligns with the diversity statement.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-tvm/issues/6623#issuecomment-703897640

[Apache TVM Discuss] [Development] [RFC] Move to use main as default branch

2020-10-05 Thread Chris Hoge via Apache TVM Discuss


>From the [pull request](https://github.com/apache/incubator-tvm/issues/6623) 
>that @tqchen sent up over the weekend:

> Dear TVM Community:
> 
> In light of recent proposed change of [github's default branch from master to 
> main](https://github.blog/changelog/2020-10-01-the-default-branch-for-newly-created-repositories-is-now-main/).
>  It would be great for the community to consider such a change. Given the 
> minimum impact to set it up. We believe is a net positive to the community 
> and also keeps us up to the latest github convention.
> 
> This thread seeks formal lazy consensus :) Everyone is also more than 
> welcomed to share their thoughts.
> 
> TQ





---
[Visit 
Topic](https://discuss.tvm.apache.org/t/rfc-move-to-use-main-as-default-branch/8087/1)
 to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, [click 
here](https://discuss.tvm.apache.org/email/unsubscribe/006d857ed3ff408845e6464ba9e34626a5724c1efe0e276bd8f18a3d9fc6a702).


[Apache TVM Discuss] [Development] [RFC] Move to use main as default branch

2020-10-05 Thread Chris Hoge via Apache TVM Discuss


This change would be in accordance with the [Apache Code of 
Conduct](https://www.apache.org/foundation/policies/conduct.html) across 
several dimensions.

1. It creates a more open community.
2. It shows empathy for the diverse open source community.
3. It encourages collaboration by using more inclusive language.
4. It is being careful with the words we choose.
5. It aligns with the diversity statement.





---
[Visit 
Topic](https://discuss.tvm.apache.org/t/rfc-move-to-use-main-as-default-branch/8087/2)
 to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, [click 
here](https://discuss.tvm.apache.org/email/unsubscribe/07a15fdc1feae1bd84f004439a90da5a075343bb93102d01fb258135ce74f3ef).