Skip to content

Conversation

@artemii235
Copy link
Contributor

Fixes #521

Copy link
Contributor

@ordian ordian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

I don't know which allocator iOS uses by default and whether it's possible to use jemalloc there.

It's fine to merge this if you tested it locally, however it would be hard for us to support iOS w/o proper CI setup for it.

@ordian ordian requested a review from cheme February 8, 2021 10:21
@ordian
Copy link
Contributor

ordian commented Feb 8, 2021

(asking @cheme for a review because they implemented #93)

@artemii235
Copy link
Contributor Author

I guess I have to fix the formatting, I will push it asap.

Copy link
Collaborator

@cheme cheme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, the cfg default to estimate heap size when we do not use jemalloc (so for mac and ios only option is jemalloc now, not sure if other allocator could make sense for those targets).

@niklasad1 niklasad1 merged commit 3ad905d into paritytech:master Feb 8, 2021
ordian added a commit that referenced this pull request Feb 16, 2021
* master:
  build(deps): update sysinfo requirement from 0.15.3 to 0.16.3 (#526)
  CI: add a workaround for build issue (#527)
  parity-util-mem: use ios compilation conditions same as macos. (#522)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[mem-util] reaching unreachable!(...) on iOS.

4 participants