llnl / llnl/CompilerGPT

Ablation study: What if the LLM is asked to optimize the code without seeing the optimization report?

Open
#18 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
19
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Comparing the necessity of knowing the optimization reports

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.

Research direction

No files, tests, or entry points are named. Start by locating the optimization-report input path and the code-optimization experiment, then compare runs where the LLM receives reports with runs where it does not. Done means the ablation results are recorded.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
ai, compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.