From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Brian Gerst <bgerst@didntduck.org>
Cc: Richard Henderson <rth@twiddle.net>,
Petr Vandrovec <VANDROVE@vc.cvut.cz>, dvorak <dvorak@xs4all.nl>,
linux-kernel@vger.kernel.org
Subject: Re: Syscall changes registers beyond %eax, on linux-i386
Date: Thu, 19 Sep 2002 15:18:02 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.3.95.1020919151622.15882A-100000@chaos.analogic.com> (raw)
In-Reply-To: <3D8A1CC0.8070407@didntduck.org>
On Thu, 19 Sep 2002, Brian Gerst wrote:
> Richard Henderson wrote:
> > On Thu, Sep 19, 2002 at 02:04:43PM -0400, Brian Gerst wrote:
> >
> >>Now that I've thought about it more, I think the best solution is to go
> >>through all the syscalls (a big job, I know), and declare the parameters
> >>as const, so that gcc knows it can't modify them, and will throw a
> >>warning if we try.
> >
> >
> > The parameter area belongs to the callee, and it may *always* be modified.
> >
> >
> > r~
> >
>
> The parameters can not be modified if they are declared const though,
> that's my point.
Yes. A temporary declaration change to compile the kernel and
see where it complains.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.18 on an i686 machine (797.90 BogoMips).
The US military has given us many words, FUBAR, SNAFU, now ENRON.
Yes, top management were graduates of West Point and Annapolis.
next prev parent reply other threads:[~2002-09-19 19:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 17:44 Syscall changes registers beyond %eax, on linux-i386 Petr Vandrovec
2002-09-19 18:04 ` Brian Gerst
2002-09-19 18:30 ` Richard Henderson
2002-09-19 18:51 ` Brian Gerst
2002-09-19 18:57 ` Richard Henderson
2002-09-19 19:40 ` Richard B. Johnson
2002-09-19 19:41 ` Richard Henderson
2002-09-19 19:53 ` Richard B. Johnson
2002-09-19 22:46 ` J.A. Magallon
2002-09-20 12:27 ` Richard B. Johnson
2002-09-20 17:16 ` Richard Henderson
2002-09-22 1:33 ` Pavel Machek
2002-09-23 13:11 ` Richard B. Johnson
2002-09-23 18:31 ` Pavel Machek
2002-09-19 19:18 ` Richard B. Johnson [this message]
2002-09-19 19:24 ` Daniel Jacobowitz
2002-09-19 20:25 ` Mikael Pettersson
2002-09-20 8:32 ` george anzinger
2002-09-21 6:19 ` Richard Henderson
2002-09-21 8:09 ` george anzinger
2002-09-21 15:08 ` Richard Henderson
2002-09-24 18:02 ` CHECKER bate: " george anzinger
-- strict thread matches above, loose matches on Subject: below --
2002-09-19 14:45 dvorak
2002-09-19 16:11 ` Richard B. Johnson
2002-09-19 17:09 ` Brian Gerst
2002-09-19 17:22 ` Richard B. Johnson
2002-09-19 17:51 ` Brian Gerst
2002-09-19 18:30 ` Richard B. Johnson
2002-09-19 17:59 ` dvorak
2002-09-19 18:32 ` Richard B. Johnson
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=Pine.LNX.3.95.1020919151622.15882A-100000@chaos.analogic.com \
--to=root@chaos.analogic.com \
--cc=VANDROVE@vc.cvut.cz \
--cc=bgerst@didntduck.org \
--cc=dvorak@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
/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).