lapacke_cherfsx.c(3)

πŸ“¦ version 3.9.0, in centos-stream 9

πŸ’… lapacke_cherfsx.c

okay so real talk β€” this here is the manpage for lapacke_cherfsx.c, straight out of LAPACK's LAPACKE layer, and it's giving "the doc generator had one job and that job was typing the signature." No cap. But we're gonna walk through it together anyway because every single arg matters, bestie. 🫢


✨ NAME ✨

lapacke_cherfsx.c β€” that's it, that's the name. The page literally just names the source file. Iconic minimalism, honestly. πŸ’€


🌸 SYNOPSIS 🌸

First thing you gotta do, always, is pull in the utils header:

#include 'lapacke_utils.h'

πŸŽ€ Functions

Then we've got exactly one (1) function, and she is long. Behold:

lapack_int LAPACKE_cherfsx (int matrix_layout, char uplo, char equed,
    lapack_int n, lapack_int nrhs, const lapack_complex_float *a,
    lapack_int lda, const lapack_complex_float *af, lapack_int ldaf,
    const lapack_int *ipiv, const float *s, const lapack_complex_float
    *b, lapack_int ldb, lapack_complex_float *x, lapack_int ldx, float
    *rcond, float *berr, lapack_int n_err_bnds, float *err_bnds_norm,
    float *err_bnds_comp, lapack_int nparams, float *params)

Twenty-one parameters. Twenty-one!! She ate and left absolutely no crumbs. πŸ”₯


πŸ‘‘ Function Documentation πŸ‘‘

πŸ’œ lapack_int LAPACKE_cherfsx

Same function, same args, just with the spacing the doc generator felt like that day. Copying it faithfully because we do not edit signatures in this house:

lapack_int LAPACKE_cherfsx (int matrix_layout, char uplo, char equed,
    lapack_int n, lapack_int nrhs, const lapack_complex_float * a,
    lapack_int lda, const lapack_complex_float * af, lapack_int ldaf, const
    lapack_int * ipiv, const float * s, const lapack_complex_float * b,
    lapack_int ldb, lapack_complex_float * x, lapack_int ldx, float * rcond,
    float * berr, lapack_int n_err_bnds, float * err_bnds_norm, float *
    err_bnds_comp, lapack_int nparams, float * params)
⚠️ heads up bestie: this page gives you the signature and nothing else. No prose description of what each parameter does, no return-value rundown, no notes. So don't go assuming β€” go read the actual LAPACK docs if you need the semantics. I'm not out here inventing lore. πŸ™ˆ

Here's the full roll call of everything she takes, exactly as written, so you can vibe-check your call site:

  • int matrix_layout
  • char uplo
  • char equed
  • lapack_int n
  • lapack_int nrhs
  • const lapack_complex_float *a
  • lapack_int lda
  • const lapack_complex_float *af
  • lapack_int ldaf
  • const lapack_int *ipiv
  • const float *s
  • const lapack_complex_float *b
  • lapack_int ldb
  • lapack_complex_float *x
  • lapack_int ldx
  • float *rcond
  • float *berr
  • lapack_int n_err_bnds
  • float *err_bnds_norm
  • float *err_bnds_comp
  • lapack_int nparams
  • float *params

That's all twenty-one, accounted for, nobody left on read. πŸ’–

Definition at line 36 of file lapacke_cherfsx.c. (yes, line 36, go look, she's right there ✨)


πŸ¦‹ Author πŸ¦‹

Generated automatically by Doxygen for LAPACK from the source code. So nobody wrote this page, a robot did, and honestly the robot understood the assignment: signature, definition location, done. πŸ€–πŸ’…


and that's the whole page, bestie β€” Version 3.8.0, dated Tue Nov 14 2017, no cap, adapted from the LAPACK source code. now go compile something beautiful πŸŽ€πŸŒˆ

πŸ“¦ where this page comes from