From: Chen Gang <gang.chen.5i5j@gmail.com>
To: cmetcalf@tilera.com
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arch: tile: kernel: kgdb.c: Use memcpy() instead of pointer copy one by one
Date: Wed, 12 Nov 2014 10:11:31 +0800 [thread overview]
Message-ID: <5462C1D3.3010504@gmail.com> (raw)
In-Reply-To: <5454DD70.6060004@gmail.com>
Hello maintainer:
Please help check this patch, when you have time (sorry for my original
typo for your email address, so maybe you did not notice about the
original mail).
Thanks.
On 11/1/14 21:17, Chen Gang wrote:
> Not only memcpy() is faster than pointer copy, but also let code more
> clearer and simple, which can avoid compiling warning (the original
> implementation copy registers by exceeding member array border).
>
> The related warning (with allmodconfig under tile):
>
> CC arch/tile/kernel/kgdb.o
> arch/tile/kernel/kgdb.c: In function 'sleeping_thread_to_gdb_regs':
> arch/tile/kernel/kgdb.c:140:31: warning: iteration 53u invokes undefined behavior [-Waggressive-loop-optimizations]
> *(ptr++) = thread_regs->regs[reg];
> ^
> arch/tile/kernel/kgdb.c:139:2: note: containing loop
> for (reg = 0; reg <= TREG_LAST_GPR; reg++)
> ^
>
> Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>
> ---
> arch/tile/kernel/kgdb.c | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/arch/tile/kernel/kgdb.c b/arch/tile/kernel/kgdb.c
> index 4cd8838..ff5335a 100644
> --- a/arch/tile/kernel/kgdb.c
> +++ b/arch/tile/kernel/kgdb.c
> @@ -125,9 +125,7 @@ int dbg_set_reg(int regno, void *mem, struct pt_regs *regs)
> void
> sleeping_thread_to_gdb_regs(unsigned long *gdb_regs, struct task_struct *task)
> {
> - int reg;
> struct pt_regs *thread_regs;
> - unsigned long *ptr = gdb_regs;
>
> if (task == NULL)
> return;
> @@ -136,9 +134,7 @@ sleeping_thread_to_gdb_regs(unsigned long *gdb_regs, struct task_struct *task)
> memset(gdb_regs, 0, NUMREGBYTES);
>
> thread_regs = task_pt_regs(task);
> - for (reg = 0; reg <= TREG_LAST_GPR; reg++)
> - *(ptr++) = thread_regs->regs[reg];
> -
> + memcpy(gdb_regs, thread_regs, TREG_LAST_GPR * sizeof(unsigned long));
> gdb_regs[TILEGX_PC_REGNUM] = thread_regs->pc;
> gdb_regs[TILEGX_FAULTNUM_REGNUM] = thread_regs->faultnum;
> }
>
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
next prev parent reply other threads:[~2014-11-12 2:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-01 13:17 [PATCH] arch: tile: kernel: kgdb.c: Use memcpy() instead of pointer copy one by one Chen Gang
2014-11-12 2:11 ` Chen Gang [this message]
2014-11-12 13:27 ` Jeff Epler
2014-11-12 15:43 ` Chen Gang
2014-11-12 19:29 ` Jeff Epler
2014-11-12 20:15 ` Chris Metcalf
-- strict thread matches above, loose matches on Subject: below --
2014-11-13 0:08 Chen Gang
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=5462C1D3.3010504@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=cmetcalf@tilera.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.