Quality RTOS & Embedded Software

 Real time embedded FreeRTOS RSS feed 
Quick Start Supported MCUs PDF Books Trace Tools Ecosystem TCP & FAT




Loading

Couple of questions for next release

Posted by JC on July 28, 2007
Richard,

For the next release, will you be able to suppress the type-punning warnings that arm-elf-gcc 4.1.2 throws? The GCC flag set being used is: -Wall -Wextra -Wshadow -Wpointer-arith -Wbad-function-cast -Wcast-align -Wsign-compare -Waggregate-return -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wunused

Will structures declarations and such be visible outside of FreeRTOS? I'm not interested in the instantiated data, but it would be nice to be able to do a sizeof (xheap) and others for sizing purposes. I definitely believe the actual FreeRTOS data should be private, the way you're doing it now.

Will there be a call to determine if the scheduler is running? It would be nice to know if the scheduler has been not yet started, running (xSchedulerRunning), and suspended (uxSchedulerSuspended).

Do you have a set date for the release? I'd like to release an update of the demo package, but not before you release the latest FreeRTOS.

Thanks!
--jc

RE: Couple of questions for next release

Posted by Richard on July 28, 2007
> For the next release, will you be able to suppress the
> type-punning warnings
> that arm-elf-gcc 4.1.2 throws? The GCC flag set being used
> is: -Wall -Wextra
> -Wshadow -Wpointer-arith -Wbad-function-cast -Wcast-align
> -Wsign-compare
> -Waggregate-return -Wstrict-prototypes -Wmissing-prototypes
> -Wmissing-declarations
> -Wunused


I only get the warning with optimisation strangely. I presumed it was because of the strict aliasing option, but you don't have that in your list here.


>
> Will structures declarations and such be visible outside of
> FreeRTOS? I'm
> not interested in the instantiated data, but it would be nice
> to be able to
> do a sizeof (xheap) and others for sizing purposes. I
> definitely believe the
> actual FreeRTOS data should be private, the way you're doing it now.
>
> Will there be a call to determine if the scheduler is
> running? It would be
> nice to know if the scheduler has been not yet started,
> running (xSchedulerRunning),
> and suspended (uxSchedulerSuspended).


This can be on the list, but I'm not sure if it will get done this time around. Can you please add these to the feature request tracker (in SourceForge) so they stay visible.


>
> Do you have a set date for the release? I'd like to
> release an update of
> the demo package, but not before you release the latest FreeRTOS.
>

Well, it was planned for this Monday or Tuesday, but with the discussions that have been going on here over the last day it may be delayed a little. I don't want to delay it as missing this deadline will put it back probably about three weeks, so I will do my best to get it out on time.

Regards.


RE: Couple of questions for next release

Posted by JC on July 28, 2007
My bad. The Makefile has warnings and optimizations on separate lines. Optimizations are -O3 -fomit-frame-pointer.

I will add these items to the feature request tracker.

Thanks!
--jc


[ Back to the top ]    [ About FreeRTOS ]    [ Sitemap ]    [ ]




Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.

Latest News

FreeRTOS kernel V10 is available for immediate download. Now MIT licensed.


FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

IAR Partner

Microchip Premier RTOS Partner

RTOS partner of NXP for all NXP ARM microcontrollers

STMicro RTOS partner supporting ARM7, ARM Cortex-M3, ARM Cortex-M4 and ARM Cortex-M0

Texas Instruments MCU Developer Network RTOS partner for ARM and MSP430 microcontrollers

OpenRTOS and SafeRTOS