Skip to content

[wasm] Do not use link flags for bitcode compilation #108846

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

Closed
wants to merge 6 commits into from

Conversation

radekdoulik
Copy link
Member

@radekdoulik radekdoulik commented Oct 14, 2024

Manual backport of (#101397) and (#101538)

Customer Impact

  • Customer reported
  • Found internally

Regression

  • Yes
  • No

Risk

Low. Fixes warning during bc files compilation.

Description

This avoids errors like:

/root/helix/work/correlation/build/wasm-shared/WasmApp.Common.targets(832,5): error : emcc: warning: linker setting ignored during compilation: 'EXPORT_ES6' [-Wunused-command-line-argument] [/root/helix/work/workitem/e/publish/ProxyProjectForAOTOnHelix.proj]
/root/helix/work/correlation/build/wasm-shared/WasmApp.Common.targets(832,5): error : emcc: warning: linker setting ignored during compilation: 'EXPORT_EXCEPTION_HANDLING_HELPERS' [-Wunused-command-line-argument] [/root/helix/work/workitem/e/publish/ProxyProjectForAOTOnHelix.proj]

This should helps with known build error #104827 where the warning can hide another errors

Backport of (dotnet#101397)

This avoids errors like:

    /root/helix/work/correlation/build/wasm-shared/WasmApp.Common.targets(832,5): error : emcc: warning: linker setting ignored during compilation: 'EXPORT_ES6' [-Wunused-command-line-argument] [/root/helix/work/workitem/e/publish/ProxyProjectForAOTOnHelix.proj]
    /root/helix/work/correlation/build/wasm-shared/WasmApp.Common.targets(832,5): error : emcc: warning: linker setting ignored during compilation: 'EXPORT_EXCEPTION_HANDLING_HELPERS' [-Wunused-command-line-argument] [/root/helix/work/workitem/e/publish/ProxyProjectForAOTOnHelix.proj]

This should helps with known build error dotnet#104827
where the warning can hide another errors
@carlossanlop
Copy link
Contributor

Friendly reminder that today 10/14 is Code Complete for the November Release. If this fix is intended to be included in that release, please make sure it's merged before 4pm PT. Otherwise, it will have to wait until next month.

@radekdoulik
Copy link
Member Author

@lewing what do you think about merging this to release/8.0? it would allow us to cast some light to issues potentially invisible due to known build error issue

@carlossanlop
Copy link
Contributor

@lewing @radekdoulik Friendly reminder that today is Code Complete for the February 2025 Release. Please get a Tactics approval and merge it before 4pm PT, otherwise it would have to wait until next month.

@carlossanlop carlossanlop added the Servicing-approved Approved for servicing release label Jan 30, 2025
@carlossanlop
Copy link
Contributor

This is infra only, so I marked it servicing-approved.

There are new failures though. Are they related?

@jeffschwMSFT
Copy link
Member

@radekdoulik please take a look at the PR failures. we can merge when ready

@carlossanlop
Copy link
Contributor

@radekdoulik @lewing Today is code complete for the April Release. If you want this fix included in this release, please merge it before 4pm PT.

@carlossanlop
Copy link
Contributor

carlossanlop commented Apr 2, 2025

@radekdoulik @lewing Friendly reminder that code complete is on April 14th for the May Release. If you'd like to get this change included in that release, please get a Tactics approval and merge this PR before that date.

@lewing lewing closed this Apr 11, 2025
@akoeplinger
Copy link
Member

We decided not to take this after all given where we are in the 8.0 cycle.

@akoeplinger akoeplinger removed the Servicing-approved Approved for servicing release label Apr 11, 2025
@github-actions github-actions bot locked and limited conversation to collaborators May 12, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants