From: Andrew Cagney <ac131313@cygnus.com>
To: "Theodore A. Roth" <troth@verinet.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb support for Atmel AVR
Date: Fri, 08 Feb 2002 12:49:00 -0000 [thread overview]
Message-ID: <3C6439E6.8070007@cygnus.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0202081030470.23246-100000@bozoland.mynet>
> :)Finally, there is -Werror. Your target should be buildable with:
> :) --target=<your-target> --enable-gdb-build-warnings=,-Werror
> :)and then start. You need to select your host carefully. Pragmatics:
> :)anyone making changes across GDB should try rebuilding and running all
> :)targets. -Werror makes this much easier.
>
> That should be easy to do.
>
> :)
> :)The one thing you'll notice isn't on the check list is test results. On
> :)that count, far as I'm conceerned, as soon as your target is showing
> :)reasonable signs of life it is ready for acceptance.
>
> Some people are already using it for real work so I think it's got a heart
> beat already. ;)
Sounds good.
> I'm especially interested in someone reviewing the changes I had to make
> outside of avr-tdep.c and config/avr/*. These changes may affect other
> targets. I've tried really hard to keep those changes to a minimum though.
(Mutter something about needing to avoid contamination until the
assignment is in place :-/ :-)
I'll personally avoid looking at the changes however it looks like
you're getting the feedback you need.
good luck!
Andrew
next prev parent reply other threads:[~2002-02-08 20:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 11:53 Theodore A. Roth
2002-02-08 8:33 ` Andrew Cagney
2002-02-08 9:53 ` Theodore A. Roth
2002-02-08 11:20 ` Daniel Jacobowitz
2002-02-08 14:19 ` Theodore A. Roth
2002-02-08 14:29 ` Daniel Jacobowitz
2002-02-08 14:56 ` Andrew Cagney
2002-02-08 15:10 ` Theodore A. Roth
2002-02-10 10:27 ` Theodore A. Roth
2002-02-10 10:38 ` Andrew Cagney
2002-02-08 12:49 ` Andrew Cagney [this message]
2002-02-11 14:18 ` Theodore A. Roth
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=3C6439E6.8070007@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=troth@verinet.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