Quality RTOS & Embedded Software

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


Loading

warnings on IAR compiler for AVR

Posted by Nobody/Anonymous on December 20, 2005
I compiled the RTOS under IAR AVR 4.12 and got 20 warnings,I fear to use it in my project because these warning may make bugs in design.

Is is possible author of FreeRTOS modifies source codes for each compiler ,and give them in seperate folder?,so we do not have warning,and codes is 100% compatible with that compiler.

Can Author do this for sensitive IAR AVR compiler?(as a special case)

BTW: FreeRTOS is great and user notes can improve it extensively.

Thanks in advance


RE: warnings on IAR compiler for AVR

Posted by Nobody/Anonymous on December 20, 2005
Out of all the supported ports the AVR/IAR port is the only one I know that ships with compiler warnings. Did you see the section "Compiler Warnings" on the http://www.freertos.org/AVR_IAR.html page?

These are all non serious warnings but annoying. They can be switched off in the project file, but then you will also not get the warnings in your application code where you may want to see them.

RE: warnings on IAR compiler for AVR

Posted by Nobody/Anonymous on December 21, 2005
I want to remove warnings by modifying freertos source code,But I need help to do it,I do not know how to fix the type cast and other warnings.

I am disappointed.

List of warnings for IAR AVR (ver4.12a)

Warning[Pe191]: type qualifier is meaningless on cast type G:\freertos\Demo\Common\Minimal\PollQ.c 100
Warning[Pe191]: type qualifier is meaningless on cast type G:\freertos\Demo\Common\Minimal\PollQ.c 101
Warning[Pe191]: type qualifier is meaningless on cast type G:\freertos\Demo\Common\Minimal\comtest.c 145
Warning[Pe191]: type qualifier is meaningless on cast type G:\freertos\Demo\Common\Minimal\comtest.c 146
Warning[Pe191]: type qualifier is meaningless on cast type G:\freertos\Demo\Common\Minimal\flash.c 92
Warning[Pe191]: type qualifier is meaningless on cast type G:\freertos\Demo\Common\Minimal\integer.c 103
Warning[Ta006]: Interrupt function has no assigned vector. G:\freertos\Demo\AVR_ATMega323_IAR\serial\serial.c 164
Warning[Ta006]: Interrupt function has no assigned vector. G:\freertos\Demo\AVR_ATMega323_IAR\serial\serial.c 180
Warning[Ta006]: Interrupt function has no assigned vector. G:\freertos\Demo\AVR_ATMega323_IAR\serial\serial.c 164
Warning[Ta006]: Interrupt function has no assigned vector. G:\freertos\Demo\AVR_ATMega323_IAR\serial\serial.c 180
Warning[Pe191]: type qualifier is meaningless on cast type G:\freertos\Source\tasks.c 478
Warning[Pe191]: type qualifier is meaningless on cast type G:\freertos\Source\tasks.c 494
Warning[Pe191]: type qualifier is meaningless on cast type G:\freertos\Source\tasks.c 900
Warning[Pa082]: undefined behavior: the order of volatile accesses is undefined in this statement G:\freertos\Source\tasks.c 1260
Warning[Pa082]: undefined behavior: the order of volatile accesses is undefined in this statement G:\freertos\Source\tasks.c 1260
Warning[Pa082]: undefined behavior: the order of volatile accesses is undefined in this statement G:\freertos\Source\tasks.c 1260
Warning[w6]: Type conflict for external/entry "uxQueueMessagesWaiting", in module PollQ against external/entry in
Warning[w6]: Type conflict for external/entry "xQueueCreate", in module PollQ against external/entry in module queue;
Warning[w6]: Type conflict for external/entry "xQueueReceive", in module PollQ against external/entry in module queue;
Warning[w6]: Type conflict for external/entry "xQueueReceiveFromISR", in module serial against external/entry in
Warning[w6]: Type conflict for external/entry "xQueueSend", in module PollQ against external/entry in module queue;
Warning[w6]: Type conflict for external/entry "xQueueSendFromISR", in module serial against external/entry in module

Thanks in advance

RE: warnings on IAR compiler for AVR

Posted by Richard on December 21, 2005
As said previously, the warnings are benign. Modifying the source code will cause warning to be produced by other compilers. This is the only port for which warnings are produced currently. You may be better off disabling the warnings.

> Warning[Pe191]: type qualifier is meaningless on cast type
> G:\freertos\Demo\Common\Minimal\PollQ.c 100

This is not part of the source, but the demo. If you want to fix this by modifying the code then remove the qualifier in the cast prior to the QConsNB parameter (line 100 of PollQ). Likewise for the other type qualifier is meaningless warnings. The line numbers are given.

> Warning[Pa082]: undefined behavior: the order of volatile accesses is undefined
> in this statement G:\freertos\Source\tasks.c 1260

These warning are in the listGET_OWNER_OF_NEXT_ENTRY() macro. You can remove the volatile cast from within the macro if you wish.


> Warning[w6]: Type conflict for external/entry "uxQueueMessagesWaiting", in module
> PollQ against external/entry in

These warnings are generated because of a deliberate data hiding policy. You would have to change the location the queue and tcb data structures are defined to remove the warning. This is not a good idea as you would also remove the data hiding which is not desirable. In this case I really recommend just disabling the warning.


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


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

Latest News

NXP tweet showing LPC5500 (ARMv8-M Cortex-M33) running FreeRTOS.

Meet Richard Barry and learn about running FreeRTOS on RISC-V at FOSDEM 2019

Version 10.1.1 of the FreeRTOS kernel is available for immediate download. MIT licensed.

View a recording of the "OTA Update Security and Reliability" webinar, presented by TI and AWS.


Careers

FreeRTOS and other embedded software careers at AWS.



FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

Espressif ESP32

IAR Partner

Microchip Premier RTOS Partner

RTOS partner of NXP for all NXP ARM microcontrollers

Renesas

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

Xilinx Microblaze and Zynq partner