Skip to content

Fix errors and typos in some docs#843

Merged
devinamatthews merged 13 commits intoflame:masterfrom
jip:fix
Jan 21, 2025
Merged

Fix errors and typos in some docs#843
devinamatthews merged 13 commits intoflame:masterfrom
jip:fix

Conversation

@jip
Copy link
Copy Markdown
Contributor

@jip jip commented Jan 20, 2025

Details:

  • fix errors and typos,
  • format according to coding style guide,
  • unify a bit the formatting and content in docs/BLIS*API.md,
  • sync the content in docs/BLIS*API.md with the current code base.

BTW, questions:

  • There is one discrepancy in function signatures: bli_?print[vm] use the type const void* for x parameter, but bli_?fprint[vm] use the type const ctype*. Is this made intentionally?
  • Why bli_rntm_print function is not exported?
  • A bli_info_get_enable_stay_auto_init function is declared, but not defined.

Note: this is a refreshed version of my PR #838 closed that differs as follows:

  • is rebased to the current master,
  • commits are reordered a bit.

jip added 12 commits January 20, 2025 18:52
1. Some integer-based types were missed.
2. Some function parameters were missed.

Changes to be committed:
	modified:   docs/BLISObjectAPI.md
	modified:   docs/BLISTypedAPI.md
Remove comma after last function parameter.
1) Function signature must be terminated by a semicolon.
2) Condense short code to single lines.

Changes to be committed:
	modified:   docs/BLISObjectAPI.md
	modified:   docs/BLISTypedAPI.md
	modified:   docs/KernelsHowTo.md
Remove trailing whiespaces.

Changes to be committed:
	modified:   docs/KernelsHowTo.md
	modified:   docs/Performance.md
Make indents of proper size for parentheses and function arguments.
Sync docs with 31c8657 commit.

Changes to be committed:
	modified:   docs/BLISObjectAPI.md
	modified:   docs/BLISTypedAPI.md
Highlight syntax as for C source, not as for a shell script.

Changes to be committed:
	modified:   docs/BLISObjectAPI.md
	modified:   docs/ReleaseNotes.md
Make their content more similar to each other.

Changes to be committed:
	modified:   docs/BLISObjectAPI.md
	modified:   docs/BLISTypedAPI.md
Mention new global scalar constants: BLIS_ONE_I, BLIS_MINUS_ONE_I, BLIS_NAN.
Use 'const' pointers.

Changes to be committed:
	modified:   docs/BLISObjectAPI.md
	modified:   docs/BLISTypedAPI.md
Recreate omitting fragments.
@devinamatthews
Copy link
Copy Markdown
Member

@jip thanks for rebasing. I'll check over the PR shortly. As for the questions:

  • bli_rntm_print is an internal debugging function. You'll note it's not actually used in the framework either (calls are commented out).
  • void* in ?print[vm] is an oversight, and should really be ctype*. If you use ctype in the docs I can fix the code to match.
  • AFAICT bli_info_get_enable_stay_auto_init is vestigial and the export can be removed. @fgvanzee?

Comment thread docs/BLISObjectAPI.md

### Operation implementation type query

The following routines allow the caller to obtain a string that identifies the implementation (`ind_t`) that is currently active (ie: implemented and enabled) for each level-3 operation. Possible implementation types are listed in the section above covering [microkernel implemenation query](BLISTypedAPI.md#microkernel-implementation-type-query).
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The data type should probably be mentioned here since sd will always return BLIS_NAT while cz could return other values.

Partially undo 4b92ba6 commit for bli_?print[vm]: there should be ctype* instead of void*.
@jip
Copy link
Copy Markdown
Contributor Author

jip commented Jan 21, 2025

* `void*` in `?print[vm]` is an oversight, and should really be `ctype*`. If you use `ctype` in the docs I can fix the code to match.

I've added a correcting commit for docs/BLISTypedAPI.md .

@devinamatthews devinamatthews merged commit a3cfbef into flame:master Jan 21, 2025
@devinamatthews
Copy link
Copy Markdown
Member

Thanks!

@jip jip deleted the fix branch January 21, 2025 01:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants