From: Richard Hirst <rhirst@linuxcare.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] gcc/binutils bug building parted?
Date: Thu, 14 Mar 2002 01:11:07 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905269@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905246@msgid-missing>
On Wed, Mar 13, 2002 at 10:34:53AM -0800, David Mosberger wrote:
> Oh, I see now what's wrong: data4 implicitly aligns the data to a 4-byte
> boundary. To get an unaligned entry, you'd have to use data4.ua or gcc
> would have to emit the data byte by byte (data1).
>
> This needs to be fixed in the compiler. Would you mind filing a bug
> report with the gcc folks?
Will do.
> typedef unsigned char guid_t[16];
> #define EFI_GUID(a,b,c,b0,b1,b2,b3,b4,b5,b6,b7)
OK, thanks. I'll work up a patch for parted to do that if no-one beats
me to it.
Cheers,
Richard
next prev parent reply other threads:[~2002-03-14 1:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 20:45 [Linux-ia64] gcc/binutils bug building parted? Richard Hirst
2002-03-13 5:01 ` David Mosberger
2002-03-13 11:57 ` Richard Hirst
2002-03-13 18:34 ` David Mosberger
2002-03-13 18:52 ` Matt_Domsch
2002-03-14 1:11 ` Richard Hirst [this message]
2002-03-15 13:15 ` Richard Hirst
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=marc-linux-ia64-105590701905269@msgid-missing \
--to=rhirst@linuxcare.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