Skip to content

Switch default backend from 'fastcomp' to 'upstream' #373

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 2 commits into from
Oct 21, 2019

Conversation

sbc100
Copy link
Collaborator

@sbc100 sbc100 commented Oct 16, 2019

When users as for 'latest' or just '1.39.0' we now default to the upstream llvm backend.

For versions before 1.39.0 we continue to default to fastcomp.

Fixes: emscripten-core/emscripten#5488

@kripken
Copy link
Member

kripken commented Oct 18, 2019

Before we land this we should have docs probably, but I'm not sure where?

@kripken
Copy link
Member

kripken commented Oct 18, 2019

Actually, maybe we could have the emsdk say something? Like show a message, "the default backend has changed" on first run after the change?

@sbc100
Copy link
Collaborator Author

sbc100 commented Oct 18, 2019

Good idea. Added a bit notice.

@sbc100 sbc100 force-pushed the upstream_by_default branch from 5efc809 to aabbf8d Compare October 18, 2019 21:03
@kripken
Copy link
Member

kripken commented Oct 18, 2019

Looks good, thanks!

@kripken
Copy link
Member

kripken commented Oct 18, 2019

In offline discussion we had the idea to maybe not always default to upstream, but just from 1.39.0 and onwards. The idea being that say at a version from last year, upstream's support was not that great yet, so it would be bad. Only at 1.39.0 are we confident the new backend is good enough for general use.

Let's discuss more and decide next week.

@sbc100 sbc100 force-pushed the upstream_by_default branch from aabbf8d to 588d8bb Compare October 21, 2019 19:44
@sbc100
Copy link
Collaborator Author

sbc100 commented Oct 21, 2019

Updated so that we now only default for upstream for 'latest' and for 1.39.0 and above.

@sbc100 sbc100 changed the title Switch 'latest' from 'latest-fastcomp' to 'latest-upstream' Switch default backend from 'fastcomp' to 'latest' Oct 21, 2019
@sbc100 sbc100 force-pushed the upstream_by_default branch from 588d8bb to 12a6db9 Compare October 21, 2019 19:47
@sbc100 sbc100 changed the title Switch default backend from 'fastcomp' to 'latest' Switch default backend from 'fastcomp' to 'upstream' Oct 21, 2019
When users as for 'latest' or just '1.39.0' we now default to the
upstream llvm backend.

For versions before 1.39.0 we continue to default to fastcomp.

Fixes: emscripten-core/emscripten#5488
@sbc100 sbc100 force-pushed the upstream_by_default branch from 12a6db9 to 25835aa Compare October 21, 2019 19:50
if arg in ('latest', 'sdk-latest', 'latest-64bit', 'sdk-latest-64bit', 'latest-fastcomp', 'latest-releases-fastcomp'):
if arg in ('latest', 'sdk-latest', 'latest-64bit', 'sdk-latest-64bit'):
# This is effectly the default SDK
report_upstream_by_default()
Copy link
Member

Choose a reason for hiding this comment

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

I think we can report this only if the version is high enough? Can maybe share code with the existing check later down.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

The version check make sense below, but here we know that we want to unconditionally select upstream right? We never want latest to point to fastcomp ever again, do we? And if we do we would revert this code.

@sbc100 sbc100 merged commit ae5044e into master Oct 21, 2019
@sbc100 sbc100 deleted the upstream_by_default branch October 21, 2019 21:23
@aheejin
Copy link
Member

aheejin commented Oct 21, 2019

🎉🎉🎉

vargaz pushed a commit to vargaz/emsdk that referenced this pull request Nov 22, 2023
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.

Switching to use upstream LLVM backend by default
3 participants