#3201 closed defect (invalid)
ParModelica cannot parse kernel functions
Reported by: | gustaf | Owned by: | mahge930 |
---|---|---|---|
Priority: | high | Milestone: | never |
Component: | ParModelica | Version: | trunk |
Keywords: | ParModelica | Cc: |
Description
A fairly small kernel function:
kernel function KernelTestNull end KernelTestNull;
Will result in a slightly bigger parsing failure:
$ omc -g=ParModelica KernelTestNull.mo Error processing file: KernelTestNull.mo Failed to parse file: KernelTestNull.mo! [.../KernelTestNull.mo:1:0-1:6:writable] Error: Parser error: Unexpected token near: kernel (IDENT) # Error encountered! Exiting... # Please check the error message and the flags. Failed to parse file: KernelTestNull.mo! Execution failed!
Trying a bigger example like:
package KernelTest parallel function multiply input Integer a; input Integer b; output Integer c; algorithm c := a * b; end multiply; kernel function arrayElemWiseMultiply input Integer m; input Integer A[m]; input Integer B[m]; output Integer C[m]; protected Integer id; algorithm id := ocl_get_global_id(0); C[id] := multiply(A[id],B[id]); end arrayElemWiseMultiply; end KernelTest;
Will give a similar (but slightly different) parsing error:
$ omc -g=ParModelica KernelTest.mo Error processing file: KernelTest.mo Failed to parse file: KernelTest.mo! [.../KernelTest.mo:10:3-10:9:writable] Error: No viable alternative near token: kernel # Error encountered! Exiting... # Please check the error message and the flags. Failed to parse file: KernelTest.mo! Execution failed!
$ omc --version
1.9.2+dev (r24991)
Change History (3)
comment:1 Changed 10 years ago by gustaf
comment:2 Changed 9 years ago by mahge930
- Resolution set to invalid
- Status changed from new to closed
Documentation issue.
comment:3 Changed 9 years ago by dietmarw
- Milestone changed from Future to never
Sorting away the closed as invalid, won't fix and duplicate tickets from Future.
Reading the presentation linked in #3199 -> s/kernel/parkernel/
...so this is one more (user reading wrong) documentation issue.