From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Heike C. Zimmerer" Newsgroups: gmane.emacs.devel Subject: Re: gas-mode.el - Comments welcome Date: Thu, 31 May 2007 00:18:59 +0200 Organization: Mostly Harmless Message-ID: References: <20070531.032349.202076025.jet@gyve.org> Reply-To: hcz@hczim.de NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1180566816 8537 80.91.229.12 (30 May 2007 23:13:36 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 30 May 2007 23:13:36 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu May 31 01:13:30 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1HtXM8-00075L-Jv for ged-emacs-devel@m.gmane.org; Thu, 31 May 2007 01:13:28 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HtXM7-0007lo-VB for ged-emacs-devel@m.gmane.org; Wed, 30 May 2007 19:13:27 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HtXM5-0007lj-1o for emacs-devel@gnu.org; Wed, 30 May 2007 19:13:25 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HtXM3-0007lX-Jq for emacs-devel@gnu.org; Wed, 30 May 2007 19:13:24 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HtXM3-0007lU-Gg for emacs-devel@gnu.org; Wed, 30 May 2007 19:13:23 -0400 Original-Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1HtXM3-0002Ah-16 for emacs-devel@gnu.org; Wed, 30 May 2007 19:13:23 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HtX6O-0007Jm-OZ for emacs-devel@gnu.org; Thu, 31 May 2007 00:57:12 +0200 Original-Received: from p54a11deb.dip0.t-ipconnect.de ([84.161.29.235]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 31 May 2007 00:57:12 +0200 Original-Received: from hcz by p54a11deb.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 31 May 2007 00:57:12 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 34 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: p54a11deb.dip0.t-ipconnect.de User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/23.0.0 (gnu/linux) X-detected-kernel: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:72002 Archived-At: Masatake YAMATO writes: > Which architecture are you targeting on? i386? It is not bound to a specific architecture (there are just too many of them). Checking of opcodes or even arguments is IMHO better done by the assembler. However, it would be no big deal to highlight specific opcodes (the code is already there and used to recognize asm directives) or even to check for the correct number of arguments (the current parser returns the number of arguments). I've postponed this idea, since I feel it wouldn't buy much for me. Once you're accustomed to the instruction set (and I've seen a lot of exotic ones), getting opcode and number of arguments correct is not something that IMHO justifies another level of highlighting (I don't think the more's the better when it comes to it). I see that it might, however, be a coding aid for the occasional programmer and for beginners, so if there's enough interest in it, it can be done, preferably by reading the instruction set from some external configuration file. For now, we should stick with the present features and make sure they work rock solid. > gdb-ui.el could show disassembled code. If gas-mode can supports > font-locking well on multiple architectures' assembly code, > gas-mode's font-locking code can be applied to gdb-ui.el. That would be no big deal. gas-mode can parse any standard assembler line and return its syntactic fields, including positional information. Let's focus on that later. - Heike