Upstream software project

sediment

A function reordering tool set

About sediment

A function reordering tool set

This project links 2 native package records across 2 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

sediment repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Fedora 43: 1 package records; Fedora 44: 1 package records. Catalog coverage diagram, not an application screenshot.sediment: recorded package coverageFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
sediment
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
fedora-43, fedora-44
License expression
GPL-3.0-or-later
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

The sediment tool set allows reordering of the functions in compiled programs built with RPM to reduce the frequency of TLB misses and decrease the number of pages in the resident set. Sediment generates call graphs from program execution and converts the call graphs into link order information to improve code locality.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. Package sediment

    43 (Fedora 43) (Unspecified): A function reordering tool set

    0.9.4-3.fc43: noarch

    Source: sediment

Fedora 44

  1. Package sediment

    44 (Fedora 44) (Unspecified): A function reordering tool set

    0.9.4-4.fc44: noarch

    Source: sediment

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.