From: "Jan Beulich" <JBeulich@novell.com>
To: <wilson@specifixinc.com>
Cc: <binutils@sources.redhat.com>
Subject: Re: [PATCH] Re: ia64: @ not allowed to start symbol?
Date: Mon, 14 Feb 2005 19:45:00 -0000 [thread overview]
Message-ID: <s210bc83.041@emea1-mh.id2.novell.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1717 bytes --]
>>> James E Wilson <wilson@specifixinc.com> 11.02.05 02:10:07 >>>
>On Tue, 2005-02-08 at 08:27, Jan Beulich wrote:
>> * config/tc-ia64.h (LEX_AT): Include LEX_BEGIN_NAME.
>> (LEX_QM): Likewise.
>> ...
>
>OK.
The previously committed patch to allow @ and ? at the start of symbol
names
was incomplete; the scrubber still didn't know about these two.
Built and tested on ia64-unknown-linux-gnu.
Jan
gas/
2005-02-14 Jan Beulich <jbeulich@novell.com>
* config/tc-ia64.h (ia64_symbol_chars): Declare.
(ty_symbol_chars): Define.
* config/tc-ia64.c (ia64_symbol_chars): Define.
---
/home/jbeulich/src/binutils/mainline/2005-02-14/gas/config/tc-ia64.c 2005-02-14
08:56:13.000000000 +0100
+++ 2005-02-14/gas/config/tc-ia64.c 2005-02-14 15:43:36.807863235
+0100
@@ -174,6 +174,10 @@ static struct hash_control *alias_name_h
static struct hash_control *secalias_hash;
static struct hash_control *secalias_name_hash;
+/* List of chars besides those in app.c:symbol_chars that can start
an
+ operand. Used to prevent the scrubber eating vital white-space.
*/
+const char ia64_symbol_chars[] = "@?";
+
/* Characters which always start a comment. */
const char comment_chars[] = "";
---
/home/jbeulich/src/binutils/mainline/2005-02-14/gas/config/tc-ia64.h 2005-02-08
17:18:43.000000000 +0100
+++ 2005-02-14/gas/config/tc-ia64.h 2005-02-14 15:43:36.808839797
+0100
@@ -78,6 +78,9 @@ extern const char *ia64_target_format PA
#define LEX_QM (LEX_NAME|LEX_BEGIN_NAME) /* allow `?'
inside name */
#define LEX_HASH LEX_END_NAME /* allow `#' ending a name */
+extern const char ia64_symbol_chars[];
+#define tc_symbol_chars ia64_symbol_chars
+
#define SUB_SEGMENT_ALIGN(SEG, FRCHAIN) 0
struct ia64_fix
[-- Attachment #2: binutils-mainline-ia64-lex-at-qm-2.patch --]
[-- Type: text/plain, Size: 1504 bytes --]
The previously committed patch to allow @ and ? at the start of symbol names
was incomplete; the scrubber still didn't know about these two.
Built and tested on ia64-unknown-linux-gnu.
Jan
gas/
2005-02-14 Jan Beulich <jbeulich@novell.com>
* config/tc-ia64.h (ia64_symbol_chars): Declare.
(ty_symbol_chars): Define.
* config/tc-ia64.c (ia64_symbol_chars): Define.
--- /home/jbeulich/src/binutils/mainline/2005-02-14/gas/config/tc-ia64.c 2005-02-14 08:56:13.000000000 +0100
+++ 2005-02-14/gas/config/tc-ia64.c 2005-02-14 15:43:36.807863235 +0100
@@ -174,6 +174,10 @@ static struct hash_control *alias_name_h
static struct hash_control *secalias_hash;
static struct hash_control *secalias_name_hash;
+/* List of chars besides those in app.c:symbol_chars that can start an
+ operand. Used to prevent the scrubber eating vital white-space. */
+const char ia64_symbol_chars[] = "@?";
+
/* Characters which always start a comment. */
const char comment_chars[] = "";
--- /home/jbeulich/src/binutils/mainline/2005-02-14/gas/config/tc-ia64.h 2005-02-08 17:18:43.000000000 +0100
+++ 2005-02-14/gas/config/tc-ia64.h 2005-02-14 15:43:36.808839797 +0100
@@ -78,6 +78,9 @@ extern const char *ia64_target_format PA
#define LEX_QM (LEX_NAME|LEX_BEGIN_NAME) /* allow `?' inside name */
#define LEX_HASH LEX_END_NAME /* allow `#' ending a name */
+extern const char ia64_symbol_chars[];
+#define tc_symbol_chars ia64_symbol_chars
+
#define SUB_SEGMENT_ALIGN(SEG, FRCHAIN) 0
struct ia64_fix
next reply other threads:[~2005-02-14 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-14 19:45 Jan Beulich [this message]
2005-02-15 0:01 ` James E Wilson
-- strict thread matches above, loose matches on Subject: below --
2005-02-08 20:05 Jan Beulich
2005-02-11 7:05 ` James E Wilson
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=s210bc83.041@emea1-mh.id2.novell.com \
--to=jbeulich@novell.com \
--cc=binutils@sources.redhat.com \
--cc=wilson@specifixinc.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: link
Be 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).