public inbox for cgen-cvs@sourceware.org help / color / mirror / Atom feed
From: fche@sourceware.cygnus.com To: cgen-cvs@sourceware.cygnus.com Subject: src/cgen ChangeLog desc-cpu.scm mach.scm doc/r ... Date: Wed, 11 Jul 2001 19:32:00 -0000 [thread overview] Message-ID: <20010712023225.20058.qmail@sourceware.cygnus.com> (raw) CVSROOT: /cvs/src Module name: src Changes by: fche@sources.redhat.com 2001-07-11 19:32:25 Modified files: cgen : ChangeLog desc-cpu.scm mach.scm cgen/doc : rtl.texi Log message: * some support for funny-endian 16/32-bit insn sets [cgen/ChangeLog] 2001-07-11 Frank Ch. Eigler <fche@redhat.com> * desc-cpu.scm (-gen-mach-table-defns): Emit fourth field: the mach->cpu insn-chunk-bitsize. (-gen-cpu-open): In @arch@_cgen_rebuild_tables, process above new field toward CGEN_CPU_TABLE->insn_chunk_bitsize. * mach.scm (<cpu>): New field insn-chunk-bitsize. (-cpu-parse, -cpu-read): Parse/initialize it. * doc/rtl.texi (define-cpu): Document it. [opcodes/ChangeLog] 2001-07-11 Frank Ch. Eigler <fche@redhat.com> * cgen-dis.in (print_insn): Use cgen_get_insn_value instead of bfd_get_bits. * cgen-opc.c (cgen_get_insn_value, cgen_put_insn_value): Respect non-zero CGEN_CPU_DESC->insn_chunk_bitsize. [include/opcode/ChangeLog] 2001-07-11 Frank Ch. Eigler <fche@redhat.com> * cgen.h (CGEN_MACH): Add insn_chunk_bitsize field. (cgen_cpu_desc): Ditto. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/cgen/ChangeLog.diff?cvsroot=src&r1=1.73&r2=1.74 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/cgen/desc-cpu.scm.diff?cvsroot=src&r1=1.7&r2=1.8 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/cgen/mach.scm.diff?cvsroot=src&r1=1.1.1.1&r2=1.2 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/cgen/doc/rtl.texi.diff?cvsroot=src&r1=1.9&r2=1.10
reply other threads:[~2001-07-11 19:32 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010712023225.20058.qmail@sourceware.cygnus.com \ --to=fche@sourceware.cygnus.com \ --cc=cgen-cvs@sourceware.cygnus.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: linkBe 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).