id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
357	SUBTAG-BYTES and weird element-types	rme	gb	"On 32-bit platforms, we see:
{{{
? (open #p""/dev/null"" :direction :probe :element-type '(unsigned-byte 33))
> Error: Not an ivector subtag: 170
> While executing: SUBTAG-BYTES, in process listener(1).
}}}

The 170 is subtag-simple-vector.  Maybe SUBTAG-BYTES should just punt somehow if it gets a non-ivector subtag?  Maybe return NIL and deal with that in OPTIMAL-BUFFER-SIZE?

(From the test suite.)

"	defect	closed	minor		Runtime (threads, GC)	trunk	duplicate