From: Chen Gang <gang.chen@asianux.com>
To: linux-sh@vger.kernel.org
Subject: [Suggestion] sh: about the warnings for "overflow in branch to syscall_exit_work"
Date: Thu, 01 Aug 2013 02:52:36 +0000 [thread overview]
Message-ID: <51F9CD74.1000404@asianux.com> (raw)
Hello Maintainers:
I find some warnings for sh, can they cause real world issue ?
It is also found by Geert Uytterhoeven, please ref:
http://lkml.indiana.edu/hypermail/linux/kernel/1301.3/02181.html
The related warnings (with allmodconfig):
AS arch/sh/kernel/cpu/sh2/entry.o
arch/sh/kernel/cpu/sh2/../../entry-common.S: Assembler messages:
arch/sh/kernel/cpu/sh2/../../entry-common.S:89: Warning: overflow in branch to __restore_all; converted into longer instruction sequence
arch/sh/kernel/cpu/sh2/../../entry-common.S:210: Warning: overflow in branch to syscall_call; converted into longer instruction sequence
arch/sh/kernel/cpu/sh2/../../entry-common.S:349: Warning: overflow in branch to syscall_trace_entry; converted into longer instruction sequence
arch/sh/kernel/cpu/sh2/../../entry-common.S:351: Warning: overflow in branch to syscall_trace_entry; converted into longer instruction sequence
arch/sh/kernel/cpu/sh2/../../entry-common.S:375: Warning: overflow in branch to syscall_exit_work; converted into longer instruction sequence
arch/sh/kernel/cpu/sh2/../../entry-common.S:378: Warning: overflow in branch to syscall_exit_work; converted into longer instruction sequence
For me, I guess it can cause real world issue (and it seems a "long
time existence" issue)
Welcome any members suggestions or completions.
Thanks.
--
Chen Gang.
reply other threads:[~2013-08-01 2:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=51F9CD74.1000404@asianux.com \
--to=gang.chen@asianux.com \
--cc=linux-sh@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.