public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Missing EXPORT_SYMBOL memset
Date: Sat, 13 Apr 2002 02:17:05 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905449@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905441@msgid-missing>

On Fri, 12 Apr 2002 19:10:24 -0700, 
David Mosberger <davidm@napali.hpl.hp.com> wrote:
>>>>>> On Sat, 13 Apr 2002 11:55:13 +1000, Keith Owens <kaos@ocs.com.au> said:
>
>  Keith> I know about the "gcc decides to insert memset after cpp
>  Keith> phase" problem.  When it occurred in the past (it used to
>  Keith> happen with gcc 2.7 in 2.[02] kernels) the response was
>  Keith> always to change the source code to prevent gcc making this
>  Keith> wrong decision.
>
>I don't see much wrong with gcc generating calls to memset().
>What problem are you worried about?

Because those calls are generated after cpp has run so they do not use
#define memset.  We end up with two classes of memset, most using the
macro but a few using the function.  When this problem occurred in the
context of gcc 2.7 and 2.[02] kernels, the response was always to
change the source code to prevent gcc generating code that we did not
want.  If that decision is going to change, it needs to be run past l-k
first.



  parent reply	other threads:[~2002-04-13  2:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-12 15:05 [Linux-ia64] Missing EXPORT_SYMBOL memset Andreas Schwab
2002-04-13  1:28 ` Keith Owens
2002-04-13  1:38 ` Andreas Schwab
2002-04-13  1:55 ` Keith Owens
2002-04-13  1:57 ` David Mosberger
2002-04-13  1:57 ` Andreas Schwab
2002-04-13  2:00 ` David Mosberger
2002-04-13  2:10 ` David Mosberger
2002-04-13  2:17 ` Keith Owens [this message]
2002-04-13  2:21 ` David Mosberger

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=marc-linux-ia64-105590701905449@msgid-missing \
    --to=kaos@ocs.com.au \
    --cc=linux-ia64@vger.kernel.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