Skip to content

[M68k] Add floating point support #61744

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

Open
mshockwave opened this issue Mar 28, 2023 · 8 comments
Open

[M68k] Add floating point support #61744

mshockwave opened this issue Mar 28, 2023 · 8 comments
Labels

Comments

@mshockwave
Copy link
Member

mshockwave commented Mar 28, 2023

Add supports for floating pointer registers, basic instructions and inline assembly.

Foundation

Basic instruction definitions

Instruction definitions and MC supports for common FP instructions, for instance:

Advanced instruction supports

@llvmbot
Copy link
Member

llvmbot commented Mar 28, 2023

@llvm/issue-subscribers-backend-m68k

@0x59616e
Copy link
Contributor

Hello @mshockwave ,

May I inquire if we have any plans or milestones established? Additionally, is there a corresponding to-do list for said milestones?

@RKSimon RKSimon removed the new issue label Mar 28, 2023
@mshockwave
Copy link
Member Author

Hello @mshockwave ,

May I inquire if we have any plans or milestones established? Additionally, is there a corresponding to-do list for said milestones?

Yeah I will put more detailed milestones for this. In the short term, we have to pass llvm-test-suite, which relies on inline assembly with floating point constructions. For instance:

__asm__ volatile ("fmove%.l %0, %!" : : "dm" (cw))

So for that, we at least need floating pointer register definitions and MC supports for commonly-used floating point instructions.

@mshockwave
Copy link
Member Author

UPDATE: just updated the description to add (preliminary) roadmap for this task.

@0x59616e
Copy link
Contributor

It appears that this is a large-scale project. I'm wondering if it's possible to divide these tasks and list them in a table format ? This could help us keep track of which items are currently under development and avoid any potential duplication of effort.

Something like this:

item picker
register support aaa
instruction mc support bbb
inline support ccc

@mshockwave
Copy link
Member Author

It appears that this is a large-scale project. I'm wondering if it's possible to divide these tasks and list them in a table format ? This could help us keep track of which items are currently under development and avoid any potential duplication of effort.

Something like this:

item picker
register support aaa
instruction mc support bbb
inline support ccc

Yes I agree. I've created issues for these tasks. Please put yourself as assignee if you want to work on that.

@0x59616e
Copy link
Contributor

Thanks ! Looks like we have so much fun to do.

@glaubitz
Copy link
Contributor

Any news on the M68k backend?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants