Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[NFC] Use initial-stack-allocations for more data structures #110544

Merged
merged 3 commits into from
Sep 30, 2024
Merged

[NFC] Use initial-stack-allocations for more data structures #110544

merged 3 commits into from
Sep 30, 2024

Commits on Sep 30, 2024

  1. [NFC] Use inital-stack-allocations for more data structures 

    This replaces some of the most frequent offenders of using a DenseMap that
cause a malloc, where the typical element-count is small enough to fit in
an initial stack allocation.

Most of these are fairly obvious, one to highlight is the collectOffset
method of GEP instructions: if there's a GEP, of course it's going to have
at least one offset, but every time we've called collectOffset we end up
calling malloc as well for the DenseMap in the MapVector.
    @jmorse
    jmorse committed Sep 30, 2024
    Configuration menu
    Copy the full SHA
    c161cf1 View commit details
    Browse the repository at this point in the history

  2. [NFC] Use initial-stack-allocations for some nested containers 

    I've done a little more testing on these as, being nested, there's more
initialization to do when they're created. The net effect is positive on
the compile-time-tracker.
    @jmorse
    jmorse committed Sep 30, 2024
    Configuration menu
    Copy the full SHA
    b8ec33b View commit details
    Browse the repository at this point in the history

  3. clang-format

    @jmorse
    jmorse committed Sep 30, 2024
    Configuration menu
    Copy the full SHA
    7fa7d88 View commit details
    Browse the repository at this point in the history