FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [July 2006 Threads] FreeRTOS 4.0.4, GCC: InliningPosted by Thomas K.-H. Nittel on July 19, 2006 Hi,
when the module FreeRTOSV4.0.4\FreeRTOS\Source\portable\GCC\ARM7_AT91SAM7S\portISR.c is compiled with arm-elf-gcc 4.1.0 the following warning appears ... Source/portable/GCC/ARM7_AT91SAM7S/portISR.c -o portISR.o ../../Source/FreeRTOS_4.0.4/Source/portable/GCC/ARM7_AT91SAM7S/portISR.c: In function 'vPreemptiveTick': ../../Source/FreeRTOS_4.0.4/Source/include/task.h:832: warning: inlining failed in call to 'vTaskIncrementTick': function body not available ../../Source/FreeRTOS_4.0.4/Source/portable/GCC/ARM7_AT91SAM7S/portISR.c:144: warning: called from here
Obviously inlining doesn't work with GCC.
gcc.pdf, page 216 recommends to put the function definition in a header file with the keywords inline and extern. If 'vTaskIncrementTick' is put as 'extern inline void vTaskIncrementTick( void )' in 'task.h' inlining will work with GCC, too. Of cause some declarations of variables, functions and macros of 'tasks.c' are addtionally necessary in 'task.h'.
I found the above mentioned document at http://www.gnuarm.org/. Its title is 'Using the GNU Compiler Collection' for GCC 3.3.2 and dated from 20. December 2002. A newer version doesn't seem to be available.
The compiler command which I used is arm-elf-gcc -c -I../../Source/Demo -I../../Source/FreeRTOS_4.0.4/Source/include -I../../Source/FreeRTOS_4.0.4/Source/portable/GCC/ARM7_AT91SAM7S -I../../Source/Utilities -Wall -Wextra -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wno-strict-aliasing -Winline -D THUMB_INTERWORK -D SAM7_GCC -mthumb-interwork -mcpu=arm7tdmi -MMD -finline-limit=1000 -Os ../../Source/FreeRTOS_4.0.4/Source/portable/GCC/ARM7_AT91SAM7S/portISR.c -o portISR.o
Best regards
Thomas
RE: FreeRTOS 4.0.4, GCC: InliningPosted by Nobody/Anonymous on July 19, 2006 The inline is a legacy thing. Most portmacro.h files include the lilne
#define inline
to remove it from the code and prevent any warnings.
RE: FreeRTOS 4.0.4, GCC: InliningPosted by Thomas K.-H. Nittel on July 19, 2006 Hi, of cause warnings can be avoided this way. But I want my code to be inlined so that the function call overhead is spared. For an example see my posting 'RE: FreeRTOS 4.0.4, AT91SAM7X256, Timertick 2006-07-19 14:05' Regards Thomas
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|