[PATCH 1/2] libmm score and stubs

Gedare Bloom gedare at rtems.org
Wed Jul 24 19:20:24 UTC 2013


The approach we have taken so far with libmm is that it is "always on"
even if it is not supported by the BSP/CPU. In the cases that it is
not supported, the functions are nops that may have minimal effect on
runtime if users try to use the libmm. (Currently there is no API for
using libmm.)

On Wed, Jul 24, 2013 at 2:48 PM, Chris Johns <chrisj at rtems.org> wrote:
> Claus, Ric wrote:
>> There is already so much output generated during building that it slows a
>> developer down to go through the output to determine what things must be
>> paid attention to, what things can be ignored and what things are simply
>> informational.  My vote is for a solution that doesn't add to that burden.
>> Most of the output is just distracting, but then on the other hand one does
>> want to get some sense that the build is making progress.  It would be
>> really nice, I think, to get just one over-printed line that shows what
>> directory is being worked on and that newlines are generated only by error,
>> warning, and perhaps informational messages.
>> Perhaps a possibility is to introduce --enable-mm on the configure line
>> and then to print the compile-time warning only when there is a disagreement
>> between the flag and the ability, i.e., --enable-mm is present, but mm
>> support isn't, and --enable-mm is not present, but mm support is.  In the
>> "normal" case (--enable-mm is present and mm is supported, and --enable-mm
>> is not present and mm support isn't) the build system would stay quiet.
> I do not like new configure options because it becomes just another untested
> path in the build system. We have so many now that are not tested and that
> it is a concern.
> Chris

More information about the devel mailing list