| commit | aacf4563878cac2afbbdc9818d810d2a3b075c6a | |
| author | Thomas Monjalon <thomas@monjalon.net> | |
| Tue, 27 Apr 2010 13:27:09 +0000 (27 15:27 +0200) | ||
| committer | Blue Swirl <blauwirbel@gmail.com> | |
| Tue, 27 Apr 2010 18:56:11 +0000 (27 18:56 +0000) | ||
| tree | bd2d07ed6a59fc9c84d99ad479180b489aa56fe6 | treesnapshot (tar.gz zip) |
| parent | 14a6063a91083c9cbe1bc502ee58fc7ca146bc1a | commitdiff |
microblaze: fix custom fprintf
Using GCC-4.2.4-1ubuntu4, there is a warning:
microblaze-dis.c:792: warning: unused variable 'fprintf'
Indeed, fprintf() is shadowed by a custom redefinition but is not used because
of FORTIFY_SOURCE option which replace calls to fprintf() by fprintf_chk().
So, fprintf refers to the libc implementation instead of the qemu one.
It's a bug.
It is fixed by renaming the variable to something different of "fprintf".
It prevents from hazardous shadowing.
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
Using GCC-4.2.4-1ubuntu4, there is a warning:
microblaze-dis.c:792: warning: unused variable 'fprintf'
Indeed, fprintf() is shadowed by a custom redefinition but is not used because
of FORTIFY_SOURCE option which replace calls to fprintf() by fprintf_chk().
So, fprintf refers to the libc implementation instead of the qemu one.
It's a bug.
It is fixed by renaming the variable to something different of "fprintf".
It prevents from hazardous shadowing.
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
| microblaze-dis.c | diffblobblamehistory |