Re: Multiple translation unit regression

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Multiple translation unit regression
From: Christopher Li <sparse@xxxxxxxxxxx>
Date: Mon, 6 Jul 2009 23:27:22 -0700
Cc: Al Viro <viro@xxxxxxxxxxxxxxxxxx>, Junio C Hamano <gitster@xxxxxxxxx>, Andreas Ericsson <ae@xxxxxx>, Sparse Mailing-list <linux-sparse@xxxxxxxxxxxxxxx>
In-reply-to: <70318cbf0907060232j7067f7fcra857b71ebdf62348@xxxxxxxxxxxxxx>
References: <4A5131F4.7070007@xxxxxxxxxxxxxxxxxxx> <70318cbf0907060232j7067f7fcra857b71ebdf62348@xxxxxxxxxxxxxx>

Can you try the following patch? I move the extern inline function
to file scope. Again, I still think it would be better let sparse
check one file at a time.

Chris

Attachment: extern-inline
Description: Binary data

Follow-Ups:
- Re: Multiple translation unit regression
  - From: Ramsay Jones

References:
- Multiple translation unit regression
  - From: Ramsay Jones
- Re: Multiple translation unit regression
  - From: Christopher Li

Prev by Date: Re: Multiple translation unit regression
Next by Date: Re: [PATCH] kmemcheck: fix sparse warning
Previous by thread: Re: Multiple translation unit regression
Next by thread: Re: Multiple translation unit regression
Index(es):
- Date
- Thread

[Index of Archives] [Newbies FAQ] [LKML] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Trinity Fuzzer Tool]

Powered by Linux