comment end correction
The proposed solution to improve the presentation of the code in port.c
was not a good result in initial tests I did worked, but I was using in
a function and in this case macros are then researched the impact of
using functions inline, and so I thought acclaim, besides the fact that
the result be the same when properly parameterized.
http://www.parashift.com/c++-faq/inline-vs-macros.html
Parameters for create a menu to Arduino Mega + DuinOS
Fixed type parameter to the function defnition
Once the function is always_inline it need not be noreturn not naked.
Auxiliary function defined as the Task naked and always_inline The

Once the function is always_inline it need not be noreturn not naked.

function used in Infinite Loop task is just an object to facilitate the
use of the macro that facilitates the access to Task structure for use
in the FreeRTOS, so this function must be inserted into the code so
which are optimum and avoiding headers function.
The names of the subsections as ". lowtext" does not need a reference.
Text so its reference should be made only as ". lowtext" and not as ".
text.lowtext"

Moreover expand use of the ". lowtext" for macros and
portTASK_FUNCTION_PROTO portTASK_FUNCTION File "portmacro.h"
The names of the subsections as ". lowtext" does not need a reference.
Text so its reference should be made only as ". lowtext" and not as ".
text.lowtext"

Moreover expand use of the ". lowtext" for macros and
portTASK_FUNCTION_PROTO portTASK_FUNCTION File "portmacro.h"
Adjusted the file to create the distribution package with information
regarding the version of FreeRTOS / DuinOS