public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/features: re-generate riscv/{32,64}bit-csr.c
Date: Thu, 18 Jun 2020 16:37:11 -0400	[thread overview]
Message-ID: <50976a9f-bb32-baee-17b4-c97917189d69@polymtl.ca> (raw)
In-Reply-To: <20200618201756.GF2737@embecosm.com>

On 2020-06-18 4:17 p.m., Andrew Burgess wrote:
> * Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> [2020-06-18 15:39:05 -0400]:
> 
>> Running
>>
>>     make cfiles GDB=...
>>
>> inside the gdb/features source directory leads to those two files
>> becoming dirty.  I did a bisect, and found that it started with this
>> commit:
>>
>>     commit bd0cf5a6bae180f65f3b9298619d1bd695abcdd8
>>     Author: Nelson Chu <nelson.chu@sifive.com>
>>     Date:   Wed Feb 12 02:18:49 2020 -0800
>>
>>         RISC-V: Support the ISA-dependent CSR checking.
>>
>> This patch commits the re-generated files.
>>
>> gdb/ChangeLog:
>>
>> 	* features/riscv/32bit-csr.c: Re-generate.
>> 	* features/riscv/64bit-csr.c: Re-generate.
> 
> You're welcome to merge this, but:
> 
>   https://sourceware.org/pipermail/gdb-patches/2020-June/169568.html
> 

Ah! I didn't see this.  It would be good for my commit stats to merge it, but
if you're going to merge your series soon-ish, I will just abandon this patch.

Simon


      reply	other threads:[~2020-06-18 20:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18 19:39 Simon Marchi
2020-06-18 20:17 ` Andrew Burgess
2020-06-18 20:37   ` 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=50976a9f-bb32-baee-17b4-c97917189d69@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    /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).