Optimize bionic by using the restrict keyword where possible

Registered by Bernhard Rosenkraenzer on 2012-10-03

Why?
If the compiler knows a pointer will only be referenced through itself, it can optimize more efficiently.
Doing this for basic functionality like Bionic's is likely to result in a faster and smaller build.

Context?
Part of general platform optimization work

What gets produced?
Patches to Bionic that make it use the restrict keyword where possible

Where will the work get put?
android-build.linaro.org and AOSP

Blueprint information

Status:
Not started
Approver:
Zach Pfeffer
Priority:
Undefined
Drafter:
Bernhard Rosenkraenzer
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
Accepted for future
Implementation:
Not started
Milestone target:
milestone icon backlog

Related branches

Sprints

Whiteboard

Notes:
[2012/10/3 berolinux] Put notes here.

Meta:
Roadmap id: PLATFORM-WORK
Headline: Bionic has been updated to use the restrict keyword, allowing more optimizations
Acceptance: Bionic in linaro_android_4.1.1 has been patched to use the restrict keyword where possible, and the patch has been submitted to AOSP.

(?)

Work Items

Work items:
Check where restrict can be used [glibc has been using it for quite some time, so simply checking where glibc uses restrict should be fine]: TODO
Add it in Bionic: TODO
Run a test build: TODO
Verify everything still works, fix issues if any: TODO
Submit patch to AOSP: TODO

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.