Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: cgd@broadcom.com
Cc: Richard Sandiford <rsandifo@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [rfa/mips] Second go at vr5500 hilo hazard fix
Date: Thu, 25 Mar 2004 22:14:00 -0000	[thread overview]
Message-ID: <406359BA.9000302@gnu.org> (raw)
In-Reply-To: <yov5isgtqtxy.fsf@ldt-sj3-010.sj.broadcom.com>


>>>     As for having to tag each individual entry in the .igen file with an
>>>     explicit CPU. Yes, that sux. However, I also believe that it has
>>>     significantly reduced the overall error rate (no more breaking one
>>>     target by editing another) and that benefit vastly outweighs the short
>>>     term pain.
> 
> 
> I still take issue with the latter ("short term pain"), for such
> additions have to stay in for the life of support for the arch in the
> simulator, which *should* be quite long term.

Look at it this way, if the igen mechanism is used, gcc is able to 
eliminate everything :-)

If there's another way of achieving the same effect, I'm interested.

>>> But that was exactly what Andrew objected to:
> 
> 
> And he and I (strongly, IMO) disagreed at that time.  (IIRC, I think I
> mentioned at the time that the right solution to this is better
> testing.  I still think that's true.)
> 
> Of course, in August of last year, (unprompted by me!) he decided to
> stop being MIPS co-maintainer.  So, at this point, I'm the approval
> authority, and I like my style of patch most.  8-)
> 
> I would like to see it augmented to include some test code (now that
> there's a prelim test framework for mips, with what, 1 test? 8-), but
> as long as you commit to actually doing that I'm OK with it waiting a
> little bit.

Your call.

Andrew



  parent reply	other threads:[~2004-03-25 22:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-18 15:05 Richard Sandiford
     [not found] ` <mailpost.1079622402.27828@news-sj1-1>
2004-03-19  0:09   ` cgd
2004-03-18 17:57     ` cgd
2004-03-18 20:55     ` Richard Sandiford
2004-03-19  0:09       ` Richard Sandiford
2004-03-19 15:19       ` Andrew Cagney
2004-03-24  7:59         ` Richard Sandiford
2004-03-24 15:59           ` cgd
2004-03-25  7:15       ` cgd
2004-03-25  7:45         ` Richard Sandiford
     [not found]           ` <mailpost.1080200738.13330@news-sj1-1>
2004-03-25 18:53             ` cgd
2004-03-25 22:14         ` Andrew Cagney [this message]
2004-03-26  0:01           ` cgd
2004-03-26  0:28             ` Andrew Cagney
     [not found]               ` <mailpost.1080260907.10999@news-sj1-1>
2004-03-26  2:19                 ` cgd
2004-03-28 10:16     ` Richard Sandiford
     [not found]       ` <mailpost.1080469040.8967@news-sj1-1>
2004-03-29 19:38         ` cgd
2004-04-10  6:59         ` cgd
2004-03-19  0:09 ` Richard Sandiford

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=406359BA.9000302@gnu.org \
    --to=cagney@gnu.org \
    --cc=cgd@broadcom.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=rsandifo@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