public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: a question about memory access on IA64
Date: Fri, 16 Jan 2004 03:16:51 +0000	[thread overview]
Message-ID: <16391.22435.819115.866878@napali.hpl.hp.com> (raw)
In-Reply-To: <40075464.6010202@sinosoft.com.cn>

>>>>> On Fri, 16 Jan 2004 11:03:00 +0800, liuduo <liuduo@sinosoft.com.cn> said:

  liuduo> Dear Sir: nice to see you !  here is a problem about
  liuduo> accessing memory on IA64 as follows, we define a structrue
  liuduo> is : typedef struct b{ unsigned short b1; unsigned short b2;
  liuduo> unsigned char b3; unsigned char b4; unsigned char b5;
  liuduo> unsigned char b6; }B;

  liuduo> typedef struct a{ struct b bb[512]; int c;}A;

  liuduo> when we use the struct A on IA64, the segmentation fault
  liuduo> occurs , and then we modify the struct A as follows :
  liuduo> typedef struct a{ int c; struct b bb[512]; }A; we can use it
  liuduo> normally .  can you explain why ?  thanks a lot , and expect
  liuduo> your reply urgently

The example you posted is not a complete, self-contained program, so
it's impossible to say whats wrong.  Perhaps it's a compiler bug,
perhaps it's a kernel bug, perhaps it's a bug in the program.  Please
post a _minimal_ test program that reproduces the problem you're
trying to solve and state what compiler version, etc. you're using.
Then somebody may be able to help.

	--david

  reply	other threads:[~2004-01-16  3:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-16  3:03 a question about memory access on IA64 liuduo
2004-01-16  3:16 ` David Mosberger [this message]
2004-01-16  3:56 ` liuduo
2004-01-16  4:16 ` Martin Pool
2004-01-16  4:59 ` David Mosberger
2004-01-16  7:01 ` Martin Pool
2004-01-16  7:12 ` liuduo

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=16391.22435.819115.866878@napali.hpl.hp.com \
    --to=davidm@napali.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