From: Sam Ravnborg <sam@ravnborg.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
torvalds@transmeta.com, reiserfs-dev@namesys.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Remove 'strchr' warning from reiserfs
Date: Mon, 19 May 2003 23:33:15 +0200 [thread overview]
Message-ID: <20030519213315.GA1069@mars.ravnborg.org> (raw)
In-Reply-To: <20030519124712.2c4b692d.shemminger@osdl.org>
On Mon, May 19, 2003 at 12:47:12PM -0700, Stephen Hemminger wrote:
>
> Is this gcc behaviour documented anywhere?
I dropped a mail to gcc-bugs - the reply was:
=======
The kernel is a special case; GCC is entitled to assume the existence of
standard C library functions.
=======
So when messing with standard functions we may expect a few suprises,
which I think is fair enough.
Sam
next prev parent reply other threads:[~2003-05-19 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-17 19:16 [PATCH] Remove 'strchr' warning from reiserfs Sam Ravnborg
2003-05-19 19:47 ` Stephen Hemminger
2003-05-19 21:33 ` Sam Ravnborg [this message]
2003-05-20 0:26 ` Kurt Wall
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=20030519213315.GA1069@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-dev@namesys.com \
--cc=shemminger@osdl.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