Skip to content

Avoid writing even sanity.txt if FROZEN_CACHE is enabled #13316

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.

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

Merged
merged 1 commit into from
Jan 29, 2021

Conversation

sbc100
Copy link
Collaborator

@sbc100 sbc100 commented Jan 25, 2021

These improvements to the FROZE_CACHE setting allow for a
pre-populated read-only cache. In thie senario the cache
is cannot ever be locked, and that we don't even write
the sanity file.

Users can still forece a sanity check with emcc --check
but no sanity file will ever be written.

Copy link
Member

@kripken kripken left a comment

Choose a reason for hiding this comment

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

Nice!

@sbc100 sbc100 force-pushed the improve_froze_cache branch 4 times, most recently from 211b7f7 to cde0c76 Compare January 26, 2021 05:08
sbc100 added a commit that referenced this pull request Jan 26, 2021
This is in service of improving support for FROZEN_CACHE and is needed
as part of #13316.

The logic here mirrors the lock in cache.get() where we first attempt to
verify the contents of the cache without holding the lock and early out
in the common case the what we want is already here.
sbc100 added a commit that referenced this pull request Jan 26, 2021
This is in service of improving support for FROZEN_CACHE and is needed
as part of #13316.

The logic here mirrors the lock in cache.get() where we first attempt to
verify the contents of the cache without holding the lock and early out
in the common case the what we want is already here.
sbc100 added a commit that referenced this pull request Jan 26, 2021
…13321)

This is in service of improving support for FROZEN_CACHE and is needed
as part of #13316.

The logic here mirrors the lock in cache.get() where we first attempt to
verify the contents of the cache without holding the lock and early out
in the common case the what we want is already here.
@sbc100 sbc100 force-pushed the improve_froze_cache branch 3 times, most recently from 85990b9 to f795dfe Compare January 28, 2021 23:04
@sbc100 sbc100 force-pushed the improve_froze_cache branch from f795dfe to 372386b Compare January 29, 2021 00:21
@sbc100 sbc100 changed the base branch from master to avoid_cache_lock January 29, 2021 00:21
@sbc100 sbc100 force-pushed the improve_froze_cache branch 2 times, most recently from ad94a68 to 4c1b540 Compare January 29, 2021 03:15
Base automatically changed from avoid_cache_lock to master January 29, 2021 16:04
These improvements to the FROZE_CACHE setting allow for a
pre-populated read-only cache.  In thie senario the cache
is cannot ever be locked, and that we don't even write
the sanity file.

Users can still forece a sanity check with `emcc --check`
but no sanity file will ever be written.
@sbc100 sbc100 force-pushed the improve_froze_cache branch from 4c1b540 to 0f46f59 Compare January 29, 2021 16:05
@sbc100 sbc100 merged commit e74e0af into master Jan 29, 2021
@sbc100 sbc100 deleted the improve_froze_cache branch January 29, 2021 16:06
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.

2 participants