From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9017 invoked by alias); 24 Jan 2011 14:24:00 -0000 Received: (qmail 8996 invoked by uid 22791); 24 Jan 2011 14:23:59 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 24 Jan 2011 14:23:56 +0000 Received: (qmail 6839 invoked from network); 24 Jan 2011 14:23:55 -0000 Received: from unknown (HELO localhost) (froydnj@127.0.0.2) by mail.codesourcery.com with ESMTPA; 24 Jan 2011 14:23:55 -0000 Date: Mon, 24 Jan 2011 14:24:00 -0000 From: Nathan Froyd To: cgen@sourceware.org Subject: insn semantics required? Message-ID: <20110124142354.GE6247@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.17+20080114 (2008-01-14) X-IsSubscribed: yes Mailing-List: contact cgen-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cgen-owner@sourceware.org X-SW-Source: 2011-q1/txt/msg00001.txt.bz2 I've been looking through the documentation and couldn't determine conclusively whether defining the semantics of an insn is required. Is it? Auto-magically defining a simulator seems less useful in this day and age, but an auto-generated assembler and disassembler seems quite useful. I suppose as a stopgap one could simply provide an uninteresting semantics for each insn. -Nathan