Skip to content

Commit

Permalink
Explanation on why Brain (#59)
Browse files Browse the repository at this point in the history
Signed-off-by: Nicolas Brunie <[email protected]>
Signed-off-by: Ken Dockser <[email protected]>
Co-authored-by: Ken Dockser <[email protected]>
  • Loading branch information
nibrunieAtSi5 and kdockser authored Dec 15, 2023
1 parent 6704c48 commit 6d874ca
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion doc/riscv-bfloat16-introduction.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,8 @@ Experts working in machine learning at Google who continued to work with FP32 va
noted that the least significant 16 bits of their significands were not always needed
for good results, even in training. They proposed a truncated version of FP32, which was
the 16 most significant bits of the FP32 encoding. This format was named BFloat16
(or BF16). The B in BF16, stands for Brain. Not only did they find that the number of
(or BF16). The B in BF16, stands for Brain since it was initially introduced
by the Google Brain team. Not only did they find that the number of
significant bits in BF16 tended to be sufficient for their work (despite being fewer than
in FP16), but it was very easy for them to reuse their existing data; FP32 numbers could
be readily rounded to BF16 with a minimal amount of work. Furthermore, the even smaller
Expand Down

0 comments on commit 6d874ca

Please sign in to comment.