|
Re: "function called through a non-compatible type" when activating diags_ENTRY [message #422 is a reply to message #417] |
Wed, 26 November 2008 17:19 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Dave Russo![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=d-russo%40ti.com) Messages: 172 Registered: July 2009 |
Senior Member |
|
|
Clemens Fuchs wrote:
> Hi,
>
> when activating diagnosis support like described in the user's guide
> (Defaults.common$.diags_ENTRY = Diags.RUNTIME_ON;), I get following
> error for all function calls when compiling:
>
> package/cfg/Test_x86GW.c:18914: warning: function called through a
> non-compatible type
> package/cfg/Test_x86GW.c:18914: note: if this code is reached, the
> program will abort
>
> I use mingw32-gcc-3.4.5, did anybody experience similar problems?
>
> thanks,
> Clemens
>
I can't reproduce the problem. Goggling the warning from gcc suggests
that the compiler has detected a call through a function pointer whose
type signature does not match the arguments being passed.
Log diagnostics does call an underlying "Logger" function via a function
pointer, so it seems likely this is the source of the warning. But
since I don't get this warning, I wonder if you are passing additional
"strict" options to the compiler?
The Test_x86GW.c file is a generated file and it's possible that we need
to add an appropriate cast around arguments being passed to the logger.
Finally, if you can send me the Test_x86GW.c file (d-russo at ti.com),
it would help us diagnose the problem.
|
|
|
|
Powered by
FUDForum. Page generated in 0.03746 seconds