Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Doug Evans <xdje42@gmail.com>
Cc: Yao Qi <yao@codesourcery.com>, Tom Tromey <tromey@redhat.com>,
	       Hui Zhu <hui_zhu@mentor.com>,
	       gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: target-delegates.c needs some TLC [was Re: [OB PATCH] target.h (to_traceframe_info): Fix TARGET_DEFAULT_RETURN]
Date: Fri, 07 Mar 2014 18:33:00 -0000	[thread overview]
Message-ID: <531A110B.4060502@redhat.com> (raw)
In-Reply-To: <CAP9bCMTwuW_2_3Dn+JynOxtgyv862ghs8GZgOyUm8MbEcfb=Tw@mail.gmail.com>

On 03/06/2014 05:20 AM, Doug Evans wrote:
> On Mon, Mar 3, 2014 at 5:36 PM, Yao Qi <yao@codesourcery.com> wrote:
>> On 03/04/2014 09:18 AM, Hui Zhu wrote:
>>> I cannot understand about this OB is not right.  I have 2 questions to you:
>>> 1. Before my patch, does target-delegates.c that generated by make-target-delegates is same with current target-delegates.c?
>>
>> No, as I said, I forgot to re-generate target-delegates.c.
> 
> Hmmm....
> 
> I don't even see target-delegates.c in Makefile.in.  That feels like a
> bug. [Could be blind of course. :-)]
> I realize there's a comment in target-delegates.c that says how to
> regenerate it, but these kind of things are part of what makefiles are
> for.

This also crossed my mind when initially reviewing the series (and
I'm sure Tom's too when writing it, as it's such an obvious thing),
but realized this is really no different from e.g., gdbarch.h|c.

So given the precedent, I don't consider this a particular bug of
target-delegates.c, but a more generic "IWBN if we had Makefile
rules for our generated files".

Of course, I'd welcome patches in that direction.

> I'm not sure I'd want to require perl for --enable-maintainer-mode
> (which is a common trigger for enabling in makefiles the appropriate
> rules to auto-regenerate checked-in machine-generated files), but it's
> one thought.

I don't see a problem there.  automake is perl as well, for instance,
and it's common for --enable-maintainer-mode to trigger automake/aclocal.

Even if that weren't true, by configuring with --enable-maintainer-mode,
by definition you're asserting you have the tools required for
regular gdb maintenance, and given make-target-delegates is perl,
well, any maintainer must have it handy.

-- 
Pedro Alves


  reply	other threads:[~2014-03-07 18:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06  5:20 Doug Evans
2014-03-07 18:33 ` Pedro Alves [this message]
2014-03-09 23:16   ` Doug Evans
2014-03-21 16:25     ` Pedro Alves
2014-03-10  2:47 ` Yao Qi
2014-03-10  2:54   ` Hui Zhu
2014-03-10  5:34   ` Doug Evans

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=531A110B.4060502@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=hui_zhu@mentor.com \
    --cc=tromey@redhat.com \
    --cc=xdje42@gmail.com \
    --cc=yao@codesourcery.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