public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Cc: petero2@telia.com, Andrew Morton OSDL <akpm@osdl.org>,
	Linus Torvalds <torvalds@osdl.org>
Subject: Re: Linux 2.6.7-rc2
Date: 31 May 2004 08:20:24 -0400	[thread overview]
Message-ID: <1086006023.8188.34.camel@cube> (raw)

Peter Osterlund writes:

> If I put "#if 0" around the *wdata assignment in
> nfs_writepage_sync, the stack usage goes down to 36,
> so it looks like gcc is building a temporary structure
> on the stack and then copies the whole thing to *wdata.

This would be required because of the -Wno-strict-aliasing
option. For the 2.7.xx kernels, how about we start off by
replacing -Wno-strict-aliasing with -std=gnu99 ? It's been
5 years since 1999. The "restrict" keyword is useful too.



             reply	other threads:[~2004-05-31 14:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-31 12:20 Albert Cahalan [this message]
2004-05-31 16:53 ` Linux 2.6.7-rc2 Linus Torvalds
2004-05-31 15:12   ` Albert Cahalan
  -- strict thread matches above, loose matches on Subject: below --
2004-05-30  6:52 Linus Torvalds
2004-05-30  7:56 ` Danny ter Haar
2004-05-30 11:09   ` Francois Romieu
2004-05-30 13:16     ` Danny ter Haar
2004-05-30 13:24       ` Danny ter Haar
2004-05-30 16:26   ` Malte Schröder
2004-05-30 17:26   ` Jeff Garzik
2004-05-31  9:21 ` Peter Osterlund
2004-05-31  9:27   ` Andrew Morton
2004-05-31 16:58   ` Linus Torvalds
2004-05-31 22:04     ` Peter Osterlund
2004-06-03 20:01       ` Flavio Stanchina
2004-06-02 14:37 ` Thomas Zehetbauer
2004-06-04 14:06   ` Denis Vlasenko
2004-06-08 17:02     ` Bill Davidsen
2004-06-08 18:02       ` David Ford

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=1086006023.8188.34.camel@cube \
    --to=albert@users.sf.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petero2@telia.com \
    --cc=torvalds@osdl.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