PARSE clocks.

Amar Takhar verm at
Mon Nov 30 19:16:52 UTC 2015

On 2015-11-30 14:13 -0500, Eric S. Raymond wrote:
> Cute, but I'm not sure the space savings are worth the additional
> complexity cost in the build system. The whole point of the parse
> driver architecture is to share code among the subtypes; thus, the
> memory overhead of any N-1 is pretty small.

I've already added the code to do this for PPS clocks.

> I just ran the numbers with size(1) and in the best case (building
> with the single smallest driver) you condition out about 28K of text
> space - that's 3% of the 787K build size with all refclocks, 7% of
> the build size with none.

I'm trying to remove the additional symbols so coverage reports are more useful 
on an individual basis.

> This is going to be potentially useful only on very constrained SBCs.
> It's highly doubtful such systems will ever talk to a parse clock;
> every Stratum 1 SBC design I've ever seen uses a GPS.
> How much code does this add to the build system?

Very little as it uses existing interfaces.


More information about the devel mailing list