Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Compiler FE] build for armv7l on tizen obs #8481

Closed
wants to merge 10 commits into from
Closed

[Compiler FE] build for armv7l on tizen obs #8481

wants to merge 10 commits into from

Conversation

chunseoklee
Copy link
Contributor

No description provided.

seanshpark and others added 2 commits February 22, 2022 10:42
@seanshpark
DRAFT: Compiler FE ARM32 build
53f5f5c 
on-going draft to cross build for ARM32

Signed-off-by: SaeHie Park <[email protected]>
@chunseoklee
Tizen build PoC
0ac050a 
- Add HDF5, PROTBUF tar.gz into packaging folder
- Makefile.arm32.native for gbs qemu native build
- nnfw.spec file update

ONE-DCO-1.0-Signed-off-by: Chunseok Lee <[email protected]>
@chunseoklee chunseoklee mentioned this pull request Feb 22, 2022
Closed
@chunseoklee chunseoklee added the PR/NO TEST Tell CI to not run test label Feb 22, 2022
@hseok-oh
Copy link
Contributor

@chunseoklee @seanshpark Why don't we use flatbuffers latest version (2.0.0) for all compiler and runtime modules? Tizen is using 2.0.0 to build both tensorflow-1.13.1 and tensorflow-2.7.0.

@chunseoklee
Fix Werror on std::move in circle-partitioner
133914e 
GCC 9.2 complains when returning std::move(unique_ptr)
@chunseoklee
Copy link
Contributor Author

@chunseoklee @seanshpark Why don't we use flatbuffers latest version (2.0.0) for all compiler and runtime modules? Tizen is using 2.0.0 to build both tensorflow-1.13.1 and tensorflow-2.7.0

I am not against this.
compiler side has no problem ?

@chunseoklee
Remove arm32_host build on native build
5ec7b6a 
ONE-DCO-1.0-Signed-off-by: Chunseok Lee <[email protected]>
@seanshpark
Copy link
Contributor

I am not against this.
compiler side has no problem ?

I am also OK. Just didn't do any tests :)

@seanshpark
Copy link
Contributor

Why don't we use flatbuffers latest version (2.0.0) for all compiler and runtime modules?

If NPU compiler is also OK then we can try with 2.0.0 :)

@seanshpark
Copy link
Contributor

Related: #8397

@hseok-oh hseok-oh mentioned this pull request Feb 23, 2022
Closed
2 tasks
@chunseoklee
Fix build error
0be8a49 
- disable neon to avoid tflite build
- At this point build is Ok

ONE-DCO-1.0-Signed-off-by: Chunseok Lee <[email protected]>
@chunseoklee
CMAKE_BUILD_TYPE as release
4b12f67 
To fix test fail due to debug's assert

ONE-DCO-1.0-Signed-off-by: Chunseok Lee <[email protected]>
@ejjeong
Copy link
Contributor

ejjeong commented Mar 4, 2022

@chunseoklee Here's the list we discussed offline. (cc/ @hseok-oh)

angkor
hermes
hermes-std
loco
locomotiv
locop
logo
logo-core
luci-env
luci-import
luci-lang
luci-log
luci-logex
luci-pass
luci-plan
luci-profile
luci-service
mio-circle
mio-tflite260
oops
pepper-csv2vec
pepper-str
pepper-strcast
pp

@chunseoklee chunseoklee closed this by deleting the head repository Oct 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
PR/NO TEST Tell CI to not run test
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@chunseoklee @hseok-oh @seanshpark @ejjeong