public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "arnold-j at t-online dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/24863] New __attribute__((alias("target"))) requirement break aliasing assembler functions
Date: Mon, 14 Nov 2005 22:55:00 -0000	[thread overview]
Message-ID: <20051114225536.7002.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24863-11714@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from arnold-j at t-online dot de  2005-11-14 22:55 -------
I am indeed hiding a lot of code, but hopefully in order to pinpoint the issue.
This code snippet is taken from the rockbox project http://www.rockbox.org/ ,
precisely from 
http://www.rockbox.org/viewcvs.cgi/firmware/system.c?annotate=1.73
Check lines 652-1019.

This is part of the exception handling on the SH1 target CPU. All exceptions
are
handled in one C handler function, UIE(). However, the only way to get the
exception number on SH1 is checking the called handler address, so all
exceptions that aren't handled by other code are handled by tiny assembler
snippets which just fetch their callee address and pass it to UIE(), which then
checks the address it was called from.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24863


  parent reply	other threads:[~2005-11-14 22:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 21:47 [Bug c/24863] New: " arnold-j at t-online dot de
2005-11-14 21:49 ` [Bug c/24863] " arnold-j at t-online dot de
2005-11-14 22:20 ` pinskia at gcc dot gnu dot org
2005-11-14 22:55 ` arnold-j at t-online dot de [this message]
2005-11-14 23:02 ` pinskia at gcc dot gnu dot org
2005-11-14 23:16 ` arnold-j at t-online dot de
2006-04-26 21:12 ` pinskia at gcc dot gnu dot org
2009-03-30  1:19 ` jsm28 at gcc dot gnu dot org

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=20051114225536.7002.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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 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).