All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Chouquet-Stringer <mchouque@online.fr>
To: sparclinux@vger.kernel.org
Subject: Re: Another gcc 3.4 fix
Date: Wed, 12 May 2004 19:45:11 +0000	[thread overview]
Message-ID: <20040512194511.GA15250@localhost> (raw)
In-Reply-To: <20040512052744.GA31207@localhost>

On Wed, May 12, 2004 at 12:15:18PM -0700, David S. Miller wrote:
> It can't be the same in both cases, because something is
> making kernel_unaligned_trap_fault underfined right?  

My bad, I had the -fno-unit-at-a-time option on the command line.

So with the original version of unaligned.c, there's a
kernel_unaligned_trap in the .s file but no kernel_unaligned_trap_fault
(only references to it) and no unaligned_panic. (am I making myself clear
here?)

That's why I was saying I don't get it: why forcing gcc to generate code
for unaligned_panic make it build kernel_unaligned_trap_fault?

> One way is for it not to get emitted at all, and that's what
> I thought was occurring with gcc-3.4 builds.
>
> Meanwhile, I've put your workaround in for the time being.

Ok.
-- 
Mathieu Chouquet-Stringer                 E-Mail: mchouque@online.fr
       Never attribute to malice that which can be adequately
                    explained by stupidity.
                     -- Hanlon's Razor --

  parent reply	other threads:[~2004-05-12 19:45 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
2004-05-12 19:15 ` David S. Miller
2004-05-12 19:45 ` Mathieu Chouquet-Stringer [this message]
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=20040512194511.GA15250@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.