Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Eager <eager@eagercon.com>
To: tromey@redhat.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 17:12:00 -0000	[thread overview]
Message-ID: <4AD757FE.6060704@eagercon.com> (raw)
In-Reply-To: <m3iqegzk0s.fsf@fleche.redhat.com>

Tom Tromey wrote:
>>>>>> "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.

Not easy.  It would require coordination with users.  Lots.
Perhaps a test to see if code was generated by a particular version
of gcc or something equally ugly.

Even if gcc was fixed to accept reg+8 for the return address,
there would need to be a change to the MicroBlaze-specific
INCOMING_RETURN_ADDR_RTX for it to take any effect.  (There's
a warning note about this in gcc, which I might make more emphatic.)
So this is not going to happen by accident.

I'm just as happy to leave this problem unfixed.  Gcc generates an
incorrect CIE entry, which is philosophically not a good thing.
But fixing this causes far more problems than it solves.

> 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.

Oops.  The "Changes in GDB 7.0" was added after I updated the file
and I didn't notice it.  I'll move the entry.


-- 
Michael Eager	 eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077


  parent reply	other threads:[~2009-10-15 17:12 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
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 [this message]
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=4AD757FE.6060704@eagercon.com \
    --to=eager@eagercon.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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