[lkml]   [2005]   [Apr]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [08/08] uml: va_copy fix
On Tuesday 05 April 2005 20:47, Renate Meijer wrote:
> On Apr 5, 2005, at 6:48 PM, Greg KH wrote:
> > -stable review patch. If anyone has any objections, please let us
> > know.
> >
> > ------------------
> >
> > Uses __va_copy instead of va_copy since some old versions of gcc
> > (2.95.4
> > for instance) don't accept va_copy.
> Are there many kernels still being built with 2.95.4? It's quite
> antiquated, as far as
> i'm aware.
> The use of '__' violates compiler namespace.
Why? The symbol is defined by the compiler itself.
> If 2.95.4 were not easily
> replaced by
> a much better version (3.3.x? 3.4.x) I would see a reason to disregard
> this, but a fix
> merely to satisfy an obsolete compiler?

Let's not flame, Linus Torvalds said "we support GCC 2.95.3, because the newer
versions are worse compilers in most cases". One user complained, even
because he uses Debian, and I cannot do less than make sure that we comply
with the requirements we have choosen (compiling with that GCC).

Please let's not start a flame on this. Consider me as having no opinion on
this except not wanting to break on purpose Debian users. If you want, submit
a patch removing Gcc 2.95.3 from supported versions, and get ready to fight
for it (and probably loose).

Also, that GCC has discovered some syscall table errors in UML - I sent a
separate patch, which was a bit big sadly (in the reduced version, about 70
lines + description).
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-04-06 13:31    [W:0.095 / U:4.436 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site