From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Kai Germaschewski <kai-germaschewski@uiowa.edu>,
"David S. Miller" <davem@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.5.46
Date: 05 Nov 2002 17:25:02 +0000 [thread overview]
Message-ID: <1036517102.4827.98.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0211050806151.2762-100000@home.transmeta.com>
On Tue, 2002-11-05 at 16:08, Linus Torvalds wrote:
> Especially since we expect the array to be potentially megabytes in the
> end (especially if somebody wants to make a bootable CD using this), and
> at least traditional gcc's would do horrible O(n^2) things with big
> initialized arrays.
Newer gcc is much saner, but there are other ways to do it - gas is
quite happy to chew a 10Mb .byte file 8)
next prev parent reply other threads:[~2002-11-05 16:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-04 23:13 Linus Torvalds
2002-11-04 23:44 ` Udo A. Steinberg
2002-11-05 11:50 ` [patch] " Gerd Knorr
2002-11-04 23:58 ` Miquel van Smoorenburg
2002-11-05 0:05 ` David T Hollis
2002-11-05 0:10 ` Adrian Bunk
2002-11-05 0:40 ` george anzinger
2002-11-05 0:43 ` Davide Libenzi
2002-11-05 1:15 ` george anzinger
2002-11-05 1:30 ` Davide Libenzi
2002-11-05 2:37 ` Kai Germaschewski
2002-11-05 4:01 ` Skip Ford
2002-11-05 4:17 ` Davide Libenzi
2002-11-05 4:12 ` Skip Ford
2002-11-05 15:58 ` Kai Germaschewski
2002-11-05 6:30 ` David S. Miller
2002-11-05 9:35 ` Linux v2.5.46 (compile error) Michael Kummer
2002-11-05 9:38 ` Linux v2.5.46 (compile error) (rivafb) Michael Kummer
2002-11-09 1:07 ` James Simmons
2002-11-05 11:09 ` Linux v2.5.46 (compile error) Alan Cox
2002-11-05 16:02 ` Linux v2.5.46 Kai Germaschewski
2002-11-05 16:08 ` Linus Torvalds
2002-11-05 17:25 ` Alan Cox [this message]
2002-11-05 16:59 ` David S. Miller
2002-11-06 21:22 ` Robert Love
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=1036517102.4827.98.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=kai-germaschewski@uiowa.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®