From: Andrew Cagney <ac131313@redhat.com>
To: Richard.Earnshaw@arm.com
Cc: Daniel Jacobowitz <drow@mvista.com>,
Richard.Earnshaw@buzzard.freeserve.co.uk,
gdb-patches@sources.redhat.com
Subject: Re: [RFA] Repost ARM frame patches
Date: Fri, 05 Sep 2003 20:43:00 -0000 [thread overview]
Message-ID: <3F58F557.4090801@redhat.com> (raw)
In-Reply-To: <200309050950.h859oNV23553@pc960.cambridge.arm.com>
>> i.e. GCC emits _empty_ dwarf unwind information for thumb functions,
>> rather than none at all. That's unlikely to work. We'd need to modify
>> the dwarf2 unwinder to ignore empty FDEs.
>>
>> I'll check in the non-dwarf parts now, and then we can figure out what
>> to do about that.
>
>
> Though of course a trivial leaf function *will* have an empty FDE.
> Consider
>
> int func(void) { return 0;}
>
> Which compiles to
>
> mov r0, #0
> bx lr
>
> I would have thought that wouldn't need any frame unwind information. So
> we would have a problem distinguishing trivial cases from "not generated"
> cases.
FYI, the dwarf2 spec (draft 7) doesn't specify the disposition of
unspecified registers that result from an empty or under populated CFI
info - such registers are truly undefined. GCC is pushing the bounds of
well defined behavior in emitting such info.
Andrew
next prev parent reply other threads:[~2003-09-05 20:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 1:50 Daniel Jacobowitz
2003-09-02 22:56 ` Richard Earnshaw
2003-09-03 20:41 ` Daniel Jacobowitz
2003-09-05 9:50 ` Richard Earnshaw
2003-09-05 20:43 ` Andrew Cagney [this message]
2004-02-08 4:11 ` Daniel Jacobowitz
2004-02-09 12:12 ` Richard Earnshaw
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=3F58F557.4090801@redhat.com \
--to=ac131313@redhat.com \
--cc=Richard.Earnshaw@arm.com \
--cc=Richard.Earnshaw@buzzard.freeserve.co.uk \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
/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