From: Sam Ravnborg <sam@xxxxxxxxxxxx>
Date: Wed, 20 Apr 2011 14:58:53 +0200
> The issue with boot_cpu_id being cleared is btw not new - but
> I should have caught that anyway.
It's partially another side effect of that awful behavioral change GCC
made several years ago to "auto BSS" variables explicitly initialized
to zero.
You used to be able to add an explicit zero initialization to force
items into the data section.
This change has broken various things in the sparc32 port over the
years.
Probably the thing to do is to initialize boot_cpu_id{,4} to some
"invalid" value (like 0xff) in the kernel image and just make certain
the the initialization happens early enough.
--
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
