public inbox for cgen-cvs@sourceware.org help / color / mirror / Atom feed
From: devans@sourceware.org To: cgen-cvs@sourceware.org Subject: src/cgen ChangeLog opcodes.scm Date: Thu, 15 Oct 2009 06:13:00 -0000 [thread overview] Message-ID: <20091015061320.407.qmail@sourceware.org> (raw) CVSROOT: /cvs/src Module name: src Changes by: devans@sourceware.org 2009-10-15 06:13:20 Modified files: cgen : ChangeLog opcodes.scm Log message: * opcode.scm (<ifield>, 'gen-insert): Use ifld-decode-mode instead of ifld-encode-mode. (<multi-ifield>, 'gen-insert): Ditto. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/cgen/ChangeLog.diff?cvsroot=src&r1=1.398&r2=1.399 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/cgen/opcodes.scm.diff?cvsroot=src&r1=1.18&r2=1.19
next reply other threads:[~2009-10-15 6:13 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-10-15 6:13 devans [this message] -- strict thread matches above, loose matches on Subject: below -- 2005-04-04 10:10 nickc 2005-01-20 23:12 jimb 2001-07-05 7:11 bje
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=20091015061320.407.qmail@sourceware.org \ --to=devans@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: 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).