Skip to content

Conversation

@jerryzh168
Copy link
Contributor

@jerryzh168 jerryzh168 commented Oct 24, 2019

Stack from ghstack:

Summary:
att

Test Plan:
python test/test_quantized_tensor.py

Reviewers:
gchanan

Subscribers:

Tasks:

Tags:

Differential Revision: D18255247

Summary:
att

Test Plan:
python test/test_quantized_tensor.py

Reviewers:
gchanan

Subscribers:

Tasks:

Tags:

[ghstack-poisoned]
Summary:
att

Test Plan:
python test/test_quantized_tensor.py

Reviewers:
gchanan

Subscribers:

Tasks:

Tags:

[ghstack-poisoned]
jerryzh168 added a commit that referenced this pull request Oct 24, 2019
Summary:
att

Test Plan:
python test/test_quantized_tensor.py

Reviewers:
gchanan

Subscribers:

Tasks:

Tags:

ghstack-source-id: cad7afa
Pull Request resolved: #28612
Summary:
att

Test Plan:
python test/test_quantized_tensor.py

Reviewers:
gchanan

Subscribers:

Tasks:

Tags:

[ghstack-poisoned]
jerryzh168 added a commit that referenced this pull request Oct 25, 2019
Summary:
att

Test Plan:
python test/test_quantized_tensor.py

Reviewers:
gchanan

Subscribers:

Tasks:

Tags:

ghstack-source-id: ffb90cb
Pull Request resolved: #28612
Copy link
Contributor

@gchanan gchanan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you remind me why quantized tensors use qint8 storages and not int8 storages?

@jerryzh168
Copy link
Contributor Author

can you remind me why quantized tensors use qint8 storages and not int8 storages?

I don't remember exactly, but one reason I can think of right now is because when we inspect the storage we want to distinguish between qint8 and int8 storage?

Summary:
att

Test Plan:
python test/test_quantized_tensor.py

Reviewers:
gchanan

Subscribers:

Tasks:

Tags:

[ghstack-poisoned]
jerryzh168 added a commit that referenced this pull request Oct 25, 2019
Summary:
att

Test Plan:
python test/test_quantized_tensor.py

Reviewers:
gchanan

Subscribers:

Tasks:

Tags:

ghstack-source-id: 893238c
Pull Request resolved: #28612
Copy link
Contributor

@gchanan gchanan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does this support copy_, i.e. a.copy_(b)?

Summary:
att

Test Plan:
python test/test_quantized_tensor.py

Reviewers:
gchanan

Subscribers:

Tasks:

Tags:

[ghstack-poisoned]
jerryzh168 added a commit that referenced this pull request Oct 29, 2019
Summary:
att

Test Plan:
python test/test_quantized_tensor.py

Reviewers:
gchanan

Subscribers:

Tasks:

Tags:

ghstack-source-id: a58fafe
Pull Request resolved: #28612
@jerryzh168
Copy link
Contributor Author

does this support copy_, i.e. a.copy_(b)?

Yes it does, test added

@jerryzh168 jerryzh168 requested a review from gchanan October 29, 2019 23:05
Summary:
att

Test Plan:
python test/test_quantized_tensor.py

Reviewers:
gchanan

Subscribers:

Tasks:

Tags:

[ghstack-poisoned]
Summary:
att

Test Plan:
python test/test_quantized_tensor.py

Reviewers:
gchanan

Subscribers:

Tasks:

Tags:

[ghstack-poisoned]
Summary:
att

Test Plan:
python test/test_quantized_tensor.py

Reviewers:
gchanan

Subscribers:

Tasks:

Tags:

[ghstack-poisoned]
jerryzh168 added a commit that referenced this pull request Oct 31, 2019
Summary:
att

Test Plan:
python test/test_quantized_tensor.py

Reviewers:
gchanan

Subscribers:

Tasks:

Tags:

ghstack-source-id: 92ff628
Pull Request resolved: #28612
@jerryzh168 jerryzh168 requested a review from gchanan October 31, 2019 20:52
@jerryzh168 jerryzh168 changed the title [quant] Quantized Tensor support copy [quant] Quantized Tensor support deepcopy Nov 1, 2019
@jerryzh168
Copy link
Contributor Author

@gchanan this PR only adds support for deepcopy, normal quantized tensor copy is already supported in another PR: #21852

Copy link
Contributor

@gchanan gchanan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this, in-and-of-itself, looks fine for deepcopy.

Why was the existing copy behavior (of clobbering the quantizer of the destination) chosen? That seems surprising, and I don't know why you even want to copy in that case.

@jerryzh168
Copy link
Contributor Author

this, in-and-of-itself, looks fine for deepcopy.

Why was the existing copy behavior (of clobbering the quantizer of the destination) chosen? That seems surprising, and I don't know why you even want to copy in that case.

It's because of:

param.copy_(input_param)

@facebook-github-bot
Copy link
Contributor

This pull request has been merged in 23193c1.

zdevito pushed a commit to zdevito/ATen that referenced this pull request Nov 2, 2019
Summary:
Pull Request resolved: pytorch/pytorch#28612

att

Test Plan:
python test/test_quantized_tensor.py

Imported from OSS

Differential Revision: D18255247

fbshipit-source-id: 814b12640fdf9d79b27482ee642ce430dbaeea68
soumith pushed a commit that referenced this pull request Nov 4, 2019
Summary:
Pull Request resolved: #28612

att

Test Plan:
python test/test_quantized_tensor.py

Imported from OSS

Differential Revision: D18255247

fbshipit-source-id: 814b12640fdf9d79b27482ee642ce430dbaeea68
@facebook-github-bot facebook-github-bot deleted the gh/jerryzh168/120/head branch November 5, 2019 15:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants