Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support multiple global registers #6096

Open
fuzyll opened this issue Nov 6, 2024 · 2 comments
Open

Support multiple global registers #6096

fuzyll opened this issue Nov 6, 2024 · 2 comments
Labels
Component: Core Issue needs changes to the core Effort: Medium Issue should take < 1 month Impact: Medium Issue is impactful with a bad, or no, workaround Type: Enhancement Issue is a small enhancement to existing functionality

Comments

@fuzyll
Copy link
Contributor

fuzyll commented Nov 6, 2024

What is the feature you'd like to have?
Issue #3223 was fixed and is awesome. Unfortunately, we currently only support a single global register value. It would be awesome if we could support multiple.

Is your feature request related to a problem?
Sometimes, you just have more than one, y'know?

Are any alternative solutions acceptable?
None that I can think of.

Additional Information:
You can hack around this with UIDF already, but it's less-than-ideal.

@emesare
Copy link
Member

emesare commented Nov 6, 2024

An example of an architecture that would benefit from this is tricore.

2.2.1.4 System Global Registers
Address registers A[0], A[1], A[8], and A[9] are designated as system global registers.
They are not part of either context partition and are not saved/restored across calls. They
can be protected against write access by user applications.

https://www.infineon.com/dgdl/TriCore_EABI_v2_3.pdf?fileId=db3a304412b407950112b40f8d7a142b

@alexmullins
Copy link
Contributor

PowerPC is another arch that would benefit from this. The EABI specifies R2 and R13 be used as global pointers to data sections.

https://www.nxp.com/docs/en/application-note/PPCEABI.pdf

@xusheng6 xusheng6 added Type: Enhancement Issue is a small enhancement to existing functionality Component: Core Issue needs changes to the core Effort: Medium Issue should take < 1 month Impact: Medium Issue is impactful with a bad, or no, workaround labels Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Core Issue needs changes to the core Effort: Medium Issue should take < 1 month Impact: Medium Issue is impactful with a bad, or no, workaround Type: Enhancement Issue is a small enhancement to existing functionality
Projects
None yet
Development

No branches or pull requests

4 participants