Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: cgf@cygnus.com (Chris Faylor)
To: gdb@sourceware.cygnus.com
Subject: Re: Another Issue for 5.0
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <88k71j$jt0$1@cronkite.cygnus.com> (raw)
In-Reply-To: <200002181809.NAA06156@texas.cygnus.com>

In article < 200002181809.NAA06156@texas.cygnus.com >,
David Taylor  <taylor@cygnus.com> wrote:
>    Date: Thu, 17 Feb 2000 08:26:39 -0800 (PST)
>    From: Daniel Berlin <dan@cgsoftware.com>
>
>    IMHO, the overload resolution for DWARF2/STABS/all non-hp platforms should
>    really be fixed for 5.0.
>    I have patches to do this (in fact, i'm about to send another jumbo patch
>    to gdb-patches with it all combined so i don't have to keep emailing it to
>    people :P), with no regressions, well, actually, that's not true.
>    Some overload resolution things that were xfail before in the testsuite
>    now pass.
>    Sorry about that. I'll try to make sure i keep the broken things broken in
>    the future. :P
>
>    But, anyway, i get about 5-10 emails a week asking for those patches.
>    Even on HP using aCC, where overload resolution works, you get benefits
>    because i added support for references in overloads, and fixed a problem
>    where the compares against function names were whitespace sensitive where
>    they shouldn't have been (so operator [] would be considered the same
>    function as operator[] when we were hunting down overloads).
>
>    Maybe i'm biased, but anyone working on C++ programs would love it.
>
>    I'm starting to work on other C++ language support related things, if
>    anyone has any specific requests, let me know.
>
>Is there a copyright assignment on file?
>
>I'd love to look over the patch.

Nick Duffek has already looked over the patch and verified that it works exactly
as Dan has suggested.  He should be able to apply the patch as soon as the
assignment clears.

I think that this falls into Jim Blandy's maintainership area so it will be up
to him to say yea or nay, though.

cgf
-- 
cgf@cygnus.com                        Cygnus Solutions, a Red Hat company
http://sourcware.cygnus.com/          http://www.redhat.com/
From rearnsha@arm.com Sat Apr 01 00:00:00 2000
From: Richard Earnshaw <rearnsha@arm.com>
To: Scott Bambrough <scottb@netwinder.org>
Cc: rearnsha@arm.com
Subject: Re: Breakpoint problem when running on gdb-4.18 arm/thumb simulator target
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-id: <200001131530.PAA27948@cam-mail2.cambridge.arm.com>
References: <387DE3A6.A2BCAB58@netwinder.org>
X-SW-Source: 2000-q1/msg00029.html
Content-length: 222

> 
> ARM CPU's currently have no hardware support for breakpoints that I know of.

ARM cores with 'I' in the product name (eg ARM7TDMI, ARM9TDMI) have 
hardware breakpoints.  These are part of the ICE hardware.

Richard



      reply	other threads:[~2000-04-01  0:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-01  0:00 David Taylor
2000-04-01  0:00 ` Chris Faylor [this message]

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='88k71j$jt0$1@cronkite.cygnus.com' \
    --to=cgf@cygnus.com \
    --cc=gdb@sourceware.cygnus.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