* Linus Torvalds <[email protected]> wrote:
> And people are nervous about it, exactly because the gcc people have
> historically just changed what "inline" means, with little regard for
> real-life code that uses it. [...]
i think whatever gcc does, we probably cannot get hurt more than we are
hurting right now: everything is inlined, which bloats stuff to the
maximum level. Stating that doesnt in any way excuse gcc 3.1's
unilateral change of what 'inline' means, it doesnt reduce the distrust
that might exist towards gcc, it's simply a statement of the situation
we have right now. We can continue to distrust gcc (and probably
rightfully so), but we probably cannot continue to hurt users as
collateral damage of whatever tool-level fight. (and i'm not suggesting
that this collateral damage is intentional in any way, it slowly evolved
into the mess we have now.)
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
