> Kernel code tends to dictate/control things at the lower levels > (e.g., directly inserted assembly code, variables held in specific > CPU registers, "volatile" memory regions, etc.) more than is typical > in normal applications. Perhaps these kinds of special compile > requirements things cause gcc to lean more heavily on gmp in certain > areas thus triggering the problem.
I found the clue: "The main target applications of GMP are cryptography applications and research, Internet security applications, and computer algebra systems." So it must be the kernel's crypto functions tripping over it, and I can understand new instruction set evolutions wouldn't be backwards-compatible. Still, if gcc weren't trying to embed those instructions in the kernel and were just setting the kernel up to use gmplib, it seems more likely they would be a runtime error. I suppose TLS & OpenSSL might also try it. So I still don't think I understand it yet. -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
