KhronosGroup / KhronosGroup/OpenCL-Headers

Problem with x264 OpenCL

Open
#258 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
766
Forks
273
Avg merge
2d 2h
Merged PRs (30d)
3

Description

I use https://github.com/KhronosGroup/OpenCL-Headers/commit/c860bb551eeef9a47d56286a70cea903db3d6ed2
I has info codec x264:
```[libx264 @ 000001ad8d0d3b10] using SAR=1/1
[libx264 @ 000001ad8d0d3b10] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
[libx264 @ 000001ad8d0d3b10] OpenCL acceleration enabled with NVIDIA Corporation NVIDIA GeForce RTX 3050
[libx264 @ 000001ad8d0d3b10] Compiling OpenCL kernels...
[libx264 @ 000001ad8d0d3b10] profile High, level 4.0, 4:2:0, 8-bit
[libx264 @ 000001ad8d0d3b10] 264 - core 164 r3191M 4613ac3 - H.264/MPEG-4 AVC codec - Copyleft 2003-2022 - http://www.videolan.org/x264.html -
options: opencl=1 cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=4 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=abr mbtree=1 bitrate=3000 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00```

When do I use https://github.com/KhronosGroup/OpenCL-Headers/commit/d79beab14769efdff4ff9106cdc47268575d6891 then I have error.

_OpenCL: kernel build errors written to x264_kernel_build_log.txt_

_error : Binary format for key='0', ident='' is not recognized_

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by comparing the OpenCL-Headers commits c860bb551eeef9a47d56286a70cea903db3d6ed2 and d79beab14769efdff4ff9106cdc47268575d6891. Reproduce the x264 OpenCL kernel build with each revision and inspect the referenced x264_kernel_build_log.txt. Done means identifying whether the header change causes the reported build error and documenting or correcting the compatibility issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.