public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Vasanth <geekvasanth@gmail.com>
To: gcc@gcc.gnu.org
Subject: dw2 frame unwinder - unaligned access
Date: Tue, 19 Jul 2005 05:34:00 -0000	[thread overview]
Message-ID: <89acfbb605071822335c0e58a4@mail.gmail.com> (raw)

Hi,

With reference to the following info in the EH handling newbie document,

http://gcc.gnu.org/ml/gcc/2002-07/msg00391.html


<snip>
The exception handing via dwarf2 debugging information requires
several things to work:
.........
-Unaligned accesses to read dwarf2 information
</snip>


What is the recommended way to do DW2 frame unwinding based exception
handling for targets that do not support unaligned accesses in
hardware? I did see the documentation about UNALIGNED_INT_ASM_OP, but
not sure if that is meant to generate a directive to the assembler to
produce an aligned int (the name indicates otherwise). Also, I see
UNALIGNED_INT_ASM_OP being used only in the VMS debugging source file.
So I am unsure how it relates to DW2 based frame unwinding.

thanks for any help,

regards,
Vasanth

             reply	other threads:[~2005-07-19  5:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19  5:34 Vasanth [this message]
2005-07-19  6:04 ` Ian Lance Taylor

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=89acfbb605071822335c0e58a4@mail.gmail.com \
    --to=geekvasanth@gmail.com \
    --cc=gcc@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).