From: Pedro Alves <pedro@palves.net>
To: Simon Marchi <simon.marchi@efficios.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 4/7] gdb: move store/extract integer functions to extract-store-integer.{c, h}
Date: Tue, 23 Apr 2024 19:03:52 +0100 [thread overview]
Message-ID: <a14ebe6b-79c7-477b-bacc-b1cf3ec804b0@palves.net> (raw)
In-Reply-To: <20240422201157.46375-5-simon.marchi@efficios.com>
On 2024-04-22 21:10, Simon Marchi wrote:
> diff --git a/gdb/extract-store-integer.c b/gdb/extract-store-integer.c
> new file mode 100644
> index 000000000000..a3b7e40d6424
> --- /dev/null
> +++ b/gdb/extract-store-integer.c
> @@ -0,0 +1,308 @@
> +/* Copyright (C) 2024 Free Software Foundation, Inc.
> +
The code moved here isn't new. (Copyright covers contents, not files.)
next prev parent reply other threads:[~2024-04-23 18:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 20:10 [PATCH 0/7] First cleanup of defs.h Simon Marchi
2024-04-22 20:10 ` [PATCH 1/7] gdb: move two declarations out " Simon Marchi
2024-04-22 20:10 ` [PATCH 2/7] gdb: move `enum compile_i_scope_types` to compile/compile.h Simon Marchi
2024-04-22 20:10 ` [PATCH 3/7] gdb: remove extract_long_unsigned_integer Simon Marchi
2024-04-22 20:10 ` [PATCH 4/7] gdb: move store/extract integer functions to extract-store-integer.{c,h} Simon Marchi
2024-04-23 18:03 ` Pedro Alves [this message]
2024-04-23 19:10 ` [PATCH 4/7] gdb: move store/extract integer functions to extract-store-integer.{c, h} Simon Marchi
2024-04-23 19:40 ` Pedro Alves
2024-04-22 20:10 ` [PATCH 5/7] gdb: move RequireLongest to gdbsupport/traits.h Simon Marchi
2024-04-22 20:10 ` [PATCH 6/7] gdb: don't include hashtab.h in defs.h Simon Marchi
2024-04-22 20:10 ` [PATCH 7/7] gdb: don't include gdbsupport/array-view.h " Simon Marchi
2024-04-22 22:55 ` [PATCH 0/7] First cleanup of defs.h John Baldwin
2024-04-23 1:38 ` Simon Marchi
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=a14ebe6b-79c7-477b-bacc-b1cf3ec804b0@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.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).