linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-wireless@vger.kernel.org, linux-sparse@vger.kernel.org
Subject: Re: sparse using insane amounts of memory
Date: Thu, 08 Mar 2007 17:45:14 +0100	[thread overview]
Message-ID: <1173372315.3248.19.camel@johannes.berg> (raw)
In-Reply-To: <1173371608.21465.12.camel@dv>

[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]

On Thu, 2007-03-08 at 11:33 -0500, Pavel Roskin wrote:

> You forgot the version of sparse.

Good point. The commit is c4670dfcbe52b598e263c452762a66d22e636585.

>   I cannot reproduce the problem with
> the current sparse from git
> (git://git.kernel.org/pub/scm/linux/kernel/git/josh/sparse.git)

I just upgraded to 309f3805ddec9ab2f9c62da573586a7cf7c1f17a and still
observe that it uses a lot of memory.

> If you still have the problem, please remove rt2400pci.o and run:
> 
> make CC="gcc -save-temps -D__CHECKER__" KBUILD_NOCMDDEP=1
> 
> rt2400pci.i will be found in the root of the build tree.  Please see if
> you have a problem with it.  If you do, please put it online and post
> the URL.

I ran 

  make CC="gcc -save-temps -D__CHECKER__" KBUILD_NOCMDDEP=1 M=drivers/net/wireless/mac80211/rt2x00/

and aborted when I got lots of errors, rt2400pci.i was created and has
about 26k lines. Running sparse on it (sparse rt2400pci.i) takes a lot
of memory too. I put the file up at
http://johannes.sipsolutions.net/files/rt2400pci.i

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  reply	other threads:[~2007-03-08 16:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08  2:02 sparse using insane amounts of memory Johannes Berg
     [not found] ` <1173319356.3546.54.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2007-03-08 16:33   ` Pavel Roskin
2007-03-08 16:45     ` Johannes Berg [this message]
2007-03-08 17:13       ` Pavel Roskin
2007-03-08 17:31         ` Chris Wedgwood
2007-03-08 17:43         ` Linus Torvalds
     [not found]       ` <1173372315.3248.19.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2007-03-08 17:34         ` Pavel Roskin
2007-03-08 17:42           ` Johannes Berg
2007-03-08 17:43           ` Johannes Berg
2007-03-08 18:08             ` Ivo van Doorn
2007-03-08 18:54               ` Linus Torvalds
     [not found]                 ` <Pine.LNX.4.64.0703081023490.10832-5CScLwifNT1QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
2007-03-08 19:02                   ` Sam Ravnborg
2007-03-08 19:08                   ` Linus Torvalds
     [not found]                     ` <Pine.LNX.4.64.0703081104010.10832-5CScLwifNT1QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
2007-03-10  5:05                       ` Darren Jenkins
2007-03-08 19:26                   ` Ivo van Doorn
2007-03-09  1:12                 ` OT [Re: sparse using insane amounts of memory] Tommy Thorn
2007-03-09  2:15                   ` OT David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1173372315.3248.19.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=linux-sparse@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=proski@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).