### ImageMagick version

7.1.1.11

### Operating system

Linux

### Operating system, version and so on

Gentoo linux

### Description

While working on https://github.com/gap-packages/hap/issues/115, I noticed that imagemagick and graphicsmagick are producing different pixel values from `convert -colorspace RGB`. After narrowing it down to a one-pixel example, it looks like imagemagick is the one producing mysterious deviations.


### Steps to Reproduce

1. Create a single-pixel image whose RGB value is `#e1cbe1`
2. Save it as a bitmap with no colorspace information
3. Run `convert <infile> -colorspace RGB out.txt`
4. `out.txt` contains `0,0: (192,152,192)  #C098C0  rgb(75.2941%,59.7208%,75.2941%)`

(GraphicMagick, on the other hand, produces `0,0: (225,203,225) #E1CBE1`, which is correct.)

### Images

_No response_
Conversion to text with -colorspace RGB produces wrong pixel values
This is a GitHub Issue
repo:ImageMagick
owner:ImageMagick
Title : Conversion to text with -colorspace RGB produces wrong pixel values
Issue date:

--- start body ---
### ImageMagick version

7.1.1.11

### Operating system

Linux

### Operating system, version and so on

Gentoo linux

### Description

While working on https://github.com/gap-packages/hap/issues/115, I noticed that imagemagick and graphicsmagick are producing different pixel values from `convert -colorspace RGB`. After narrowing it down to a one-pixel example, it looks like imagemagick is the one producing mysterious deviations.


### Steps to Reproduce

1. Create a single-pixel image whose RGB value is `#e1cbe1`
2. Save it as a bitmap with no colorspace information
3. Run `convert <infile> -colorspace RGB out.txt`
4. `out.txt` contains `0,0: (192,152,192)  #C098C0  rgb(75.2941%,59.7208%,75.2941%)`

(GraphicMagick, on the other hand, produces `0,0: (225,203,225) #E1CBE1`, which is correct.)

### Images

_No response_
--- end body ---
