Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Marcel Moolenaar <marcel@cup.hp.com>
To: Marcel Moolenaar <marcel@xcllnt.net>
Cc: gdb-patches@sources.redhat.com
Subject: Followup: [PATCH] New port: ia64-*-freebsd
Date: Wed, 06 Jul 2005 17:24:00 -0000	[thread overview]
Message-ID: <6f09c8828a60008599e36c906ef6d98c@cup.hp.com> (raw)
In-Reply-To: <20050705195104.GA1584@ns1.xcllnt.net>

On Jul 5, 2005, at 12:51 PM, Marcel Moolenaar wrote:

> There's a small regression on ia64-*-linux that I'm currently
> analyzing and which may relate to process problems. Please let
> me know if you see it too if you're able to test the patches.

The 2 regressions for the libunwind case were indeed process
problems. I failed to see the compile failure when not compiling
against libunwind and the failures there were all bogus. I
updated the patch at http://www.xcllnt.net/~marcel/gdb and now
have real results: 3 failures less when not using libunwind.

So: all is well -- better in fact.

Just make sure to use the patch at the URL.

FYI,

-- 
  Marcel Moolenaar                                marcel@cup.hp.com


  reply	other threads:[~2005-07-06 17:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-05 19:52 Marcel Moolenaar
2005-07-06 17:24 ` Marcel Moolenaar [this message]
2005-07-15  0:01 ` Daniel Jacobowitz
2005-07-15  2:08   ` Marcel Moolenaar
2005-07-15  2:16     ` Daniel Jacobowitz
2005-07-15 18:20       ` Marcel Moolenaar
2005-07-24 21:26         ` Daniel Jacobowitz
2005-07-25 17:32           ` Marcel Moolenaar
2005-07-25 17:36             ` Daniel Jacobowitz
2005-07-25 17:58               ` Marcel Moolenaar
2005-07-25 19:34                 ` Mark Kettenis
2005-07-25 20:41                   ` Marcel Moolenaar

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=6f09c8828a60008599e36c906ef6d98c@cup.hp.com \
    --to=marcel@cup.hp.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=marcel@xcllnt.net \
    /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