memtest86 and memtest86+ are masked for x86_64 with no-multilib. What is a good way to test memory then? sys-apps/memtester? the "memtest" kernel parameter? some other way? I'm looking for something like memtest86+ that could be booted into independently. I didn't anything about this in the FAQ. It appears someone asked about memtest86+ with no-multilib a long time ago, and I guess he claimed he could compile memtest86+ with no-multilib. If that works, of course, I'd probably just go that way...but odd it's still masked if it really has worked since 2006 Any ideas?

A lot of packages that don't care about the bitness of userspace are often invalidly masked on no-multilib, foldingathome is another example. You should be fine to just go ahead and unmask it manually._________________runit-init howto | Overlay - gtk2 stuff

I had just planned to have it as an option in grub2, like on my other machines, so I really hadn't considered downloading and burning a CD or someone's pre-built binary. Yes, that should work. Kind of makes me wonder why it doesn't build under Gentoo, but mostly, I just need a practical solution, so thanks for the tip.

memtest86+ was designed and ripped from the original 32 bit kernel and was never modified to build in a 64-bit environment...

You could also build it in an 32-bit chroot or another 32-bit machine, but until the memtest86 guys hack it so that they can build in a 64-bit environment, you're kind of stuck..._________________Intel Core i7 2700K@ 4.1GHz/HD3000 graphics/8GB DDR3/180GB SSDWhat am I supposed to be advocating?

memtest86 is one of the options (like optional kernels) on a Gentoo
amd64 minimal install cd image. If you have a cd or dvd writer, you
can download and write an install image to cd-r, boot that, and run
memtest86 directly from the cd to test installed ram._________________TIA