All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: gerg@snapgear.com
Cc: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org,
	Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH 1/3] m68k: consistently call ret_from_exception in entry code
Date: Tue, 15 May 2012 10:18:08 +0200	[thread overview]
Message-ID: <m21uml6enz.fsf@igel.home> (raw)
In-Reply-To: <1337064949-966-2-git-send-email-gerg@snapgear.com> (gerg@snapgear.com's message of "Tue, 15 May 2012 16:55:47 +1000")

<gerg@snapgear.com> writes:

> The ret_from_excption code is referenced by its function name, or by a label
> set at the start of its code. Modify all uses to consistently just use the
> function name "ret_from_exception".

This will cause all branches to use the long variant, because
ret_from_exception is a global symbol (and thus overridable in the ELF
model).  The point of the additional local label is to allow the
assembler to relax the branches.

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."

  reply	other threads:[~2012-05-15  8:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15  6:55 [PATCH 00/03] m68k: clean up and merge MMU and non-MMU versions of entry.S gerg
2012-05-15  6:55 ` [PATCH 1/3] m68k: consistently call ret_from_exception in entry code gerg
2012-05-15  8:18   ` Andreas Schwab [this message]
2012-05-16  3:38     ` Greg Ungerer
2012-05-15  6:55 ` [PATCH 2/3] m68k: use jbsr to call functions instead of bsrl gerg
2012-05-15  6:55 ` [PATCH 3/3] m68k: merge the MMU and non-MMU versions of the entry.S code gerg

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=m21uml6enz.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=gerg@snapgear.com \
    --cc=gerg@uclinux.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=uclinux-dev@uclinux.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.