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

Issues and enhancement suggestions #2

Open
thorax58 opened this issue Jan 28, 2025 · 4 comments
Open

Issues and enhancement suggestions #2

thorax58 opened this issue Jan 28, 2025 · 4 comments

Comments

@thorax58
Copy link

Love the application. Here are some issues/suggestion for you to consider:

  1. Suggestion: Would be nice to copy text from the intrinsic display. For example if I search and expand the entry for __mm512_multishift_epi64_epi8 I'd like to be able to copy, for example, the perf information or the instruction name. However, the click is used to expand/collapse the entry so can't be used for copying text.
  2. Issue: Searching by instruction doesn't work for me. If I enter "vperm" or "vpmulti", for example, I get a blank screen.
  3. Issue: I have a firewall issue so I download the intrinsic/uops data the manually. I have to do this every time I go into the application as it won't use the existing data if the connect to download fails. Would be nice if after failing to connect it would just keep using the already local data.
  4. Issue: Some Description texts don't wrap and are displayed in a single line making the last half unreadable. For example the Description text for _mm256_maskz_gf2p8affineinv_epi64_epi8 doesn't wrap.
  5. Issue: The app losing focus causes the current open intrinsic to collapse/close. Would be nice to have the intrinsic visible while working in another window.
  6. Suggestion: Perform the search as each character is typed rather than wait for . (Similar to what Intel's Intrinsic Guide does.) Would also be nice to ignore leading/trailing whitespace for the search.

Thanks again for a great app. Apologies if you get this twice.

@Sibras
Copy link
Owner

Sibras commented Jan 31, 2025

  1. This is a limitiation of the UI library (Qt qml) which im not sure how to workaround it. There is a workaround inplace though that allows for copying the intrinsic name and header from the synopsis section (you should see the mouse cursor change when hovering over these items. I havnt yet worked out how to do it for the whole expandable section though.
  2. Ill look into adding this
  3. The program should create a file called 'dataCache' next to the executable that contains the cached contents of the download files. It should only try and redownload the source file if this cache file is missing or out of date. Check that this file is being created, it might be a write permission issue that is causing the file not to be saved between runs
  4. Ill fix that
  5. Just tested that and couldnt reproduce it. I tried changing windows, alt+tabbing out and the intrinsic stayed open. Any suggestion to reproduce?
  6. This is actually a performance consideration as having it auto search on type was causing serious perforamnce issues due to the UI library being slower than expected. Ive since tried to workaround some perf issues to speed things up so Ill reevaluate whether auto search is feasible now

@thorax58
Copy link
Author

thorax58 commented Feb 1, 2025 via email

@Sibras
Copy link
Owner

Sibras commented Feb 2, 2025

Ive added some commits that address some of the issues that you mention
Current status:

  • (1) Ive added user selectable text into the expanded intrinsic area for the intruction (below the exiting selectable intrinsic/header)
  • (2) WIP
  • (3) Fixed this, it was a version issue with the upstream intel source being rather old
  • (4) Should be fixed as ive added improved resizing both horizonatally and vertically
  • (5) Ive added state to remember the 'expanded' state of each intrinsic which should fix it getting reset to collapsed
  • (6) WIP

@thorax58
Copy link
Author

thorax58 commented Feb 2, 2025 via email

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

No branches or pull requests

2 participants