performance regression with codegen-units=1
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- performance
Research direction
The issue links to the discussion on pull request #598 and identifies CARGO_PROFILE_RELEASE_CODEGEN_UNITS=1 as a possible trigger. Start by reading that comment and checking the release-build performance impact of this setting; the issue does not name files or tests. Done means the regression is understood and addressed, with the affected performance behavior verified.
Written by the indexing model from the issue text.
Description
https://github.com/uutils/sed/pull/598#issuecomment-6029613732
People can accidentaly met this with personal config for cargo e.g. CARGO_PROFILE_RELEASE_CODEGEN_UNITS=1.
- Dominant language
- Rust
- Stars
- 110
- Forks
- 36
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 30
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from uutils/sed
-
l command: the wrap width comes from the terminal size, and -l is ignoredPossibly taken @SichenLiang claimed this 41 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Back-references are rejected in byte (C locale) modePossibly taken @Omkar-Wagholikar claimed this 5 days ago. Opengood first issue
Difficulty 4/5 3-5 days Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
--posix should disable the GNU regular expression escapes (\? \+ \| \w \s)Possibly taken @LoukasPap claimed this 43 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
s/// replacement: implement the \U \L \u \l \E case-conversion escapesPossibly taken @dedsec-terminal claimed this 33 days ago. Opengood first issue
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
fritzprix/libr-agent#2165 ·
Maintainers usually reply within 1 day
-
area:ecosystem bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Chelis-Lang/chelis#3942 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
review-bot
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day