From: "Suzuki K. Poulose" <suzuki@in.ibm.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Athira Rajeev <atrajeev@in.ibm.com>,
systemtap@sourceware.org, srikar@linux.vnet.ibm.com
Subject: Re: [PATCH] systemtap: Fix parsing of literals in SDT_V3 operand for s390x and ia64
Date: Thu, 11 Oct 2012 10:57:00 -0000 [thread overview]
Message-ID: <5076A60F.9010908@in.ibm.com> (raw)
In-Reply-To: <y0mvcej7j7f.fsf@fche.csb>
On 10/09/2012 09:04 PM, Frank Ch. Eigler wrote:
>
> atrajeev wrote:
>
>> systemtap fails to parse literal arguments of the format 'N' ( for
>> example in s390x and ia64 ) The regular expression to match literals
>> is defined in function "visit_target_symbol_arg" as below:
>>
>> ^[i\\$#][-]?[0-9][0-9]*$
>> [...]
>> This fails in s390x where literal is of the form 'N' which doesnt
>> have leading $ or i.
>
> Can the s390 do the same hack done for powerpc and add the 'i' prefix in
> sys/sdt.h?
>
> #if defined __powerpc__ || defined __powerpc64__
> # define _SDT_ARGTMPL(id) %I[id]%[id]
> #else
> # define _SDT_ARGTMPL(id) %[id]
> #endif
Frank,
We will try this and let you know the results. I guess we could do this
for ia64 as well.
>
>> [...]
>> - rc = regexp_match (asmarg, "^[i\\$#][-]?[0-9][0-9]*$", matches);
>> + rc = regexp_match (asmarg, "^[i\\$#]?[-]?[0-9][0-9]*$", matches);
>
> I would be worried about this change because of possible conflicts
> with the other operand addressing-mode combinations. (Recall that 'i'
> is added for ppc in order to separate register-number and
> literal-number cases.)
OK.
Thanks
Suzuki
>
> - FChE
>
next prev parent reply other threads:[~2012-10-11 10:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 14:24 Athira Rajeev
2012-10-09 15:37 ` Frank Ch. Eigler
2012-10-11 10:57 ` Suzuki K. Poulose [this message]
2012-10-12 16:07 ` Frank Ch. Eigler
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=5076A60F.9010908@in.ibm.com \
--to=suzuki@in.ibm.com \
--cc=atrajeev@in.ibm.com \
--cc=fche@redhat.com \
--cc=srikar@linux.vnet.ibm.com \
--cc=systemtap@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: 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).