Lower target layout intrinsics in the Whale adapter

Abierto
  • ¿Algo no está bien?
#1,034 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
rust
Área
compilers

Línea de trabajo

Start by reading whale/src/codegen/expression.rs:23 and the existing layout intrinsic entry points referenced in the issue. Before implementing, discuss the target size/alignment contract with @LunaStev, since the issue explicitly leaves its authoritative source unresolved. Run the compiler’s size_of capability probe and inspect layout lowering; done means supported scalar, alias, and aggregate layouts match the selected Wave target contract, size_of and align_of share those facts, and missing facts produce clear errors with output preserved.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

discussion enhancement help wanted

Motivation

A std::mem::layout size_of() call succeeds through LLVM but Whale treats __wave_size_of as an unsupported intrinsic/external call. align_of belongs to the same target-layout contract.

Starting point: whale/src/codegen/expression.rs:23.

Validation

Audited canonical Wave 540728c2eb6cc12f5c69c3fb3fdb96e07ba059a4 (0.0.1-alpha-dev), whose tree matches the local checkout. Validation: Executed size_of capability probe and inspected existing layout intrinsic entry points. Executed compiler probes use the matching checkout-built compiler and std on Linux amd64 (Rust 1.89.0 / LLVM 21.1.8). Source/header or mocked checks are not native execution on another OS.

Scope

Agree how authoritative target size/alignment facts reach the adapter, then lower the supported intrinsic subset. Host Rust size_of and backend guesses must not define Wave layout.

Related: #996, #881. These links do not claim those broader or completed scopes are unfinished.

Design discussion required

This issue records a proposal or an unresolved contract; it is not approval to choose new semantics. Please mention @LunaStev to discuss the design before starting implementation.

Completion criteria

  • Supported scalar/alias/aggregate layouts match the selected Wave target contract.
  • size_of and align_of use the same authoritative facts.
  • Missing or unsupported layout facts are clear source/internal errors as appropriate, with output preservation.
Lenguaje dominante
Rust
Estrellas
56
Forks
21
Merge medio
23 h 20 min
PR fusionados (30 d)
45

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de wavefnd/Wave

Todos los issues de wavefnd/Wave

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.