public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephane Eranian <eranian@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Simulator bootloader fails with gcc 4
Date: Thu, 18 Aug 2005 19:07:55 +0000	[thread overview]
Message-ID: <20050818190755.GA4925@frankl.hpl.hp.com> (raw)
In-Reply-To: <20050720053139.GC13188@cse.unsw.EDU.AU>

Tony,

On Thu, Aug 18, 2005 at 11:57:03AM -0700, Luck, Tony wrote:
> >Anyway, I looked quickly at the simulator code. I don't see anything
> >wrong on that side. On SSC_COMPLETION, you end up doing a byte by byte
> >memcpy for copyin for disk_stat and a byte by byte for copyout. Not much
> >could go wrong there. The definition for disk_stat is identical (w/o the
> >aligned attribute).
> 
> Ah ... but gcc has an unpleasant habit of inlining memcpy() calls.  This
> is really annoying when you have taken the trouble to replace code
> does a structure copy with an explicit call to memcpy() becuase
> you know that one of the source or destination is unaligned, only
> to have gcc generate some inline ld8/st8 instructions.

The simulator is not using the regular memcpy() routine it has its own
custom routine (which is not named memcpy).

-- 

-Stephane

  parent reply	other threads:[~2005-08-18 19:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-20  5:31 Simulator bootloader fails with gcc 4 Ian Wienand
2005-07-20 22:34 ` James E Wilson
2005-07-22  4:58 ` Ian Wienand
2005-07-22  6:00 ` david mosberger
2005-08-15  1:49 ` Ian Wienand
2005-08-16 22:46 ` Luck, Tony
2005-08-18  0:53 ` Ian Wienand
2005-08-18 13:25 ` Stephane Eranian
2005-08-18 18:57 ` Luck, Tony
2005-08-18 19:07 ` Stephane Eranian [this message]
2005-08-18 23:14 ` Peter Chubb
2005-08-18 23:41 ` Stephane Eranian
2005-08-18 23:58 ` Peter Chubb
2005-08-19 11:33 ` Stephane Eranian
2005-08-19 23:13 ` Peter Chubb
2005-08-19 23:43 ` Stephane Eranian
2005-08-19 23:55 ` Peter Chubb
2005-08-22 13:00 ` Gerald Pfeifer
2005-08-22 22:16 ` Andreas Schwab

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=20050818190755.GA4925@frankl.hpl.hp.com \
    --to=eranian@hpl.hp.com \
    --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