cpu gpu transform #7085
Closed
cpu gpu transform #7085
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… cpu-gpu-transform
… cpu-gpu-transform
… cpu-gpu-transform Conflicts: paddle/framework/data_transform.h paddle/framework/data_transform_test.cc paddle/framework/operator.cc
… cpu-gpu-transform
reyoung
reviewed
Jan 2, 2018
| /** | ||
| * register a unique name for one module of data transform | ||
| */ | ||
| #define REGISTER_DATA_TRANSFORM_MODEULE(module) \ |
Collaborator
There was a problem hiding this comment.
Here, we should check the namespace of this symbol.
reyoung
reviewed
Jan 2, 2018
| namespace paddle { | ||
| namespace framework { | ||
|
|
||
| OpKernelType k0(proto::DataType::FP32, platform::CPUPlace(), |
Collaborator
There was a problem hiding this comment.
This will generate symbol k0, which is meaningless for other .cc files.
Member
Author
|
fixed by #7191 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix: #7050