Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Michael Eager <eager@eagercon.com>
Cc: "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>,
	        Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCH] Support for Xilinx MicroBlaze
Date: Thu, 15 Oct 2009 16:44:00 -0000	[thread overview]
Message-ID: <m3iqegzk0s.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4AD74E86.1020500@eagercon.com> (Michael Eager's message of "Thu, 	15 Oct 2009 09:32:06 -0700")

>>>>> "Michael" == Michael Eager <eager@eagercon.com> writes:

Michael> When (if) this is fixed in gcc there will need to coordinate
Michael> this with a corresponding fix in gdb.

How would this be done?
Users might be using an old gcc or a new one.

Michael> diff -urNp --exclude '*.swp' --exclude DEV-PHASE --exclude .svn --exclude CVS gdb/gdb/NEWS mb-gdb/gdb/NEWS
Michael> --- gdb/gdb/NEWS	2009-10-14 11:15:51.000000000 -0700
Michael> +++ mb-gdb/gdb/NEWS	2009-10-14 19:15:57.000000000 -0700
Michael> @@ -484,6 +484,11 @@ Lattice Mico32                  lm32-*
Michael>  x86 DICOS			i[34567]86-*-dicos*
Michael>  x86_64 DICOS		        x86_64-*-dicos*
Michael>  S+core 3			score-*-*
Michael> +Xilinx MicroBlaze		microblaze-*-*
Michael> +
Michael> +* New Simulators
Michael> +
Michael> +Xilinx MicroBlaze		microblaze
 
I think this changes the "7.0" section, not the "since 7.0" section.

Tom


  reply	other threads:[~2009-10-15 16:44 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-15 16:32 Michael Eager
2009-10-15 16:44 ` Tom Tromey [this message]
2009-10-15 16:47   ` Joel Brobecker
2009-10-15 18:00     ` Tom Tromey
2009-10-15 18:04       ` Tom Tromey
2009-10-15 18:31         ` Joel Brobecker
2009-10-16 12:53         ` Daniel Jacobowitz
2009-10-16 16:14           ` Michael Eager
2009-10-15 17:12   ` Michael Eager
2009-10-15 17:18     ` Joel Brobecker
2009-10-15 18:06       ` Michael Eager
2009-10-15 16:46 ` Joel Brobecker
2009-10-15 17:14   ` Michael Eager
2009-10-15 19:31   ` Michael Eager
2009-10-16  7:53     ` Build-failure from " Pierre Muller
2009-10-16 15:56       ` Michael Eager
2009-10-16 16:11         ` Pierre Muller
2009-10-16 16:35         ` Joel Brobecker
2009-10-16 23:21           ` Michael Eager
  -- strict thread matches above, loose matches on Subject: below --
2009-10-06  1:35 Michael Eager
2009-10-06  7:14 ` Eli Zaretskii
2009-10-14  1:47 ` Joel Brobecker
2009-10-14 17:49   ` Michael Eager
2009-10-14 17:56     ` Daniel Jacobowitz
2009-10-14 18:01       ` Michael Eager

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=m3iqegzk0s.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=eager@eagercon.com \
    --cc=gdb-patches@sourceware.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