public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Mihails Strasuns <mihails.strasuns@intel.com>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] gdb/testsuite: tweak compiler flag handling in jit-elf-helpers.exp
Date: Thu, 2 Jul 2020 21:02:29 -0400	[thread overview]
Message-ID: <c74ee918-095f-739e-6bee-c6920e8c18c8@simark.ca> (raw)
In-Reply-To: <20200616114530.5068-1-mihails.strasuns@intel.com>

On 2020-06-16 7:45 a.m., Mihails Strasuns via Gdb-patches wrote:
> db/testsuite/ChangeLog:
> 2020-06-16  Mihails Strasuns  <mihails.strasuns@intel.com>
> 
> 	* lib/jit-elf-helpers.exp (compile_jit_elf_main_as_so): Remove
> 	unused $options parameter.
> 	(compile_and_download_n_jit_so): Add optional parameter for
> 	specifying extra compiler flags.
> 	* gdb.base/jit-elf-so.exp: Do not pass compiler flag argument,
> 	it is already added by the proc itself.

Thanks that LGTM.  I would perhaps have added the new options argument in the next
patch, that actually uses it but... not a big deal.

Btw, just a nit.  Normally, the ChangeLog entry should just say very briefly what
changed not why, or go into explanations.  We prefer to put the longer explanation
about the change, the rationale, etc, in the commit message itself.  It's easier
to write something descriptive in prose there than in the ChangeLog entry, which,
by its nature, restricts the format.

So for the ChangeLog entry, you can be very brief, like:

 	* lib/jit-elf-helpers.exp (compile_jit_elf_main_as_so): Remove
 	$options parameter.
 	(compile_and_download_n_jit_so): Add optional options parameter.
 	* gdb.base/jit-elf-so.exp: Do not pass compiler flag argument.

Simon

      parent reply	other threads:[~2020-07-03  1:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16 11:45 Mihails Strasuns
2020-06-16 11:45 ` [PATCH 2/2] Disable breakpoint locations in unloaded jit objects Mihails Strasuns
2020-06-30 12:35   ` Strasuns, Mihails
2020-07-03  1:48   ` Simon Marchi
2020-07-03  1:02 ` Simon Marchi [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=c74ee918-095f-739e-6bee-c6920e8c18c8@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=mihails.strasuns@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).