On 7/22/2014 1:05 PM, Daniel Gutson wrote:
Hi,
we are working in a very RAM constrained board, and noticed that
some symbols could be moved to ROM by declaring them const.
I have a slight idea about creating a consts-candidate detector tool
KICS! (Keep It Const, St.! :) ), and wanted to
Hi
I have committed a few patches this week for multiple targets and
wanted to pass along the news for those who care.
+ binutils-gdb:
- or1k*-*-rtems* builds but requires a pending patch to disable
gdb until OpenRISC folks submit their gdb port
+ newlib-cvs:
- adjtime() prototype
Thanks Joel,
I will let you know once I address all your suggestions.
Daniel.
On Wed, Jul 23, 2014 at 10:28 AM, Joel Sherrill
joel.sherr...@oarcorp.com wrote:
On 7/22/2014 1:05 PM, Daniel Gutson wrote:
Hi,
we are working in a very RAM constrained board, and noticed that
some symbols
Hi
I should point out that I am NOT trying to particularly improve the
way we adjust time. I am only
(1) making the code use timestamps not ticks
(2) moving the adjust code to the SCORE
The use of critical sections is exactly as it was before.
The preferable way to adjust TOD is in small
On 22/07/2014 1:47 am, Joel Sherrill wrote:
On July 21, 2014 10:44:15 AM CDT, Gedare Bloom ged...@rtems.org wrote:
Either account for it in workspace sizing or use malloc.
On principle, I guess any dynamic allocated memory that isn't mandatory
to get RTEMS to work should come from malloc.
