Re: sparse -Wptr-subtraction-blows: still needed?

On Tue, 1 May 2007, Josh Triplett wrote:
> 
> Does this still apply?  Do current versions of GCC still have this problem?
> If not, can the option and warning go away?

Even if current versions of gcc don't triple the build time (and for the 
kernel, I suspect it doesn't, because we've tried to clean up our header 
files), the generated _code_ will invariably suck.

So I'd not want to remove the warning.

		Linus
-
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/

---

• Follow-Ups:
  • Re: sparse -Wptr-subtraction-blows: still needed?
    • From: Dave Jones <[email protected]>
  • Re: sparse -Wptr-subtraction-blows: still needed?
    • From: Al Viro <[email protected]>
  • Re: sparse -Wptr-subtraction-blows: still needed?
    • From: Josh Triplett <[email protected]>

• References:
  • sparse -Wptr-subtraction-blows: still needed?
    • From: Josh Triplett <[email protected]>

• Prev by Date: Re: arch/i386/boot rewrite, and all the hard-coded video cards
• Next by Date: [PATCH] workqueues: shift kthread_bind() from CPU_UP_PREPARE to CPU_ONLINE
• Previous by thread: sparse -Wptr-subtraction-blows: still needed?
• Next by thread: Re: sparse -Wptr-subtraction-blows: still needed?
• Index(es):
  • Date
  • Thread

[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]