Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Bug: b3990 ascend cann build error #10105

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
Closed
HMING666666 opened this issue Oct 31, 2024 · 4 comments
Closed

Bug: b3990 ascend cann build error #10105

HMING666666 opened this issue Oct 31, 2024 · 4 comments
Assignees
@hipudding
Labels
Ascend NPU issues specific to Ascend NPUs low severity Used to report low severity bugs in llama.cpp (e.g. cosmetic issues, non critical UI glitches)

Comments

@HMING666666
Copy link

What happened?

27.81 /app/ggml/src/ggml-cann.cpp: In function 'ggml_backend_buffer* ggml_backend_cann_host_buffer_type_alloc_buffer(ggml_backend_buffer_type_t, size_t)':
27.81 /app/ggml/src/ggml-cann.cpp:1230:19: error: 'struct ggml_backend_buffer_i' has no member named 'get_name'; did you mean 'get_base'?
27.81 1230 | buffer->iface.get_name = ggml_backend_cann_host_buffer_name;
27.81 | ^~~~~~~~
27.81 | get_base
27.85 gmake[3]: *** [ggml/src/CMakeFiles/ggml.dir/build.make:174: ggml/src/CMakeFiles/ggml.dir/ggml-cann.cpp.o] Error 1
27.85 gmake[2]: *** [CMakeFiles/Makefile2:1619: ggml/src/CMakeFiles/ggml.dir/all] Error 2
27.85 gmake[1]: *** [CMakeFiles/Makefile2:3368: examples/main/CMakeFiles/llama-cli.dir/rule] Error 2
27.85 gmake: *** [Makefile:1323: llama-cli] Error 2

Name and Version

version: b3990
os: openeuleros:22.03
framework: ascend-cann

What operating system are you seeing the problem on?

Mac

Relevant log output

No response
@HMING666666 HMING666666 added bug-unconfirmed low severity Used to report low severity bugs in llama.cpp (e.g. cosmetic issues, non critical UI glitches) labels Oct 31, 2024
@slaren
Copy link
Member

slaren commented Oct 31, 2024

@hipudding sorry, I probably introduced this issue when adapting the CANN backend to the interface changes in #10026. It would be useful to have a build of the CANN backend in the CI to avoid this from happening again in the future.

@hipudding hipudding added the Ascend NPU issues specific to Ascend NPUs label Nov 4, 2024
@hipudding
Copy link
Collaborator

@hipudding sorry, I probably introduced this issue when adapting the CANN backend to the interface changes in #10026. It would be useful to have a build of the CANN backend in the CI to avoid this from happening again in the future.

Yes, it is necessary to have CI to take care of the backend of CANN. We are limited by hardware resource issues and have not yet provided CI resources. We will solve this problem as soon as possible.

@hipudding hipudding self-assigned this Nov 4, 2024
@hipudding hipudding mentioned this issue Nov 4, 2024
Merged
4 tasks
@slaren
Copy link
Member

slaren commented Nov 4, 2024

We are limited by hardware resource issues and have not yet provided CI resources.

A build of the CANN backend in .github/workflows/build.yml would be useful to check that everything builds correctly. A full CI that can run tests on Ascend hardware would be better of course, but the build test can be added without requiring more resources.

@hipudding
Copy link
Collaborator

We are limited by hardware resource issues and have not yet provided CI resources.

A build of the CANN backend in .github/workflows/build.yml would be useful to check that everything builds correctly. A full CI that can run tests on Ascend hardware would be better of course, but the build test can be added without requiring more resources.

Yes, build test is not require any Ascend hardware, we will add this build test workflow ASAP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hipudding hipudding

Labels
Ascend NPU issues specific to Ascend NPUs low severity Used to report low severity bugs in llama.cpp (e.g. cosmetic issues, non critical UI glitches)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@slaren @hipudding @HMING666666