Skip to content

[MIPS] Add Scheduling model for MIPS i6400 and i6500 CPUs #132704

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

Merged
merged 5 commits into from
Apr 29, 2025

Conversation

mgoudar
Copy link
Contributor

@mgoudar mgoudar commented Mar 24, 2025

Add scheduling model for the MIPS i6400 and i6500, an in-order MIPS64R6 processor.

i6400 and i6500 share same instruction latencies.

CPU has following pipelines

  • Two ALUs
  • Multiply and Divide unit (MDU)
  • Branch Unit (CTU)
  • Load/Store Unit (LSU)
  • Short Floating-point Unit and
  • Long Floating-point Unit

Latency information is available at: https://mips.com/wp-content/uploads/2025/03/MIPS_I6500-F_Data_Sheet_Rev1.10_3-17-2025.pdf

@djtodoro djtodoro self-requested a review March 24, 2025 10:16
@djtodoro
Copy link
Collaborator

Thanks for working on this! Can you please share a document that shows the instruction latencies?

@djtodoro djtodoro requested a review from mshockwave March 24, 2025 10:20

// LSU pipelines
// =============
def : InstRW<[I6400WriteLSUStore], (instrs SB, SD, SH, SW, SDC1, SDC164, SWC1, SWC2_R6,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible avoid using SchedWriteRes + InstRW and using the normal SchedWrite + WriteRes instead?

InstRW really should be used for "ad-hoc fixing" nowadays (e.g. instruction A & B share the same scheduling class in their instruction definitions, but they should be in two different scheduling classes in your core)

@mgoudar
Copy link
Contributor Author

mgoudar commented Mar 25, 2025

Thanks for working on this! Can you please share a document that shows the instruction latencies?

Hi, please find the instruction latency at public document: https://mips.com/wp-content/uploads/2025/03/MIPS_I6500-F_Data_Sheet_Rev1.10_3-17-2025.pdf

@mgoudar mgoudar requested a review from mshockwave March 26, 2025 07:25
@mgoudar mgoudar force-pushed the pr/add-mips-i6500-sched-model branch from d22c99a to e1a086e Compare March 26, 2025 09:41
@mgoudar mgoudar requested a review from mshockwave March 27, 2025 07:23
mul $3, $2, $3
sw $3, 8($sp)
div $2, $1
sw $2, 0($sp)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you add more tests on simple integer and floating point arithmetics instructions, as well as some vector instructions (they're called MSA?).

Copy link
Contributor Author

@mgoudar mgoudar Mar 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes. I will add. thank you for the review

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have extended the existing test to cover more instructions.

mgoudar added 3 commits March 31, 2025 14:51
Add scheduling model for the MIPS i6400 and i6500, an in-order
MIPS64R6 processor.

i6400 and i6500 share same instruction latencies.

CPU has following pipelines
  - Two ALUs
  - Multiply and Divide unit (MDU)
  - Branch Unit (CTU)
  - Load/Store Unit (LSU)
  - Short Floating-point Unit and
  - Long Floating-point Unit
i6400 and i6500 are in-order cores. hence set BufferSize
and MicroBufferSize to 0
- remove hasNoSchedulingInfo in Mips32r6InstrInfo.td
- define BufferSize to 0 for all resources
- remove timeline test in llvm-mca testcase
@mgoudar mgoudar force-pushed the pr/add-mips-i6500-sched-model branch from b9b1cf4 to 6784668 Compare March 31, 2025 09:22
Extend i64..s to cover more instructions including MSA
@mgoudar mgoudar requested a review from mshockwave April 4, 2025 09:54
@@ -0,0 +1,133 @@
# NOTE: Assertions have been autogenerated by utils/update_mca_test_checks.py
# RUN: llvm-mca -mtriple=mips64el -mcpu=i6400 --mattr=msa -timeline -iterations=1 < %s | FileCheck %s
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

when I suggested to remove -timeline for scheduling model test, I meant remove this flag from the RUN line and run update_mca_test_checks.py again to update the test (rather than manually remove the related CHECKs)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you for pointing me the process. I have now removed --timeline option and rerun with update_mca_test_checks.py

@@ -0,0 +1,133 @@
# NOTE: Assertions have been autogenerated by utils/update_mca_test_checks.py
# RUN: llvm-mca -mtriple=mips64el -mcpu=i6400 --mattr=msa -timeline -iterations=1 < %s | FileCheck %s
Copy link
Member

@mshockwave mshockwave Apr 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just checked the processor definitions: please correct me if I'm wrong, but it seems like none of the in-tree MIPS processors support MSA, then why did you want to assign meaningful latency/occupancy to those instructions?

Copy link
Contributor Author

@mgoudar mgoudar Apr 9, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i6400 and i6500 comes with MSA implemented and enabled by default, user can disable MSA with reset bit from the software. I think I need to enable FeatureMSA as part of i6400/i6500 cpu definition. I have created a separate PR: #134985

removed --timeline option from the RUN command
@mgoudar mgoudar requested a review from mshockwave April 9, 2025 05:58
Copy link
Member

@mshockwave mshockwave left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Personally I'm not really a fan of using InstRW as I pointed out in one of my comments. But I guess it's up to MIPS maintainers to make the call on that. Other than that, LGTM.
@djtodoro do you have any other comments?

Copy link
Collaborator

@djtodoro djtodoro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets try to avoid InstRW.

@mgoudar
Copy link
Contributor Author

mgoudar commented Apr 28, 2025

Lets try to avoid InstRW.

Hi, thank you for the review and the feedback. We have started porting work. We will port all existing scheduling model for MIPS cpus to new scheduling API soon.

@djtodoro
Copy link
Collaborator

OK, it can be addressed as a separate PR, but please handle all MIPS CPUs that use InstRW. Thanks!

@mgoudar
Copy link
Contributor Author

mgoudar commented Apr 29, 2025

OK, it can be addressed as a separate PR, but please handle all MIPS CPUs that use InstRW. Thanks!

yes sure. thank you.

@brad0 brad0 merged commit ffcca51 into llvm:main Apr 29, 2025
11 checks passed
@llvm-ci
Copy link
Collaborator

llvm-ci commented Apr 29, 2025

LLVM Buildbot has detected a new failure on builder llvm-clang-x86_64-sie-ubuntu-fast running on sie-linux-worker while building llvm at step 6 "test-build-unified-tree-check-all".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/144/builds/23854

Here is the relevant piece of the build log for the reference
Step 6 (test-build-unified-tree-check-all) failure: test (failure)
******************** TEST 'LLVM :: tools/llvm-mca/Mips/i6400.s' FAILED ********************
Exit Code: 2

Command Output (stderr):
--
/home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/build/bin/llvm-mca -mtriple=mips64el -mcpu=i6400 --mattr=msa -iterations=1 < /home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/llvm-project/llvm/test/tools/llvm-mca/Mips/i6400.s | /home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/build/bin/FileCheck /home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/llvm-project/llvm/test/tools/llvm-mca/Mips/i6400.s # RUN: at line 2
+ /home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/build/bin/llvm-mca -mtriple=mips64el -mcpu=i6400 --mattr=msa -iterations=1
+ /home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/build/bin/FileCheck /home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/llvm-project/llvm/test/tools/llvm-mca/Mips/i6400.s
/home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/build/bin/llvm-mca: unable to get target for 'mips64el', see --version and --triple.FileCheck error: '<stdin>' is empty.
FileCheck command line:  /home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/build/bin/FileCheck /home/buildbot/buildbot-root/llvm-clang-x86_64-sie-ubuntu-fast/llvm-project/llvm/test/tools/llvm-mca/Mips/i6400.s

--

********************


@llvm-ci
Copy link
Collaborator

llvm-ci commented Apr 29, 2025

LLVM Buildbot has detected a new failure on builder llvm-nvptx-nvidia-win running on as-builder-8 while building llvm at step 7 "test-build-unified-tree-check-llvm".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/54/builds/8671

Here is the relevant piece of the build log for the reference
Step 7 (test-build-unified-tree-check-llvm) failure: test (failure)
******************** TEST 'LLVM :: tools/llvm-mca/Mips/i6400.s' FAILED ********************
Exit Code: 2

Command Output (stdout):
--
# RUN: at line 2
c:\buildbot\as-builder-8\llvm-nvptx-nvidia-win\build\bin\llvm-mca.exe -mtriple=mips64el -mcpu=i6400 --mattr=msa -iterations=1 < C:\buildbot\as-builder-8\llvm-nvptx-nvidia-win\llvm-project\llvm\test\tools\llvm-mca\Mips\i6400.s | c:\buildbot\as-builder-8\llvm-nvptx-nvidia-win\build\bin\filecheck.exe C:\buildbot\as-builder-8\llvm-nvptx-nvidia-win\llvm-project\llvm\test\tools\llvm-mca\Mips\i6400.s
# executed command: 'c:\buildbot\as-builder-8\llvm-nvptx-nvidia-win\build\bin\llvm-mca.exe' -mtriple=mips64el -mcpu=i6400 --mattr=msa -iterations=1
# .---command stderr------------
# | c:\buildbot\as-builder-8\llvm-nvptx-nvidia-win\build\bin\llvm-mca.exe: unable to get target for 'mips64el', see --version and --triple.
# `-----------------------------
# error: command failed with exit status: 1
# executed command: 'c:\buildbot\as-builder-8\llvm-nvptx-nvidia-win\build\bin\filecheck.exe' 'C:\buildbot\as-builder-8\llvm-nvptx-nvidia-win\llvm-project\llvm\test\tools\llvm-mca\Mips\i6400.s'
# .---command stderr------------
# | FileCheck error: '<stdin>' is empty.
# | FileCheck command line:  c:\buildbot\as-builder-8\llvm-nvptx-nvidia-win\build\bin\filecheck.exe C:\buildbot\as-builder-8\llvm-nvptx-nvidia-win\llvm-project\llvm\test\tools\llvm-mca\Mips\i6400.s
# `-----------------------------
# error: command failed with exit status: 2

--

********************


brad0 added a commit to brad0/llvm-project that referenced this pull request Apr 29, 2025
brad0 added a commit that referenced this pull request Apr 29, 2025
gizmondo pushed a commit to gizmondo/llvm-project that referenced this pull request Apr 29, 2025
Add scheduling model for the MIPS i6400 and i6500, an in-order MIPS64R6
processor.

i6400 and i6500 share same instruction latencies.

CPU has following pipelines
  - Two ALUs
  - Multiply and Divide unit (MDU)
  - Branch Unit (CTU)
  - Load/Store Unit (LSU)
  - Short Floating-point Unit and
  - Long Floating-point Unit
 
Latency information is available at:
https://mips.com/wp-content/uploads/2025/03/MIPS_I6500-F_Data_Sheet_Rev1.10_3-17-2025.pdf
gizmondo pushed a commit to gizmondo/llvm-project that referenced this pull request Apr 29, 2025
@mshockwave
Copy link
Member

LLVM Buildbot has detected a new failure on builder llvm-nvptx-nvidia-win running on as-builder-8 while building llvm at step 7 "test-build-unified-tree-check-llvm".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/54/builds/8671

Here is the relevant piece of the build log for the reference

You forgot to add lit.local.cfg like this: https://github.com/llvm/llvm-project/blob/main/llvm/test/tools/llvm-mca/RISCV/lit.local.cfg
Which limits the tests to LLVM that has the MIPS backend (or you can add REQUIRES: mips-registered-target to every single tests under the Mips folder, but usually people prefer lit.local.cfg)

@mgoudar
Copy link
Contributor Author

mgoudar commented Apr 30, 2025

LLVM Buildbot has detected a new failure on builder llvm-nvptx-nvidia-win running on as-builder-8 while building llvm at step 7 "test-build-unified-tree-check-llvm".
Full details are available at: https://lab.llvm.org/buildbot/#/builders/54/builds/8671
Here is the relevant piece of the build log for the reference

You forgot to add lit.local.cfg like this: https://github.com/llvm/llvm-project/blob/main/llvm/test/tools/llvm-mca/RISCV/lit.local.cfg Which limits the tests to LLVM that has the MIPS backend (or you can add REQUIRES: mips-registered-target to every single tests under the Mips folder, but usually people prefer lit.local.cfg)

Thank you. I will add lit.local.cfg and create new pr. thanks for your feedback.

mgoudar added a commit to mgoudar/llvm-project that referenced this pull request Apr 30, 2025
…2704)

Relands llvm#132704 with a fix in the testcase:
Add llvm/test/tools/llvm-mca/Mips/lit.local.cfg

Add scheduling model for the MIPS i6400 and i6500, an in-order MIPS64R6
processor.

i6400 and i6500 share same instruction latencies.

CPU has following pipelines
  - Two ALUs
  - Multiply and Divide unit (MDU)
  - Branch Unit (CTU)
  - Load/Store Unit (LSU)
  - Short Floating-point Unit and
  - Long Floating-point Unit

Latency information is available at:
https://mips.com/wp-content/uploads/2025/03/MIPS_I6500-F_Data_Sheet_Rev1.10_3-17-2025.pdf
brad0 pushed a commit that referenced this pull request May 4, 2025
#137984)

Relands #132704 with a fix in the testcase:
Add llvm/test/tools/llvm-mca/Mips/lit.local.cfg

Add scheduling model for the MIPS i6400 and i6500, an in-order MIPS64R6
processor.

i6400 and i6500 share same instruction latencies.

CPU has following pipelines
  - Two ALUs
  - Multiply and Divide unit (MDU)
  - Branch Unit (CTU)
  - Load/Store Unit (LSU)
  - Short Floating-point Unit and
  - Long Floating-point Unit

Latency information is available at:

https://mips.com/wp-content/uploads/2025/03/MIPS_I6500-F_Data_Sheet_Rev1.10_3-17-2025.pdf
@llvm-ci
Copy link
Collaborator

llvm-ci commented May 6, 2025

LLVM Buildbot has detected a new failure on builder llvm-nvptx-nvidia-ubuntu running on as-builder-7 while building llvm at step 6 "test-build-unified-tree-check-llvm".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/180/builds/17043

Here is the relevant piece of the build log for the reference
Step 6 (test-build-unified-tree-check-llvm) failure: test (failure)
******************** TEST 'LLVM :: tools/llvm-mca/Mips/i6400.s' FAILED ********************
Exit Code: 2

Command Output (stderr):
--
/home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/build/bin/llvm-mca -mtriple=mips64el -mcpu=i6400 --mattr=msa -iterations=1 < /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/llvm-project/llvm/test/tools/llvm-mca/Mips/i6400.s | /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/build/bin/FileCheck /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/llvm-project/llvm/test/tools/llvm-mca/Mips/i6400.s # RUN: at line 2
+ /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/build/bin/llvm-mca -mtriple=mips64el -mcpu=i6400 --mattr=msa -iterations=1
+ /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/build/bin/FileCheck /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/llvm-project/llvm/test/tools/llvm-mca/Mips/i6400.s
/home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/build/bin/llvm-mca: unable to get target for 'mips64el', see --version and --triple.FileCheck error: '<stdin>' is empty.
FileCheck command line:  /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/build/bin/FileCheck /home/buildbot/worker/as-builder-7/ramdisk/llvm-nvptx-nvidia-ubuntu/llvm-project/llvm/test/tools/llvm-mca/Mips/i6400.s

--

********************


IanWood1 pushed a commit to IanWood1/llvm-project that referenced this pull request May 6, 2025
Add scheduling model for the MIPS i6400 and i6500, an in-order MIPS64R6
processor.

i6400 and i6500 share same instruction latencies.

CPU has following pipelines
  - Two ALUs
  - Multiply and Divide unit (MDU)
  - Branch Unit (CTU)
  - Load/Store Unit (LSU)
  - Short Floating-point Unit and
  - Long Floating-point Unit
 
Latency information is available at:
https://mips.com/wp-content/uploads/2025/03/MIPS_I6500-F_Data_Sheet_Rev1.10_3-17-2025.pdf
IanWood1 pushed a commit to IanWood1/llvm-project that referenced this pull request May 6, 2025
IanWood1 pushed a commit to IanWood1/llvm-project that referenced this pull request May 6, 2025
…2704) (llvm#137984)

Relands llvm#132704 with a fix in the testcase:
Add llvm/test/tools/llvm-mca/Mips/lit.local.cfg

Add scheduling model for the MIPS i6400 and i6500, an in-order MIPS64R6
processor.

i6400 and i6500 share same instruction latencies.

CPU has following pipelines
  - Two ALUs
  - Multiply and Divide unit (MDU)
  - Branch Unit (CTU)
  - Load/Store Unit (LSU)
  - Short Floating-point Unit and
  - Long Floating-point Unit

Latency information is available at:

https://mips.com/wp-content/uploads/2025/03/MIPS_I6500-F_Data_Sheet_Rev1.10_3-17-2025.pdf
IanWood1 pushed a commit to IanWood1/llvm-project that referenced this pull request May 6, 2025
Add scheduling model for the MIPS i6400 and i6500, an in-order MIPS64R6
processor.

i6400 and i6500 share same instruction latencies.

CPU has following pipelines
  - Two ALUs
  - Multiply and Divide unit (MDU)
  - Branch Unit (CTU)
  - Load/Store Unit (LSU)
  - Short Floating-point Unit and
  - Long Floating-point Unit
 
Latency information is available at:
https://mips.com/wp-content/uploads/2025/03/MIPS_I6500-F_Data_Sheet_Rev1.10_3-17-2025.pdf
IanWood1 pushed a commit to IanWood1/llvm-project that referenced this pull request May 6, 2025
IanWood1 pushed a commit to IanWood1/llvm-project that referenced this pull request May 6, 2025
…2704) (llvm#137984)

Relands llvm#132704 with a fix in the testcase:
Add llvm/test/tools/llvm-mca/Mips/lit.local.cfg

Add scheduling model for the MIPS i6400 and i6500, an in-order MIPS64R6
processor.

i6400 and i6500 share same instruction latencies.

CPU has following pipelines
  - Two ALUs
  - Multiply and Divide unit (MDU)
  - Branch Unit (CTU)
  - Load/Store Unit (LSU)
  - Short Floating-point Unit and
  - Long Floating-point Unit

Latency information is available at:

https://mips.com/wp-content/uploads/2025/03/MIPS_I6500-F_Data_Sheet_Rev1.10_3-17-2025.pdf
IanWood1 pushed a commit to IanWood1/llvm-project that referenced this pull request May 6, 2025
Add scheduling model for the MIPS i6400 and i6500, an in-order MIPS64R6
processor.

i6400 and i6500 share same instruction latencies.

CPU has following pipelines
  - Two ALUs
  - Multiply and Divide unit (MDU)
  - Branch Unit (CTU)
  - Load/Store Unit (LSU)
  - Short Floating-point Unit and
  - Long Floating-point Unit
 
Latency information is available at:
https://mips.com/wp-content/uploads/2025/03/MIPS_I6500-F_Data_Sheet_Rev1.10_3-17-2025.pdf
IanWood1 pushed a commit to IanWood1/llvm-project that referenced this pull request May 6, 2025
IanWood1 pushed a commit to IanWood1/llvm-project that referenced this pull request May 6, 2025
…2704) (llvm#137984)

Relands llvm#132704 with a fix in the testcase:
Add llvm/test/tools/llvm-mca/Mips/lit.local.cfg

Add scheduling model for the MIPS i6400 and i6500, an in-order MIPS64R6
processor.

i6400 and i6500 share same instruction latencies.

CPU has following pipelines
  - Two ALUs
  - Multiply and Divide unit (MDU)
  - Branch Unit (CTU)
  - Load/Store Unit (LSU)
  - Short Floating-point Unit and
  - Long Floating-point Unit

Latency information is available at:

https://mips.com/wp-content/uploads/2025/03/MIPS_I6500-F_Data_Sheet_Rev1.10_3-17-2025.pdf
GeorgeARM pushed a commit to GeorgeARM/llvm-project that referenced this pull request May 7, 2025
Add scheduling model for the MIPS i6400 and i6500, an in-order MIPS64R6
processor.

i6400 and i6500 share same instruction latencies.

CPU has following pipelines
  - Two ALUs
  - Multiply and Divide unit (MDU)
  - Branch Unit (CTU)
  - Load/Store Unit (LSU)
  - Short Floating-point Unit and
  - Long Floating-point Unit
 
Latency information is available at:
https://mips.com/wp-content/uploads/2025/03/MIPS_I6500-F_Data_Sheet_Rev1.10_3-17-2025.pdf
GeorgeARM pushed a commit to GeorgeARM/llvm-project that referenced this pull request May 7, 2025
GeorgeARM pushed a commit to GeorgeARM/llvm-project that referenced this pull request May 7, 2025
…2704) (llvm#137984)

Relands llvm#132704 with a fix in the testcase:
Add llvm/test/tools/llvm-mca/Mips/lit.local.cfg

Add scheduling model for the MIPS i6400 and i6500, an in-order MIPS64R6
processor.

i6400 and i6500 share same instruction latencies.

CPU has following pipelines
  - Two ALUs
  - Multiply and Divide unit (MDU)
  - Branch Unit (CTU)
  - Load/Store Unit (LSU)
  - Short Floating-point Unit and
  - Long Floating-point Unit

Latency information is available at:

https://mips.com/wp-content/uploads/2025/03/MIPS_I6500-F_Data_Sheet_Rev1.10_3-17-2025.pdf
Ankur-0429 pushed a commit to Ankur-0429/llvm-project that referenced this pull request May 9, 2025
Add scheduling model for the MIPS i6400 and i6500, an in-order MIPS64R6
processor.

i6400 and i6500 share same instruction latencies.

CPU has following pipelines
  - Two ALUs
  - Multiply and Divide unit (MDU)
  - Branch Unit (CTU)
  - Load/Store Unit (LSU)
  - Short Floating-point Unit and
  - Long Floating-point Unit
 
Latency information is available at:
https://mips.com/wp-content/uploads/2025/03/MIPS_I6500-F_Data_Sheet_Rev1.10_3-17-2025.pdf
Ankur-0429 pushed a commit to Ankur-0429/llvm-project that referenced this pull request May 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants