Skip to content

Commit d4891c5

Browse files
authored
update optimuzz-llm post
1 parent 7711ae5 commit d4891c5

File tree

1 file changed

+2
-1
lines changed
  • content/posts/optimuzz-meets-llm

1 file changed

+2
-1
lines changed

content/posts/optimuzz-meets-llm/index.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,8 @@ Which target line should Optimuzz aim at? Provide your best suggestion of the ta
5656
The LLM answered with the target line 2026, where the optimized instruction is returned for the update optimization condition.
5757
From this, we confirmed that the LLM can effectively identify the target line of the optimization update.
5858
Note that the example above is a summary from the commit message and code changes from the LLVM commit: https://github.com/llvm/llvm-project/commit/1f69d6354a4b088bda5ee62c31411a75eead8b0c.
59-
The script that construct a prompt can be found at https://github.com/prosyslab/optimuzz/blob/master/tools/targetline.py.
59+
The script that construct a prompt can be found at https://github.com/prosyslab/optimuzz/blob/master/tools/targetline.py, and
60+
the example prompt with its expected output can be found at https://github.com/prosyslab/optimuzz/blob/master/tools/targetline.expected .
6061

6162
As a result, we have successfully integrated LLMs into our workflow.
6263
Every time there is an update on an optimization in LLVM, we automatically fetch the commit information using the GitHub API.

0 commit comments

Comments
 (0)