From: Andreas Schwab <schwab@linux-m68k.org>
To: Greg Ungerer <gerg@uclinux.org>
Cc: linux-m68k@vger.kernel.org
Subject: Re: [PATCH] m68k: use conventional function parameters for do_sigreturn
Date: Mon, 01 Feb 2016 19:39:33 +0100 [thread overview]
Message-ID: <8737tcxoka.fsf@linux-m68k.org> (raw)
In-Reply-To: <1453183018-11722-1-git-send-email-gerg@uclinux.org> (Greg Ungerer's message of "Tue, 19 Jan 2016 15:56:58 +1000")
Greg Ungerer <gerg@uclinux.org> writes:
> The motivation for this change is a problem with non-MMU targets that
> have broken signal return paths on newer versions of gcc. It appears as
> though aliasing of the regs and switch stack pointers, caused by their
> construction from pointers derived from the dummy long function parameter,
> is resulting in the gcc optimizer removing what it thinks is useless
> updates to the regs fields.
I wonder why gcc is doing that. The kernel is explicitly built without
strict aliasing, so this looks like something to investigate.
> -asmlinkage int do_sigreturn(unsigned long __unused)
> +asmlinkage int do_sigreturn(struct pt_regs *regs, struct switch_stack *sw)
Does it work to use this signature:
asmlinkage int do_sigreturn(struct switch_stack sw, struct pt_regs regs)
without changing the caller?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2016-02-01 18:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 5:56 [PATCH] m68k: use conventional function parameters for do_sigreturn Greg Ungerer
2016-02-01 4:33 ` Greg Ungerer
2016-02-01 18:39 ` Andreas Schwab [this message]
2016-02-01 23:59 ` Greg Ungerer
2016-02-02 19:25 ` Andreas Schwab
2016-02-03 4:14 ` Greg Ungerer
2016-02-08 23:31 ` Andreas Schwab
2016-02-09 0:21 ` Greg Ungerer
2016-02-09 9:48 ` Andreas Schwab
2016-02-09 13:05 ` Greg Ungerer
2016-02-09 13:17 ` Andreas Schwab
2016-02-09 14:01 ` Philippe De Muyter
2016-02-09 14:36 ` Andreas Schwab
2016-02-09 15:26 ` Philippe De Muyter
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=8737tcxoka.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=linux-m68k@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.