Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>,
	Mike Frysinger <vapier@gentoo.org>
Subject: Re: [PATCH v3] sim: bfin: new port
Date: Tue, 22 Feb 2011 10:08:00 -0000	[thread overview]
Message-ID: <201102221004.19755.pedro@codesourcery.com> (raw)
In-Reply-To: <20110221095436.GD2600@adacore.com>

On Monday 21 February 2011 09:54:36, Joel Brobecker wrote:
> Please, sending compressed files makes it harder to look at the file.
> I think you were right to do it for a file that's 4MB, but in that case,
> using  something a little more usual like gz, zip or bzip2 would have
> made things easier... I had to install the xzutil on my laptop and it
> wasn't without its little scary moment...
> 
> > changes since v3:
> >  - stubbed all the bootroms

Did you send the correct patch?  I still see a bunch of:

> diff --git a/sim/bfin/bfroms/bf50x-0.0.h b/sim/bfin/bfroms/bf50x-0.0.h
> new file mode 100644
> index 0000000..8d88c73
> --- /dev/null
> +++ b/sim/bfin/bfroms/bf50x-0.0.h
> @@ -0,0 +1,515 @@
> +/* DO NOT EDIT: Autogenerated.  */
> +static const char bfrom_bf50x_0_0[] = {

> (i'll follow up)

Thanks, I do hope this is sorted out.

> I have no other comment. I think you know what you're doing in
> the simulator area, so I'm inclined to trust your judgment on
> the rest of the code (if you could just remember for future
> contributions that comments are important). 

> If Pedro has no further comments, the meat of the patch is OK with me.

One:

> +#! /bin/sh
> +# Guess values for system-dependent variables and create Makefiles.
> +# Generated by GNU Autoconf 2.68.

The whole tree is at Autoconf 2.64.  Please use that version.
Preferably, a pristine FSF version, as distros tend to patch
autoconf, and that causes churn on the output.

I'll reply to another email, but other than that I have further
comments.  Thanks.

-- 
Pedro Alves


  parent reply	other threads:[~2011-02-22 10:04 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-16  1:41 [PATCH] " Mike Frysinger
2010-12-31 23:12 ` [PATCH v2] " Mike Frysinger
2011-02-14 20:18   ` [PATCH v3] " Mike Frysinger
2011-02-14 20:49     ` Pedro Alves
2011-02-14 21:12       ` Mike Frysinger
2011-02-14 21:55         ` Pedro Alves
2011-02-14 22:11           ` Mike Frysinger
2011-02-14 22:23             ` Mike Frysinger
2011-02-15 16:25             ` Pedro Alves
2011-02-16  1:34               ` Mike Frysinger
2011-02-16  5:34                 ` Joel Brobecker
2011-02-20  7:24     ` Mike Frysinger
2011-02-21 10:13       ` Joel Brobecker
2011-02-21 18:27         ` Mike Frysinger
2011-02-22  8:28           ` Joel Brobecker
2011-02-22 17:58             ` Mike Frysinger
2011-02-22 10:50           ` Pedro Alves
2011-02-22 18:07             ` Mike Frysinger
2011-02-22 10:08         ` Pedro Alves [this message]
2011-02-22 17:57           ` Mike Frysinger
2011-02-22 18:25             ` Pedro Alves
2011-02-22 20:54               ` Mike Frysinger
2011-02-22 20:29       ` [PATCH v5] " Mike Frysinger
2011-03-01  5:16         ` Mike Frysinger
2011-03-01 10:11         ` Joel Brobecker
2011-03-01 21:19         ` Pedro Alves
2011-03-01 23:42           ` Mike Frysinger
2011-03-02  1:13             ` Pedro Alves
2011-03-02  2:23               ` Mike Frysinger
2011-03-02  9:30                 ` Pedro Alves
2011-03-02 21:46                   ` Mike Frysinger
2011-03-02 23:32                     ` Pedro Alves
2011-03-02 23:32                     ` Pedro Alves
2011-03-03 21:40         ` [PATCH v6] " Mike Frysinger
2011-03-04 10:19           ` Pedro Alves
2011-03-04 21:12             ` Mike Frysinger

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=201102221004.19755.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=vapier@gentoo.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