public inbox for cgen-cvs@sourceware.org
help / color / mirror / Atom feed
From: amodra@sourceware.org
To: cgen-cvs@sourceware.org
Subject: src/cgen ChangeLog desc-cpu.scm opc-asmdis.scm ...
Date: Sat, 03 Mar 2018 01:31:00 -0000 [thread overview]
Message-ID: <20180303013131.63552.qmail@sourceware.org> (raw)
CVSROOT: /cvs/src
Module name: src
Changes by: amodra@sourceware.org 2018-03-03 01:31:31
Modified files:
cgen : ChangeLog desc-cpu.scm opc-asmdis.scm
opc-ibld.scm utils.scm
Log message:
binutils opcodes error messages
This patch is aimed at making binutils/opcodes files comply with the
GNU coding standard regarding error messages, that is, they should
start with the program name followed by a colon, then a lower case
message. Accomplished by calling opcodes_error_handler to output the
program name (and final '\n'), rather than calling fprintf.
* desc-cpu.scm (opcodes_error_handler): Define.
(@arch@_cgen_rebuild_tables): Use opcodes_error_handler.
(@arch@_cgen_cpu_open): Likewise.
* opc-asmdis.scm (@arch@_cgen_parse_operand): Likewise.
(@arch@_cgen_print_operand): Likewise.
* opc-ibld.scm (@arch@_cgen_get_int_operand): Likewise.
(@arch@_cgen_get_vma_operand): Likewise.
(@arch@_cgen_set_int_operand): Likewise.
(@arch@_cgen_set_vma_operand): Likewise.
(@arch@_cgen_insert_operand): Likewise.
(@arch@_cgen_extract_operand): Likewise.
* utils.scm: Update emitted copyright dates.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/src/cgen/ChangeLog.diff?cvsroot=src&r1=1.483&r2=1.484
http://sourceware.org/cgi-bin/cvsweb.cgi/src/cgen/desc-cpu.scm.diff?cvsroot=src&r1=1.35&r2=1.36
http://sourceware.org/cgi-bin/cvsweb.cgi/src/cgen/opc-asmdis.scm.diff?cvsroot=src&r1=1.8&r2=1.9
http://sourceware.org/cgi-bin/cvsweb.cgi/src/cgen/opc-ibld.scm.diff?cvsroot=src&r1=1.9&r2=1.10
http://sourceware.org/cgi-bin/cvsweb.cgi/src/cgen/utils.scm.diff?cvsroot=src&r1=1.40&r2=1.41
next reply other threads:[~2018-03-03 1:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-03 1:31 amodra [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-01 11:16 nickc
2001-10-09 1:24 nickc
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=20180303013131.63552.qmail@sourceware.org \
--to=amodra@sourceware.org \
--cc=cgen-cvs@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).