[SERVER-49323] Evaluate feasibility and impact of enabling -fno-semantic-interposition Created: 07/Jul/20 Updated: 27/Oct/23 Resolved: 27/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Server Development Platform
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Participants: | |||||
| Description |
|
The -fno-semantic-interposition flag significantly improves startup time for dynamically linked binaries by disabling support for symbol interposition (e.g. LD_PRELOAD. We should evaluate whether we think the loss of LD_PRELOAD functionality is justified by the performance gains. If we decide against doing so, we should consider building with -fsemantic-interposition, since clang defaults to -fno-semantic-interposition despite it generating binaries that are technically not in alignment with the ELF standard. |
| Comments |
| Comment by Githook User [ 23/Mar/21 ] |
|
Author: {'name': 'Andrew Morrow', 'email': 'acm@mongodb.com', 'username': 'acmorrow'}Message: |