Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: Kevin Buettner <kevinb@redhat.com>,
	gdb-patches@sources.redhat.com, nick@duffek.com
Subject: Re: [PATCH RFC] AIX thread support
Date: Sat, 13 Jul 2002 05:25:00 -0000	[thread overview]
Message-ID: <1020713011530.ZM10495@localhost.localdomain> (raw)
In-Reply-To: Andrew Cagney <ac131313@ges.redhat.com> "Re: [PATCH RFC] AIX thread support" (Jul 12,  6:59pm)

On Jul 12,  6:59pm, Andrew Cagney wrote:

> > 	From Nicholas Duffek (with minor changes by Martin Hunt, 
> > 	Louis Hamilton, and Kevin Buettner):
> > 	* aix-thread.c: New file.
> > 	* Makefile.in (ALLDEPFILES): Add aix-thread.c.
> > 	(aix-thread.o): New rule.
> > 	* configure.host (gdb_host): Set to aix432 on AIX 4.3.2+.
> > 	* config/powerpc/aix432.mh: New file.
> 
[...]
> A quick glance suggests a review is needed.   For instance, from a 
> coding (not thread -> MichaelS) viewpoint ``#define DEBUG 0'' should be 
> handled at run-time and should be written to ``gdb_stdlog''.  If 
> anything, perhaphs like for ada, this file could be initially commited, 
> but not actually included/enabled.  That should at least make the review 
> process easier.

As suggested, I've commited aix-thread.c to make the review process
easier.

Keep in mind that aix-thread.c will only be used for native AIX
builds.  As such, I think the criteria for including/enabling this
code should be much lower than that for core code or even target
specific code.

I do agree that there are a number of things in this file which should
be cleaned up over time.  However, for the initial review, I suggest
that we focus on issues which might make overall GDB maintenance or
future GDB development more difficult.  Only issues which meet these
criteria should prevent aix-thread.c from being accepted.

I certainly have no objection, however, to reviewers identifying other
cleanups that should occur over time.  I think your comment regarding
``#define DEBUG 0'' is a good example of this.

Kevin


  reply	other threads:[~2002-07-13  1:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-12 12:46 Kevin Buettner
2002-07-12 16:12 ` Andrew Cagney
2002-07-13  5:25   ` Kevin Buettner [this message]
2002-07-13 17:25     ` Andrew Cagney

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=1020713011530.ZM10495@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=ac131313@ges.redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nick@duffek.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