github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-06 16:11:34 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #11215] Assessment of the difficulty in porting CPU architecture for ollama #53901

New Issue
Closed
opened 2026-04-29 04:56:18 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-29 04:56:18 -05:00
Owner
Copy Link

Originally created by @carlosqwqqwq on GitHub (Jun 27, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/11215

The RISC-V ecosystem is maturing rapidly, with an increasing number of software undergoing migration to RISC-V. We developed a tool named RAX to assess the porting complexity of projects migrating to the RISC-V architecture. RAX evaluates complexity by incorporating Cyclomatic Complexity alongside multiple architecture-specific factors, such as the proportion of assembly code instructions and the frequency of inline function usage. The tool classifies the assessment results into three levels: Low, Middle, and High. For example, the simple project is libtool, the medium project is mesa, and the difficult project is gcc.
Your project ollama is very well-known. Our tool RAX evaluates that the complexity of your project is middle. Could you please confirm the assessment accuracy?
More details detected by our tool RAX are shown: the number of lines of architecture-related code are 1353. The number of intrinsic usages is 7123. And the cyclic complexity is 27539. If you want to learn more, please don’t hesitate to us. Thank you.

Originally created by @carlosqwqqwq on GitHub (Jun 27, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/11215 The RISC-V ecosystem is maturing rapidly, with an increasing number of software undergoing migration to RISC-V. We developed a tool named RAX to assess the porting complexity of projects migrating to the RISC-V architecture. RAX evaluates complexity by incorporating Cyclomatic Complexity alongside multiple architecture-specific factors, such as the proportion of assembly code instructions and the frequency of inline function usage. The tool classifies the assessment results into three levels: Low, Middle, and High. For example, the simple project is libtool, the medium project is mesa, and the difficult project is gcc. Your project ollama is very well-known. Our tool RAX evaluates that the complexity of your project is middle. **Could you please confirm the assessment accuracy?** More details detected by our tool RAX are shown: the number of lines of architecture-related code are 1353. The number of intrinsic usages is 7123. And the cyclic complexity is 27539. If you want to learn more, please don’t hesitate to us. Thank you.
GiteaMirror commented 2026-04-29 04:56:19 -05:00
Author
Owner
Copy Link

@pdevine commented on GitHub (Jul 1, 2025):

The problem with supporting RISC-V isn't just porting Ollama to the platform, but testing and supporting it in future versions which can create significant drag on the product. It's not that we would be against supporting RISC-V in the future, but we would wait until there was significant demand.

RISC-V is covered in a different issue though, so I'm doing to go ahead and close this as a dupe.

<!-- gh-comment-id:3025108116 --> @pdevine commented on GitHub (Jul 1, 2025): The problem with supporting RISC-V isn't just porting Ollama to the platform, but testing and supporting it in future versions which can create significant drag on the product. It's not that we would be against supporting RISC-V in the future, but we would wait until there was significant demand. RISC-V is covered in a different issue though, so I'm doing to go ahead and close this as a dupe.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#53901
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?