public inbox for
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <>
Cc: Andrew Burgess <>, Tom Tromey <>,
	 Richard Bunt <>
Subject: [PATCH v3 0/5] gdb: introduce limited array lengths while printing values
Date: Mon, 23 Jan 2023 23:00:10 +0000 (GMT)	[thread overview]
Message-ID: <> (raw)


 This is v3 of the patch series, addressing the suggestion made by Andrew 
for v2 as to the use of `value_copy' and then updating the copyright year 
across a couple of newly-added files which I missed with v2 and making Ada 
and Fortran test cases match changes made since to our trunk.

 I have also noticed and simplified redundant code in `value_copy', where 
the case of the source and destination lengths being different from each 
other was explicitly handled, while the lengths are always equal (one set 
from the other right beforehand).

 See individual change descriptions for details.

 I have regression-tested it natively with a `x86_64-linux-gnu' system.  
OK to apply?


             reply	other threads:[~2023-01-23 23:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23 23:00 Maciej W. Rozycki [this message]
2023-01-23 23:13 ` [PATCH v3 1/5] GDB: Ignore `max-value-size' setting with value history accesses Maciej W. Rozycki
2023-01-31 17:58   ` Tom Tromey
2023-02-10 14:17     ` Maciej W. Rozycki
2023-01-23 23:13 ` [PATCH v3 2/5] GDB: Fix the mess with value byte/bit range types Maciej W. Rozycki
2023-01-31 18:09   ` Tom Tromey
2023-02-10 14:18     ` Maciej W. Rozycki
2023-02-10 14:49       ` Tom Tromey
2023-01-23 23:14 ` [PATCH v3 3/5] GDB: Only make data actually retrieved into value history available Maciej W. Rozycki
2023-01-31 18:47   ` Tom Tromey
2023-02-10 14:18     ` Maciej W. Rozycki
2023-02-10 21:11       ` Tom Tromey
2023-01-23 23:14 ` [PATCH v3 4/5] GDB/testsuite: Add `-nonl' option to `gdb_test' Maciej W. Rozycki
2023-01-31 19:02   ` Tom Tromey
2023-01-23 23:14 ` [PATCH v3 5/5] GDB: Introduce limited array lengths while printing values Maciej W. Rozycki
2023-01-24 12:59   ` Eli Zaretskii
2023-01-31 20:49   ` Tom Tromey
2023-02-10 14:18     ` Maciej W. Rozycki

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).