From: Tristan Gingold <gingold@adacore.com>
To: Richard Henderson <rth@redhat.com>
Cc: "Petr Hluzín" <petr.hluzin@gmail.com>,
"Anitha Boyapati" <anitha.boyapati@gmail.com>,
binutils@sourceware.org, gdb@sourceware.org,
"GCC Patches" <gcc-patches@gcc.gnu.org>,
chertykov@gmail.com, aesok@post.ru, eric.weddington@atmel.com
Subject: Re: [avr] gas support for cfi info
Date: Thu, 17 Feb 2011 16:16:00 -0000 [thread overview]
Message-ID: <C0B81DCB-327B-49AA-9842-6F83D7E90836@adacore.com> (raw)
In-Reply-To: <4D5D48E5.30404@redhat.com>
On Feb 17, 2011, at 5:12 PM, Richard Henderson wrote:
> On 02/16/2011 02:47 PM, Petr Hluzín wrote:
>> What should I look for when testing?
>
> Run the gdb testsuite with dwarf-3 enabled. Either by editing the
> default in the compiler, or by some dejagnu argument that compiles
> the tests with -gdwarf-3.
Note that gdb includes an avr simulator (if this could simplify your testing).
next prev parent reply other threads:[~2011-02-17 16:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTim6hyXysiV-025BDgNJ84qaqTnkRdHi+e7bF2gx@mail.gmail.com>
[not found] ` <AANLkTi=Rnu-wb2W8FejN=XQHmHuTq7rZovKuDdO-QLwi@mail.gmail.com>
[not found] ` <AANLkTimOXF1V__SSFs1gtqJh5nc183EdeHm5NoeU6YXs@mail.gmail.com>
[not found] ` <AANLkTike2osnZS=sUphuN_=oFQLCDUs54uuGCWL6cLVQ@mail.gmail.com>
2011-02-15 17:41 ` Testing Call frame information in .debug_frame section Richard Henderson
2011-02-15 18:02 ` Richard Henderson
2011-02-15 22:13 ` Petr Hluzín
2011-02-16 16:51 ` Richard Henderson
2011-02-15 18:09 ` Anitha Boyapati
2011-02-15 18:48 ` Richard Henderson
2011-02-15 19:15 ` Anitha Boyapati
2011-02-15 19:03 ` [avr] gas support for cfi info Richard Henderson
2011-02-15 22:45 ` Petr Hluzín
2011-02-16 17:59 ` Richard Henderson
2011-02-16 22:49 ` Petr Hluzín
2011-02-17 16:12 ` Richard Henderson
2011-02-17 16:16 ` Tristan Gingold [this message]
2011-02-17 15:35 ` Anitha Boyapati
2011-02-17 16:05 ` Richard Henderson
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=C0B81DCB-327B-49AA-9842-6F83D7E90836@adacore.com \
--to=gingold@adacore.com \
--cc=aesok@post.ru \
--cc=anitha.boyapati@gmail.com \
--cc=binutils@sourceware.org \
--cc=chertykov@gmail.com \
--cc=eric.weddington@atmel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=petr.hluzin@gmail.com \
--cc=rth@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).