perf on parisc64

It built, after removing -fstack-protector-all that is not available for that target and suppressing the libelf-dev tests.

Transferred a perf.data file created in a i386 machine and… it fails. Endianness issues, I guess. Will fully investigate this in the next days.

About these ads
Post a comment or leave a trackback: Trackback URL.

Comments

  • fweisbec  On January 8, 2010 at 8:28 pm

    Ah! Yeah that reminds me we need to add an endianness field in the headers, so
    that we can cross-handle the bitmap of features correctly.

    I’ll send a patchlet for that soon.

    • acmel  On January 9, 2010 at 10:29 am

      An endianness field, yes, so that we can record at native endianness, i.e. at full speed, and only when decoding perform conversion.

      I’ll take a look at exactly how is it that ELF handles this, trying to use some solution that was validated in some other domain already.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: