From: Peter Bergner <bergner@linux.ibm.com>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>, binutils@sourceware.org
Cc: Claudiu Zissulescu <claziss@synopsys.com>,
Geoff Keating <geoffk@geoffk.org>, Alan Modra <amodra@gmail.com>,
Peter Bergner <bergner@vnet.ibm.com>
Subject: Re: [PATCH] PPC + ARC: Fix calloc() call
Date: Tue, 21 Nov 2023 09:19:57 -0600 [thread overview]
Message-ID: <cbb0afab-0c02-4d91-ade1-381d29242b3f@linux.ibm.com> (raw)
In-Reply-To: <20231121134012.GA21972@lug-owl.de>
On 11/21/23 7:40 AM, Jan-Benedict Glaw wrote:
> Recently, -Walloc-size warnings started to kick in. Fix these two
> calloc() calls to match the intended usage pattern.
>
> opcodes/ChangeLog:
>
> * arc-dis.c (init_arc_disasm_info): Fix calloc() call.
> * ppc-dis.c (powerpc_init_dialect): Ditto.
Looks obvious to me, but to remove any doubt, the ppc change is ok.
Thanks!
Peter
prev parent reply other threads:[~2023-11-21 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 13:40 Jan-Benedict Glaw
2023-11-21 13:49 ` Claudiu Zissulescu
2023-11-21 15:19 ` Peter Bergner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cbb0afab-0c02-4d91-ade1-381d29242b3f@linux.ibm.com \
--to=bergner@linux.ibm.com \
--cc=amodra@gmail.com \
--cc=bergner@vnet.ibm.com \
--cc=binutils@sourceware.org \
--cc=claziss@synopsys.com \
--cc=geoffk@geoffk.org \
--cc=jbglaw@lug-owl.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).