Opened 2 years ago

Last modified 23 months ago

#20872 new enhancement

option to build non-standard code paths on x86

Reported by: weasel Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.8.10
Severity: Normal Keywords: triaged-out-20170116, testing, portability, unit-tests, intro
Cc: Actual Points:
Parent ID: Points: parent
Reviewer: Sponsor:

Description

#20868 is a case where one code path gets almost always built on x86, and another is used everywhere else.

This means that we don't notice build or test failures on that other code path.

Should we have options to use the alternate path even on x86, so we can build and run tests on our CI using fast machines?

Child Tickets

Change History (6)

comment:1 Changed 2 years ago by nickm

I think we should do this whenever we can. Unfortunately, that does mean looking through all the ifdefs in our code to see which are platform-specific optimizations. Maybe we should break this into child tickets...

comment:2 Changed 2 years ago by nickm

Points: parent

comment:3 Changed 2 years ago by nickm

Type: defectenhancement

batch modify: I think these are "enhancement", though I could be wrong about some.

comment:4 Changed 2 years ago by nickm

Keywords: triaged-out-20160116 added
Milestone: Tor: 0.3.0.x-finalTor: unspecified

comment:5 Changed 2 years ago by nickm

Keywords: triaged-out-20170116 added; triaged-out-20160116 removed

comment:6 Changed 23 months ago by nickm

Keywords: testing portability unit-tests intro added
Note: See TracTickets for help on using tickets.