Mail Archives: djgpp-workers/2012/12/04/14:44:14
> Date: Tue, 04 Dec 2012 19:56:11 +0100
> From: Juan Manuel Guerrero <juan DOT guerrero AT gmx DOT de>
> CC: Ozkan Sezer <sezeroz AT gmail DOT com>
>
> Am 04.12.2012 18:45, schrieb Ozkan Sezer:
> > On 12/4/12, Ozkan Sezer <sezeroz AT gmail DOT com> wrote:
> >> Hi:
> >>
> >> As far as I can see unassemble_proper() sets its len param, however
> >> src/debug/fsdb/fullscr.c r1.12 comments out the call to avoid set-but-
> >> unused warnings but 'len' is used two lines below. So, unless I am
> >> missing something, the following is needed.
> >>
> > Slightly updated patch below. (BTW, the whole thing can actually use
> > some constification: things like char* str="string"; are everywhere..)
> >
> >
> You are right. I missed something when I tried to fix set-but-unused
> warnings. Your patch is OK.
Why is it better to do this:
inst = unassemble_proper (j, &len);
(void) inst; /* set, but not used. */
instead of this:
unassemble_proper (j, &len);
Is it "verboten" to discard the return value of a function, for some
reason? Some exciting new "feature" of the latest GCC versions or
something?
- Raw text -