Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Aidan Skinner <aidan@velvet.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] remove ada-exp.tab.c
Date: Thu, 06 Jun 2002 09:21:00 -0000	[thread overview]
Message-ID: <3CFF8BFD.6070405@cygnus.com> (raw)
In-Reply-To: <20020606164924.S617@velvet.net>

> On Wed, Jun 05, 2002 at 12:33:19PM -0400, Andrew Cagney wrote
> 
> 
>> For .l and .y files I think they really should be rebuildable with any 
>> (and not a specific lex/yacc et.al.).
> 
> 
> I have access to FreeBSD and OpenBSD machines, and an Irix box if I
> don't scrub it for debian, is there a reasonably brain-dead
> implementation available for these that I can test with?

Try it with the boxes you have access to.  However, no need to go out of 
your way.  If developers encounter problems on various hosts they will 
soon let us know :-)

> If nobody has any further objects, I'll remove ada-exp.tab.c tommorrow
> morning.

No need to wait. I believe that ada-lex.c is also generated and, hence, 
should be deleted for similar reasons.

Anyway, now that the code is in CVS I've had a better look.  The 
immediate things are very standard:

- coding style, I noticed things like:
	for () {
	}
The fix is to put the .[hc] files through gdb_indent.sh and commit the 
result.

- See http://sources.redhat.com/gdb/current/ari/ and note the 
regressions (things purged from GDB) related to the ada files.  Things 
like malloc, free, printf("%p") et.al.  You could also look at errors 
and deprecated, however regressions are the big ones(1).

- Can it be built when configured with configured with 
--enable-gdb-build-warnings=,-Werror and fix the results.  If you hit 
problems due to those #if 0's don't be to worried at this stage.

- I noticed that the debug code is using ``fprintf (stderr, ...''.  It 
should use ``fprintf_unfiltered (gdb_stdlog, ...''.  It isn't under 
regressions since the purge of fprintf() is ongoing.  I don't think it 
is fair to give Pierre more work to do though :-)

These are all considered `obvious' so, at your lesure.


Do you want to start working through the other changes?


enjoy,
Andrew

(1) I checked the table last night and the script/table contained a bug. 
  Todays re-generate will be more correct.



      reply	other threads:[~2002-06-06 16:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04 13:03 Aidan Skinner
2002-06-05  9:05 ` Joel Brobecker
2002-06-05  9:20   ` Aidan Skinner
2002-06-05  9:33   ` Andrew Cagney
2002-06-06  8:49     ` Aidan Skinner
2002-06-06  9:21       ` Andrew Cagney [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=3CFF8BFD.6070405@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=aidan@velvet.net \
    --cc=gdb-patches@sources.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