riscv-software-src / riscv-software-src/opensbi
understanding -PIE
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.5k
- Forks
- 712
- PR merge metrics
- No merged PRs in 30d
Description
just want to understand why -PIE is hard coded.
if a bare metal build should be created, then this option prevents it.
thus shouldnt the -PIE option be optional?
hints:
currently I always have to apply this patch: https://github.com/riscv-software-src/opensbi/commit/2fe7528c81453a713c6b946551e2d6f08df2d2d6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the referenced commit 2fe7528c81453a713c6b946551e2d6f08df2d2d6 and tracing where -PIE is added to the build flags. Confirm the intended bare-metal build behavior and whether the option should be configurable; done means a bare-metal build can be created without -PIE while the existing default remains supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- build-system, operating-systems
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100