Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in / Register
Toggle navigation
N
ngraph
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Packages
Packages
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
submodule
ngraph
Commits
0ad9ec2c
Commit
0ad9ec2c
authored
6 years ago
by
Sergey Shalnov
Committed by
Robert Kimball
6 years ago
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
IntelGPU backend: Change exception type for unsupported op (#1957)
parent
5b994011
No related merge requests found
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
4 deletions
+1
-4
intelgpu_backend.cpp
src/ngraph/runtime/intelgpu/intelgpu_backend.cpp
+1
-4
No files found.
src/ngraph/runtime/intelgpu/intelgpu_backend.cpp
View file @
0ad9ec2c
...
...
@@ -432,10 +432,6 @@ bool runtime::intelgpu::IntelGPUBackend::compile(shared_ptr<Function> func)
function_output_names
.
push_back
(
get_input_name
(
op
));
break
;
}
case
OP_TYPEID
:
:
GenerateMask
:
{
throw
ngraph_error
(
"GenerateMask isn't yet supported on integrated GPU"
);
}
case
OP_TYPEID
:
:
GetOutputElement
:
{
if
(
op
->
get_inputs
().
empty
()
||
op
->
get_outputs
().
size
()
!=
1
)
...
...
@@ -1508,6 +1504,7 @@ bool runtime::intelgpu::IntelGPUBackend::compile(shared_ptr<Function> func)
case
OP_TYPEID
:
:
Quantize
:
case
OP_TYPEID
:
:
ReduceWindow
:
case
OP_TYPEID
:
:
ReplaceSlice
:
case
OP_TYPEID
:
:
GenerateMask
:
case
OP_TYPEID
:
:
ReverseSequence
:
case
OP_TYPEID
:
:
SelectAndScatter
:
case
OP_TYPEID
:
:
StopGradient
:
...
...
This diff is collapsed.
Click to expand it.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment