libretro / libretro/opera-libretro

investigate improving hotspots

Open
#71 0 comments 0 reactions 1 assignee View on GitHub

@trapexit is already working on this.

Since May 2, 2018.

enhancement
Dominant language
C
Stars
86
Forks
50
Avg merge
7h 10m
Merged PRs (30d)
1

Description

(captured by building with DEBUG = 1 and adding -fno-omit-frame-pointer, let Road Rash run for > 10m)

According to perf some top hotspots are (cycles:P (self)):

  1. _arm_Execute
  2. freedo_dsp_loop
  3. dsp_operand_load
  4. TexelDraw_Arbitrary
  5. PPROC
  6. freedo_quarz_push_cycles
  7. freedo_frame_get_bitmap_xrgb_8888
  8. BitReaderBig_Read
  9. _mem_read32
  10. _3do_Frame

image

Build with -O3 and -flto (link time optimizations)

Interesting to see retro_run with such a high percentage.
image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.