[SERVER-19338] Evaluate feasibility and impact of not disabling strict aliasing Created: 08/Jul/15  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: Improvement 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:
Depends
depends on SERVER-19362 Clean up strict aliasing violations i... Backlog
Related
related to SERVER-19340 Vendored wiredtiger rand.c fails to c... Closed
Assigned Teams:
Server Development Platform
Backwards Compatibility: Fully Compatible
Sprint: Platform 6 07/17/15
Participants:

 Description   

We currently disable the compilers alias based optimziations by building with -fno-strict-aliasing, due to a small number of aliasing violations.

The majority of these aliasing violations are in the mmap subsystem.

We should switch the default to build with type based alias analysis enabled, and only disable it for subsystems which require it.



 Comments   
Comment by Githook User [ 23/Mar/21 ]

Author:

{'name': 'Andrew Morrow', 'email': 'acm@mongodb.com', 'username': 'acmorrow'}

Message: SERVER-19338 Add an experiment for allowing type-based alias analysis
Branch: master
https://github.com/mongodb/mongo/commit/691cb1577300d5df5118cd2b77c02b99a833d174

Comment by Mathias Stearn [ 29/Jul/15 ]

We need to fix BufReader before we enable strict aliasing. Should be as simple as changing the (T*)_pos lines to call memcpy.

Generated at Thu Feb 08 03:50:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.