You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
- 2-1 I'm not asking about the sizes of the fields in numbers of bits, just the actual order of them. The size of the single is not relevant to the question at all, and instead I'm asking why we are fitting the sign bit with the seven high bits of the exponent into a byte. Reordering them such that all eight bits of the exponent be in one byte, and the sign moved into one of the mantissa bytes, doesn't require changing anything about either the precision or range of the singlepetroleus– petroleus2025-02-28 14:26:06 +00:00Commented Feb 28 at 14:26
- 1@petroleus your question about bit ordering to match byte boundaries is only relevant with certain number of bits, so the number of bits is very much relevant. Second, we give answers to questions to help everyone, not as a personal answering service to you.gnasher729– gnasher7292025-02-28 18:45:48 +00:00Commented Feb 28 at 18:45
- @petroleus, I think the meat of gnasher's answer is in the last paragraph. The first two paragraphs are just providing a mathematical basis for the conclusion reached in the last paragraph: aligning to 8-bits has no advantage, nobody is complaining about it, and it would only matter on 8-bit hardware that nobody uses in the real world. Assuming I understood the answer correctly, maybe an edit to this answer to clarify or highlight this conclusion would help?Greg Burghardt– Greg Burghardt2025-02-28 20:36:26 +00:00Commented Feb 28 at 20:36
- If you had an exponent field with nine bits, eight bit alignment would mean you have 6 mantissa bits before and 16 after the exponent field. Which would be utterly stupid.gnasher729– gnasher7292025-09-02 18:19:44 +00:00Commented Sep 2 at 18:19
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you