All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Vlasenko <vda.linux@googlemail.com>
To: Hannes Reinecke <hare@suse.de>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 1/3] aic7xxx: introduce "dont_generate_debug_code" keyword in aicasm parser
Date: Tue, 1 Jul 2008 18:50:36 +0200	[thread overview]
Message-ID: <200807011850.36107.vda.linux@googlemail.com> (raw)
In-Reply-To: <200807011848.22599.vda.linux@googlemail.com>

Introduce "dont_generate_debug_code" keyword in aicasm parser.

Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
--
vda

--- linux-2.6.26-rc8.org/drivers/scsi/aic7xxx/aicasm/aicasm_gram.y	Tue Jul  1 17:07:14 2008
+++ linux-2.6.26-rc8/drivers/scsi/aic7xxx/aicasm/aicasm_gram.y	Tue Jul  1 17:06:58 2008
@@ -147,6 +147,8 @@
 
 %token T_ACCESS_MODE
 
+%token T_DONT_GENERATE_DEBUG_CODE
+
 %token T_MODES
 
 %token T_DEFINE
@@ -357,6 +359,7 @@
 |	size
 |	count
 |	access_mode
+|	dont_generate_debug_code
 |	modes
 |	field_defn
 |	enum_defn
@@ -407,6 +410,13 @@
 	T_ACCESS_MODE T_MODE
 	{
 		cur_symbol->info.rinfo->mode = $2;
+	}
+;
+
+dont_generate_debug_code:
+	T_DONT_GENERATE_DEBUG_CODE
+	{
+		cur_symbol->dont_generate_debug_code = 1;
 	}
 ;
 
--- linux-2.6.26-rc8.org/drivers/scsi/aic7xxx/aicasm/aicasm_scan.l	Tue Jul  1 17:07:14 2008
+++ linux-2.6.26-rc8/drivers/scsi/aic7xxx/aicasm/aicasm_scan.l	Tue Jul  1 17:06:58 2008
@@ -164,6 +164,7 @@
 address			{ return T_ADDRESS; }
 count			{ return T_COUNT; }
 access_mode		{ return T_ACCESS_MODE; }
+dont_generate_debug_code { return T_DONT_GENERATE_DEBUG_CODE; }
 modes			{ return T_MODES; }
 RW|RO|WO		{
 				 if (strcmp(yytext, "RW") == 0)
--- linux-2.6.26-rc8.org/drivers/scsi/aic7xxx/aicasm/aicasm_symbol.c	Tue Jul  1 17:07:14 2008
+++ linux-2.6.26-rc8/drivers/scsi/aic7xxx/aicasm/aicasm_symbol.c	Tue Jul  1 17:06:58 2008
@@ -539,6 +539,9 @@
 	aic_print_include(dfile, stock_include_file);
 	SLIST_FOREACH(curnode, &registers, links) {
 
+		if (curnode->symbol->dont_generate_debug_code)
+			continue;
+
 		switch(curnode->symbol->type) {
 		case REGISTER:
 		case SCBLOC:
--- linux-2.6.26-rc8.org/drivers/scsi/aic7xxx/aicasm/aicasm_symbol.h	Tue Jul  1 17:07:14 2008
+++ linux-2.6.26-rc8/drivers/scsi/aic7xxx/aicasm/aicasm_symbol.h	Tue Jul  1 17:06:58 2008
@@ -137,7 +137,8 @@
 		struct label_info *linfo;
 		struct cond_info  *condinfo;
 		struct macro_info *macroinfo;
-	}info;
+	} info;
+	int	dont_generate_debug_code;
 } symbol_t;
 
 typedef struct symbol_ref {

  reply	other threads:[~2008-07-01 14:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01 16:48 [PATCH 0/3] aic7xxx: debloat Denys Vlasenko
2008-07-01 16:50 ` Denys Vlasenko [this message]
2008-07-01 16:52   ` [PATCH 2/3] aic7xxx: update .reg files Denys Vlasenko
2008-07-01 16:54     ` [PATCH 3/3] aic7xxx: update *_shipped files Denys Vlasenko
2008-07-01 17:02     ` [PATCH 2/3] aic7xxx: update .reg files Denys Vlasenko
2008-07-02  9:17 ` [PATCH 0/3] aic7xxx: debloat Hannes Reinecke
2008-07-02  9:17   ` Hannes Reinecke

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=200807011850.36107.vda.linux@googlemail.com \
    --to=vda.linux@googlemail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=hare@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.