From: Mathieu Chouquet-Stringer <mchouque@online.fr>
To: sparclinux@vger.kernel.org
Subject: Re: Another gcc 3.4 fix
Date: Wed, 12 May 2004 18:51:14 +0000 [thread overview]
Message-ID: <20040512185114.GA14319@localhost> (raw)
In-Reply-To: <20040512052744.GA31207@localhost>
On Wed, May 12, 2004 at 11:32:28AM -0700, David S. Miller wrote:
> Well, what seems to be happening is that GCC believes that
> kernel_unaligned_trap() is not invoked so it does not emit
> the code for that function.
You meant kernel_unaligned_trap_fault, right? If not, why would
kernel_unaligned_trap function be defined in the .o file then? Only
kernel_unaligned_trap_fault is undefined (and unaligned_panic is simply
missing):
0000000000000360 T kernel_unaligned_trap
U kernel_unaligned_trap_fault
> As a consequence, unaligned_panic() can also not be emitted since
> it is only invoked from kernel_unaligned_trap().
>
> Is gcc-3.4 emitting kernel_unaligned_trap() into the unaligned.s file?
It is (at this stage the patch doesn't make any difference, the output
being the same with or without it):
.global kernel_unaligned_trap
.type kernel_unaligned_trap, #function
.proc 020
kernel_unaligned_trap:
.register %g7, #scratch
!#PROLOGUE# 0
save %sp, -208, %sp
!#PROLOGUE# 1
--
Mathieu Chouquet-Stringer E-Mail: mchouque@online.fr
Never attribute to malice that which can be adequately
explained by stupidity.
-- Hanlon's Razor --
next prev parent reply other threads:[~2004-05-12 18:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 5:27 Another gcc 3.4 fix Mathieu Chouquet-Stringer
2004-05-12 18:32 ` David S. Miller
2004-05-12 18:51 ` Mathieu Chouquet-Stringer [this message]
2004-05-12 19:15 ` David S. Miller
2004-05-12 19:45 ` Mathieu Chouquet-Stringer
2004-05-12 19:50 ` David S. Miller
2004-05-12 19:59 ` Mathieu Chouquet-Stringer
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=20040512185114.GA14319@localhost \
--to=mchouque@online.fr \
--cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.