- Remove 'Validated Commands and Expected Outputs' section (lines 71-95) - This information is already covered in 'Validation Workflow' section - Reduces redundancy and improves document clarity Generated with [codeagent](https://github.com/qbox/codeagent) Co-authored-by: xgopilot <noreply@goplus.org>
4.2 KiB
LLGo Project AI Assistant Guide
This document provides essential information for AI assistants to help fix bugs and implement features in the LLGo project.
About LLGo
LLGo is a Go compiler based on LLVM designed to better integrate Go with the C ecosystem, including Python and JavaScript. It's a subproject of the XGo project that aims to expand the boundaries of Go/XGo for game development, AI and data science, WebAssembly, and embedded development.
Project Structure
cmd/llgo- Main llgo compiler command (usage similar togocommand)cl/- Core compiler logic that converts Go packages to LLVM IRssa/- LLVM IR file generation using Go SSA semanticsinternal/build/- Build process orchestrationruntime/- LLGo runtime librarychore/- Development tools (llgen, llpyg, ssadump, etc.)_demo/- Example programs demonstrating C/C++ interop (c/hello,c/qsort) and Python integration (py/callpy,py/numpy)_cmptest/- Comparison tests to verify the same program gets the same output with Go and LLGo
Development Environment
For detailed dependency requirements and installation instructions, see the Dependencies and How to install sections in the README.
Build Commands
Build the entire project
go build -v ./...
Build llgo command specifically
go build -o llgo ./cmd/llgo
Check llgo version
llgo version
Testing & Validation
The following commands and workflows are essential when fixing bugs or implementing features in the LLGo project:
Run all tests
go test ./...
Note: Some tests may fail if optional dependencies (like Python) are not properly configured. The test suite includes comprehensive tests for:
- Compiler functionality
- SSA generation
- C interop
- Python integration (requires Python development headers)
Write and run tests for your changes
When adding new functionality or fixing bugs, create appropriate test cases:
# Add your test to the relevant package's *_test.go file
# Then run tests for that package
go test ./path/to/package
# Or run all tests
go test ./...
Important: The LLGO_ROOT environment variable must be set to the repository root when running llgo commands during development.
Code Quality
Format code
go fmt ./...
Run static analysis
go vet ./...
Note: Currently reports some issues related to lock passing by value in ssa/type_cvt.go and a possible unsafe.Pointer misuse in cl/builtin_test.go. These are known issues.
Common Development Tasks
Install llgo for system-wide use
./install.sh
Build development tools
go install -v ./cmd/...
go install -v ./chore/...
Key Modules for Understanding
ssa- Generates LLVM IR using Go SSA semanticscl- Core compiler converting Go to LLVM IRinternal/build- Orchestrates the compilation process
Debugging
Disable Garbage Collection
For testing purposes, you can disable GC:
LLGO_ROOT=/path/to/llgo llgo run -tags nogc .
Validation Workflow
When fixing bugs or implementing features, follow this workflow:
- Make your code changes
- Write or update tests - All bug fixes and features MUST include tests
- Run the test suite:
go test ./... - Build the project:
go build -v ./... - Test with examples: Run relevant demos from
_demo/directory - Format code:
go fmt ./... - Run static analysis:
go vet ./...
LLGO_ROOT Environment Variable
CRITICAL: Always set LLGO_ROOT to the repository root when running llgo during development:
export LLGO_ROOT=/path/to/llgo
# or
LLGO_ROOT=/path/to/llgo llgo run .
Important Notes
- Testing Requirement: All bug fixes and features MUST include tests
- Demo Directory: Examples in
_demoare prefixed with_to prevent standardgocommand from trying to compile them - Defer in Loops: LLGo intentionally does not support
deferin loops (considered bad practice) - C Ecosystem Integration: LLGo uses
go:linknamedirective to link external symbols through ABI - Python Integration: Third-party Python libraries require separate installation of library files