This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Systemtap on ARM arch results summary
- From: David Smith <dsmith at redhat dot com>
- To: David Long <dave dot long at linaro dot org>, William Cohen <wcohen at redhat dot com>
- Cc: Naresh Kamboju <naresh dot kamboju at linaro dot org>, systemtap at sourceware dot org
- Date: Thu, 12 Jun 2014 14:49:07 -0500
- Subject: Re: Systemtap on ARM arch results summary
- Authentication-results: sourceware.org; auth=none
- References: <CA+G9fYtV4apghaFPDQcD7-xbvG_Ua1mEUi=jcxVYfOQdwzAPXA at mail dot gmail dot com> <5399C1BE dot 1050409 at redhat dot com> <5399C4D6 dot 3070502 at linaro dot org> <5399CA64 dot 8050809 at redhat dot com> <5399DA51 dot 80904 at linaro dot org>
On 06/12/2014 11:50 AM, David Long wrote:
> On 06/12/14 11:42, William Cohen wrote:
>> Do you have a patch set showing where you needed to make changes to
>> the *.exp files?
>>
>
> I have something, but it is a total hack. I just hardcoded the -marm
> where needed, for a quick test. My plan is to go back and make that
> conditional on the target type. This does bring up an interesting point
> though. I didn't see an obvious way to pass global compiler options
> into the test cases. That would have been very helpful. At any rate I
> think some global mechanism is needed to deal with CPUs that support
> multiple instruction sets. Eventually we'd want to run systemtap
> multiple times on a given platform, to test thumb, thumb2, ARM, and/or
> 64bit. Maybe other more specific code generation options too.
Actually we do have a global mechanism for compile flags. It is found in
testsuite/lib/compile_flags.exp. Unfortunately I see that several tests
don't actually use it. I'll see if I can't fix that.
--
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)