From: Keith Owens <kaos@ocs.com.au>
To: Sven Heinicke <sven@research.nj.nec.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: undefined reference in 2.2.19 build with Reiserfs (was: Google's mm problem - not reproduced on 2.4.13)
Date: Fri, 02 Nov 2001 09:39:05 +1100 [thread overview]
Message-ID: <1180.1004654345@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Thu, 01 Nov 2001 11:56:04 CDT." <15329.32420.468485.681104@abasin.nj.nec.com>
On Thu, 1 Nov 2001 11:56:04 -0500 (EST),
Sven Heinicke <sven@research.nj.nec.com> wrote:
>fs/filesystems.a(reiserfs.o): In function `ip_check_balance':
>reiserfs.o(.text+0x9cc2): undefined reference to `memset'
>drivers/scsi/scsi.a(aic7xxx.o): In function `aic7xxx_load_seeprom':
>aic7xxx.o(.text+0x117ff): undefined reference to `memcpy'
The aic7xxx reference to memcpy is a gcc feature. If you do an
assignment of a complete structure then gcc may convert that into a
call to memcpy(). Alas gcc does the conversion using the "standard"
version of memcpy, not the "optimized by cpp" version that the kernel
uses. Try this patch
Index: 19.1/drivers/scsi/aic7xxx.c
--- 19.1/drivers/scsi/aic7xxx.c Tue, 13 Feb 2001 08:26:08 +1100 kaos (linux-2.2/d/b/43_aic7xxx.c 1.1.1.3.2.1.3.1.1.3 644)
+++ 19.1(w)/drivers/scsi/aic7xxx.c Fri, 02 Nov 2001 09:36:49 +1100 kaos (linux-2.2/d/b/43_aic7xxx.c 1.1.1.3.2.1.3.1.1.3 644)
@@ -9190,7 +9190,7 @@ aic7xxx_load_seeprom(struct aic7xxx_host
p->flags |= AHC_TERM_ENB_SE_LOW | AHC_TERM_ENB_SE_HIGH;
}
}
- p->sc = *sc;
+ memcpy(&(p->sc), sc, sizeof(p->sc));
}
p->discenable = 0;
Cannot help with the reiserfs problem, the code is not in the pristine
2.2.19 tree.
next prev parent reply other threads:[~2001-11-01 22:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-31 18:06 Google's mm problem - not reproduced on 2.4.13 Daniel Phillips
2001-10-31 20:39 ` Daniel Phillips
2001-10-31 20:45 ` Andrea Arcangeli
2001-10-31 21:03 ` Daniel Phillips
2001-10-31 21:53 ` Andreas Dilger
2001-11-01 4:52 ` Daniel Phillips
2001-11-01 16:56 ` undefined reference in 2.2.19 build with Reiserfs (was: Google's mm problem - not reproduced on 2.4.13) Sven Heinicke
2001-11-01 22:39 ` Keith Owens [this message]
2001-10-31 22:12 ` Google's mm problem - not reproduced on 2.4.13 Ben Smith
2001-11-01 0:34 ` Andrea Arcangeli
2001-11-02 17:51 ` Sven Heinicke
2001-11-02 18:00 ` Andrea Arcangeli
2001-11-02 18:19 ` Daniel Phillips
2001-11-02 20:27 ` Linus Torvalds
2001-11-02 21:08 ` Ben Smith
2001-11-02 21:20 ` Linus Torvalds
2001-11-02 22:42 ` Ben Smith
2001-11-02 23:15 ` Daniel Phillips
2001-11-03 22:53 ` Adaptec vs Symbios performance Stephan von Krawczynski
2001-11-03 23:01 ` arjan
2001-11-02 21:12 ` Google's mm problem - not reproduced on 2.4.13 Rik van Riel
[not found] ` <200111022027.fA2KRwe20006@penguin.transmeta.com>
2001-11-02 20:58 ` Daniel Phillips
2001-11-02 18:11 ` Daniel Phillips
2001-11-02 18:48 ` Sven Heinicke
2001-11-02 18:57 ` Daniel Phillips
2001-11-01 0:19 ` Daniel Phillips
2001-11-01 0:29 ` Andrea Arcangeli
2001-11-01 1:17 ` Ben Smith
2001-11-01 1:41 ` Rik van Riel
2001-11-01 1:55 ` Ben Smith
2001-11-01 2:06 ` Andrea Arcangeli
2001-10-31 20:48 ` Rik van Riel
2001-10-31 21:04 ` Daniel Phillips
2001-10-31 21:08 ` Rik van Riel
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=1180.1004654345@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=sven@research.nj.nec.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®