From: david mosberger <dmosberger@gmail.com>
To: linux-ia64@vger.kernel.org
Subject: Re: autocompilation hosed?
Date: Thu, 14 Jul 2005 17:43:22 +0000 [thread overview]
Message-ID: <ed5aea4305071410437afb6db9@mail.gmail.com> (raw)
In-Reply-To: <ed5aea4305071214283aada0f2@mail.gmail.com>
On 7/14/05, Magenheimer, Dan (HP Labs Fort Collins)
<dan.magenheimer@hp.com> wrote:
> > > No ... I saw it too without gcc-4. See
> > http://tinyurl.com/clzbu where I
> > > identified the patch that seems to be the cause.
> >
> > Patch below fixes the problem. Moral of the story: don't add
> > "attributed(packed)" lightly!
>
> IIRC as of gcc3.2, attribute(packed) on ia64 meant roughly the
> equivalent of specifying "generate the worst case possible
> code even for things that are aligned". Is that still the
> case in gcc-4?
I'm not sure whether gcc-4 is doing a better job at identifying
structures which are aligned better than the worst-case (I'd be
curious to hear about that, if somebody plays with this or already
knows how it behaves). Having said that, for EFI that's hardly an
issue since most of the code using those structures is executed only
once at boot-time, so performance isn't an issue (I suppose code-size
may be almost a bigger issue in that area).
--david
next prev parent reply other threads:[~2005-07-14 17:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 21:28 autocompilation hosed? david mosberger
2005-07-12 22:26 ` Ian Wienand
2005-07-12 22:28 ` david mosberger
2005-07-13 1:40 ` Ian Wienand
2005-07-13 3:28 ` david mosberger
2005-07-13 3:45 ` Tony Luck
2005-07-13 4:50 ` david mosberger
2005-07-14 15:23 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-07-14 17:43 ` david mosberger [this message]
2005-07-14 22:02 ` James E Wilson
2005-07-14 22:07 ` Magenheimer, Dan (HP Labs Fort Collins)
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=ed5aea4305071410437afb6db9@mail.gmail.com \
--to=dmosberger@gmail.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