codegen: an `array[N] ptr array[M] T` argument is declared as `T* a_p)[M]`
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 57/100
Direzione di ricerca
Read internal/cgen/expr.go around lines 611–620 and 649–678, where the issue identifies the type handling and declarator dimensions. Use the provided Wuffs repro to generate C, then check that the result is a valid declarator such as uint8_t (*a_p[2])[3] or that generation reports an error. Confirm the generated C compiles with a C compiler.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Hi,
General context of this work is in #188, including the AI-disclaimers.
No in-tree codec is affected by this issue; no std function has an argument that is an array of pointers to arrays. Claude judges the prospective risk of it as "low": the generated C does not compile, and the related nestings fail generation.
The following is Sol 6.1's writeup of the issue. Includes a repro, the generated declarator, compile errors from gcc 13.3, clang 18, MSVC and clang-cl 18, a control that compiles, and generation errors for two other nestings. The cause is reasoned from source.
For an array[2] ptr array[3] base.u8 argument, cgen emits uint8_t* a_p)[3], with an unmatched parenthesis and no outer array dimension. writeCTypeName strips the outer arrays before recognizing the pointer to an array, but writes the closing parenthesis and dimensions from the full type.
Minimal repro:
pub struct repro?(
buf : array[4] base.u8,
)
pub func repro.f!(p: array[2] ptr array[3] base.u8) {
args.p[0][1] = 7
}
Actual: at b36a81d3, wuffs-c gen -package_name repro arr_ptr_arr.wuffs exits 0 with empty stderr. The prototype is:
wuffs_repro__repro__f(
wuffs_repro__repro* self,
uint8_t* a_p)[3]);
Compiling the amalgamation with WUFFS_IMPLEMENTATION defined fails with gcc 13.3 (-std=c99 -c, exit 1), clang 18 (exit 1), MSVC (cl /c, exit 2) and clang-cl 18 (exit 1):
arr_ptr_arr-release.c:7939:1: error: ‘wuffs_repro__repro__f’ declared as function returning an array
arr_ptr_arr-release.c:7941:21: error: expected declaration specifiers before ‘)’ token
arr_ptr_arr-release.c:7941:21: error: expected function body after function declarator
arr_ptr_arr-release.c(7941): error C2059: syntax error: ')'
arr_ptr_arr-release.c(7939): error C2090: function returns array
arr_ptr_arr-release.c(7941,21): error: expected function body after function declarator
Control: a ptr array[3] base.u8 argument, without the outer array, is emitted as uint8_t* a_p and compiles. Two other nestings fail generation: ptr array[2] ptr base.u8 and ptr ptr array[3] base.u8 arguments produce cannot convert Wuffs type "ptr array[2] ptr base.u8" to C and cannot convert Wuffs type "ptr ptr array[3] base.u8" to C.
Expected: either a valid declarator for an array of pointers to arrays, such as uint8_t (*a_p[2])[3], or a generation error.
Cause: the outer arrays are stripped into x, and the pointer-to-array case is recognized on x:
The closing parenthesis and dimensions are then written from n, the full type. The outer array shifts what x.Inner().Inner() refers to:
- Lingua principale
- C
- Stelle
- 4.9k
- Fork
- 150
- Merge medio
- 4g 1h
- PR unite (30g)
- 3
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di google/wuffs
-
codegen: `io_reader.match7` with an empty prefix shifts a `uint64_t` by 64 and reports a mismatchAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 67/100
Tutte le issue di google/wuffs
Issue simili
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
containers/bubblewrap#826 ·
I maintainer di solito rispondono entro 1 giorno
-
Vulkan: create_device reads the device extension list after freeing it (random crash at start)Aperta
Difficoltà 1/5 1-3 ore Idoneità per principianti 62/100
Revivedx/SavageWindRecomp#488 ·
I maintainer di solito rispondono entro 1 giorno
-
needs-device
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
-
feature/themes QA/No release-notes/exclude tests tests/missing-coverage tests/test-quality
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
brave/brave-browser#60971 ·
I maintainer di solito rispondono entro 1 giorno