Mantis Bug Tracker

View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000938FirmwareDecoderspublic2015-06-14 03:562015-06-14 03:56
ReporterFred 
Assigned ToFred 
PrioritynormalSeverityminorReproducibilityalways
StatusassignedResolutionopen 
PlatformOSOS Version
Product Version0.2.0-SNAPSHOT 
Target Version0.2.0Fixed in Version 
Summary0000938: Timestamp variable used badly in all decoders
DescriptionAll decoders put this into a variable first, when they could put it straight into the timestamp lower half. Some have that variable static, some local/automatic.

The timestamp variable is used by all decoders, always. It should be statically or globally allocated in the interface files, and the value should be placed directly into the appropriate part of it rather than into a short term holding variable. Being automatic/inline means it's allocated as part of the stack and therefore takes up a little more time to run than if it was static/global.
TagsNo tags attached.
FirmwareVersion6dd79320ca05d0a764cba2f6f17c241b6779fec9
Issue TypeImprovement
Risk of Breakagemedium
Attached Files

- Relationships
child of 0000111assignedFred Finalise Decoder Interface (for now at least) 

-  Notes
There are no notes attached to this issue.


Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker