Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Peter Bergner <bergner@vnet.ibm.com>
To: Alan Modra <amodra@gmail.com>
Cc: Pedro Alves <palves@redhat.com>, Eli Zaretskii <eliz@gnu.org>,
	       nickc@redhat.com, gdb-patches@sourceware.org,
	uweigand@de.ibm.com,        binutils@sourceware.org
Subject: Re: [PATCH 1/2] Add support for setting disassembler-options in GDB for POWER, ARM and S390
Date: Tue, 24 Jan 2017 02:39:00 -0000	[thread overview]
Message-ID: <b17de542-fbf7-977a-bcc3-e6fd722c9236@vnet.ibm.com> (raw)
In-Reply-To: <20170124015651.GH28669@bubble.grove.modra.org>

On 1/23/17 7:56 PM, Alan Modra wrote:
> On Mon, Jan 23, 2017 at 05:34:36PM -0600, Peter Bergner wrote:
>>  The following S/390 specific disassembler options are supported for use\n\
>>  with the -M switch (multiple options should be separated by commas):\n"));
>>
>> -  fprintf (stream, _("  esa         Disassemble in ESA architecture mode\n"));
>> -  fprintf (stream, _("  zarch       Disassemble in z/Architecture mode\n"));
>> -  fprintf (stream, _("  insnlength  Print unknown instructions according "
>> -		     "to length from first two bits\n"));
>> +  for (i = 0; sizeof (options) / sizeof (options[0]); i++)
>> +    {
>> +      unsigned int len = strlen (options[i].name);
>> +      if (max_len < len)
>> +	max_len = len;
>> +    }
>> +
>> +  for (i = 0, max_len++; sizeof (options) / sizeof (options[0]); i++)
>> +    fprintf (stream, "  %s%*c %s",
>> +	     options[i].name,
>> +	     (int)(max_len - strlen (options[i].name)), ' ',
>> +	     options[i].description);
>>  }
>
> This appears to have lost translation of the help strings.

They're stored in:

diff --git a/opcodes/s390-dis.c b/opcodes/s390-dis.c
index 328ba2d..6b455aa 100644
--- a/opcodes/s390-dis.c
+++ b/opcodes/s390-dis.c
[snip]
+static const options_t options[] =
+{
+  { "esa" ,       "Disassemble in ESA architecture mode" },
+  { "zarch",      "Disassemble in z/Architecture mode" },
+  { "insnlength", "Print unknown instructions according to "
+		  "length from first two bits" }
+};

...and outputted via the loops above.  Or do you mean
language translation?

Peter



  reply	other threads:[~2017-01-24  2:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17 19:19 Peter Bergner
2016-11-17 19:52 ` Peter Bergner
2016-11-18 10:25 ` Nick Clifton
2016-11-18 15:10   ` Peter Bergner
2016-11-18 15:38     ` Eli Zaretskii
2016-11-18 16:56       ` Peter Bergner
2016-11-18 17:08         ` Eli Zaretskii
2016-11-18 17:23         ` Pedro Alves
2016-11-22 17:04           ` Peter Bergner
2016-11-22 17:40             ` Pedro Alves
2017-01-23 23:35           ` Peter Bergner
2017-01-24  1:57             ` Alan Modra
2017-01-24  2:39               ` Peter Bergner [this message]
2017-01-24  3:36                 ` Alan Modra
2017-01-24  4:32                   ` Peter Bergner
2017-01-24 16:00                     ` Peter Bergner
2017-01-25  4:31                       ` Alan Modra
2017-01-25 17:20                         ` Peter Bergner
2017-01-24  3:29             ` Eli Zaretskii
     [not found]             ` <20170125142335.GT28060@E107787-LIN>
2017-01-25 14:30               ` Peter Bergner
2017-01-31 21:13               ` Peter Bergner
2017-02-01 21:44                 ` Yao Qi

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=b17de542-fbf7-977a-bcc3-e6fd722c9236@vnet.ibm.com \
    --to=bergner@vnet.ibm.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=nickc@redhat.com \
    --cc=palves@redhat.com \
    --cc=uweigand@de.ibm.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