bitstring: fix match-at-start bug
ClosedPublic
Actions

Authored by dougm on May 10 2022, 3:29 AM.

Tags

None

Referenced Files

	Unknown Object (File)
	Thu, Nov 14, 12:15 AM

	Unknown Object (File)
	Oct 21 2024, 11:49 AM

	Unknown Object (File)
	Oct 4 2024, 10:07 PM

	Unknown Object (File)
	Oct 2 2024, 2:08 PM

	Unknown Object (File)
	Oct 2 2024, 4:26 AM

	Unknown Object (File)
	Oct 2 2024, 12:26 AM

	Unknown Object (File)
	Oct 1 2024, 4:36 AM

	Unknown Object (File)
	Sep 30 2024, 11:12 AM

View All 40 Files

Subscribers

imp

Details

Reviewers

markj

Commits

rGbb75580e0370: bitstring: fix ff_area() when start!=0
rG6e7a585348d5: bitstring: fix ff_area() when start!=0

Summary

commit 84e2ae64c597000a0 introduced an error in the ff*_area_at functions for nonzero start parameters when the bit range sought was found immediately. It mistakenly replace '_value = _start' with '_value = 0' in initialization. Undo that mistake.

Diff Detail

Lint

Lint Skipped

Unit

Tests Skipped

Event Timeline

dougm requested review of this revision.May 10 2022, 3:29 AM

dougm created this revision.

dougm added a reviewer: markj.

markj accepted this revision.May 10 2022, 1:06 PM

This revision is now accepted and ready to land.May 10 2022, 1:06 PM

Closed by commit rG6e7a585348d5: bitstring: fix ff_area() when start!=0 (authored by dougm). · Explain WhyMay 10 2022, 5:00 PM

This revision was automatically updated to reflect the committed changes.

dougm added a commit: rG6e7a585348d5: bitstring: fix ff_area() when start!=0.

Herald added a subscriber: imp. · View Herald TranscriptMay 10 2022, 5:00 PM

dougm added a commit: rGbb75580e0370: bitstring: fix ff_area() when start!=0.Jul 11 2022, 6:09 AM

Revision Contents
Changeset List

Path

Size

sys/

bitstring.h

2 lines

Diff 105801

View Options

bitstring: fix match-at-start bugClosedPublicActions