Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Effect of small data areas (SDA)
20 views
Skip to first unread message
Jens Schweikhardt
Jan 30, 2013, 11:21:24 AM1/30/13
to
hello, world\n
I'm looking at IBM's "Developing PowerPC Embedded Application Binary
(EABI) Compliant Programs",
https://www-01.ibm.com/chips/techlib/techlib.nsf/techdocs/852569B20050FF77852569970071B0D6/$file/eabi_app.pdf
in particular at table 4 on page 7. The benchmark results are 88kDhry/
sec without using SDA, and only 77kDhry/sec *with* SDA. I would have
expected using SDA not only reduce code size but also improve
performance because access to variables only needs two instead of
three instructions. Can somebody explain the numbers in the table?
What am I missing?
Regards,
Jens
I'm looking at IBM's "Developing PowerPC Embedded Application Binary
(EABI) Compliant Programs",
https://www-01.ibm.com/chips/techlib/techlib.nsf/techdocs/852569B20050FF77852569970071B0D6/$file/eabi_app.pdf
in particular at table 4 on page 7. The benchmark results are 88kDhry/
sec without using SDA, and only 77kDhry/sec *with* SDA. I would have
expected using SDA not only reduce code size but also improve
performance because access to variables only needs two instead of
three instructions. Can somebody explain the numbers in the table?
What am I missing?
Regards,
Jens
0 new messages