This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Change list for RealView Compilation Tools available?

The Release_Notes.htm file in the ARM compiler gives an overview of changes made between MDK-ARM versions, but is there somewhere I can find out exactly what bug fixes/improvements have been made to the RealView compiler itself?

The behaviour of the compiler has changed between MDK-ARM versions 4.03a and 4.10, which is not surprising since the compiler is a new version in this release. However, this has resulted in some code developed on 4.10 (which compiles with no warnings) to fail with an error during compilation on 4.03a. Specifically I have a function which accepts a pointer to void, and am passing a function pointer to it.

I can make the code compile on both versions with some casting, but I would like to be able to see if this issue is known and if there are other issues we should be wary of.

Parents

0 Gael Depreeuw over 15 years ago in reply to HansBernhard Broeker

Thanks for the answer. I had seen the information in your quote, but probably should have mentioned that I do indeed always cast back.

The way I use is it as follows.

Basically, I need to initialize a table/database that contains functions to be called. For this purpose I had created a union that holds function pointers:

typedef union {
        void    void*;
        void    (*main) (<arguments>);
        int8u   (*table)(<arguments>);
        int8u   (*text) (<arguments>);
} layout_fptrs_u;

I then have a struct for my table/database

typedef struct
{
        const int8s *name; // name of the element
        layout_fptrs_u func;
} layout_elements_t;

And the actual table itself:

layout_elements_t g_main_elements_table[] =
{
        { "Text",                     sys_process_text },
        { "Table",                    sys_process_table },
        { "Title",                    sys_process_title },
};

The table is initialized statically, so where at first i did not have the void* member in the union and the compiler complained because the function were not necessarily of the member named 'main'. (Initializing unions always initializes using the first member-type)

So I added the void* as the first member, which worked. Now, I changed it to:

typedef union {
        void    (*do_not_use)(void);
        void    (*main) (<arguments>);
        int8u   (*table)(<arguments>);
        int8u   (*text) (<arguments>);
} layout_fptrs_u;

typedef void (*void_fptr_t)(void);

and the table:

layout_elements_t g_main_elements_table[] =
{
        // Standard Elements
        { "Text",                     (void_fptr_t)sys_process_text },
        { "Table",                    (void_fptr_t)sys_process_table },
        { "Title",                    (void_fptr_t)sys_process_title },
};

I could have casted the fptr of the 'main' member as well though.

All I really use it for it to initialize my table. Nothing else uses the do_not_use member of the unio.

Reply

0 Gael Depreeuw over 15 years ago in reply to HansBernhard Broeker

Thanks for the answer. I had seen the information in your quote, but probably should have mentioned that I do indeed always cast back.

The way I use is it as follows.

Basically, I need to initialize a table/database that contains functions to be called. For this purpose I had created a union that holds function pointers:

typedef union {
        void    void*;
        void    (*main) (<arguments>);
        int8u   (*table)(<arguments>);
        int8u   (*text) (<arguments>);
} layout_fptrs_u;

I then have a struct for my table/database

typedef struct
{
        const int8s *name; // name of the element
        layout_fptrs_u func;
} layout_elements_t;

And the actual table itself:

layout_elements_t g_main_elements_table[] =
{
        { "Text",                     sys_process_text },
        { "Table",                    sys_process_table },
        { "Title",                    sys_process_title },
};

So I added the void* as the first member, which worked. Now, I changed it to:

typedef union {
        void    (*do_not_use)(void);
        void    (*main) (<arguments>);
        int8u   (*table)(<arguments>);
        int8u   (*text) (<arguments>);
} layout_fptrs_u;

typedef void (*void_fptr_t)(void);

and the table:

layout_elements_t g_main_elements_table[] =
{
        // Standard Elements
        { "Text",                     (void_fptr_t)sys_process_text },
        { "Table",                    (void_fptr_t)sys_process_table },
        { "Title",                    (void_fptr_t)sys_process_title },
};

I could have casted the fptr of the 'main' member as well though.

All I really use it for it to initialize my table. Nothing else uses the do_not_use member of the unio.

Children

0 HansBernhard Broeker over 15 years ago in reply to Gael Depreeuw

(Initializing unions always initializes using the first member-type)

As of C99, not necessarily. Among the things they added on top of C90 were named designators and non-default union initialization. So instead of this:

layout_elements_t g_main_elements_table[] =
{
        // Standard Elements
        { "Text",                     (void_fptr_t)sys_process_text },
        { "Table",                    (void_fptr_t)sys_process_table },
        { "Title",                    (void_fptr_t)sys_process_title },
};

you could now do

layout_elements_t g_main_elements_table[] =
{
        // Standard Elements
        { "Text",                     {.text = sys_process_text} },
        { "Table",                    {.table = sys_process_table } },
        { "Title",                    {.text = sys_process_title } },
};