Cc: Ingo Molnar <mingo@...>, Linux Kernel Mailing List <linux-kernel@...>, Andrew Morton <akpm@...>, Thomas Gleixner <tglx@...>, H. Peter Anvin <hpa@...>, Alexander van Heukelum <heukelum@...>, <jdike@...>
But when doing this, MARK IT LOUDLY AS A GCC BUG!
The thing is, reading that log message, it was not at all clear why that
change was made. Please make it clear why, rather than quoting a totally
useless error message that doesn't actually tell what is going on.
I agree that having work-arounds for compiler bugs is worth it (assuming
the version is common enough to worry about), but I also don't want to
have unexplained commits doing something that on the face of it is just
odd
Put another way: looking at the actual diff and looking at the commit
message, the only sane reaction from somebody who knows the code is:
"Whaa? WTF?". Saying "This is a gcc bug" would have turned that "WTF?"
into a "Oh, ok then".
Linus
--