From: Gregory Nutt <greg.nutt@cadenux.com>
To: linux-mips@linux-mips.org
Subject: gcc 3.4 / bad_unaligned_access_length
Date: Wed, 06 Oct 2004 08:51:11 -0600 [thread overview]
Message-ID: <1097074271.9253.8.camel@spudrun> (raw)
Hi, List,
I have been struggling to bring up 2.6.8-rc2 on an Au1100 processor. I
am using gcc 3.4.1 which seems to the be source of most of the issues
that I have been having.
Here is the last issue:
- At boot time, I was encountering a fault in slab.c -- ac_data
was returning a NULL pointer. But when I put in lots of printk's
the problem disappeared. Hmmm.. sound like an optimization
issue. Has anyone else seen this?
- So I tried lowering the optimization to -O1 by editting the top-
level Makefile. Now, to my surprise, I can no longer link the
kernel. I get:
"fs/built-in.o(.text+0x3a0c4): In function `parse_extended':
: undefined reference to `bad_unaligned_access_length'"
This repeats several times.
I grep'ped through the kernel. I see that bad_unaligned_access_length()
is externed in include/asm-mips/unaligned.h. It is also used in the
default: case of several inline functions in that same file. It is not
referenced or defined anywhere else in the kernel.
My hunch is that at -O2 the calls to bad_unaligned_access_length() were
optimized away and all is well. But at -O1 they are not.
Greg Nutt
--
Gregory Nutt <greg.nutt@cadenux.com>
Cadenux, LLC
next reply other threads:[~2004-10-06 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 14:51 Gregory Nutt [this message]
2004-10-06 14:59 ` Au1100 Serial Driver Gregory Nutt
2004-10-10 2:38 ` Pete Popov
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=1097074271.9253.8.camel@spudrun \
--to=greg.nutt@cadenux.com \
--cc=linux-mips@linux-mips.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