From: Alex Williamson <alex.williamson@hp.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-ia64-devel <xen-ia64-devel@lists.xensource.com>,
xen-devel <xen-devel@lists.xensource.com>,
Samuel Thibault <samuel.thibault@eu.citrix.com>
Subject: Re: [PATCH] Re: [Xen-staging] [xen-unstable] Explicitly tag every anonymous aggregate in the public headers.
Date: Mon, 31 Mar 2008 10:28:59 -0600 [thread overview]
Message-ID: <1206980939.7735.14.camel@lappy> (raw)
In-Reply-To: <C416CE2C.1EA53%keir.fraser@eu.citrix.com>
On Mon, 2008-03-31 at 17:21 +0100, Keir Fraser wrote:
> On 31/3/08 16:49, "Alex Williamson" <alex.williamson@hp.com> wrote:
>
> > It seems pretty clear that in nesting __extension__ attributes in this
> > manner, the struct is actually ignored and the compiler is treating the
> > everything that was in the struct as a separate member of the union. In
> > the mapped_regs example, the structure size remains correct only because
> > the union is full padded out using the full size arrays. Please apply
> > the patch I sent previously to revert the nested __extension__
> > attributes. Thanks,
>
> __extension__ seems worryingly half-baked. We're better off asserting
> !__STRICT_ANSI__ in my opinion. I don't suppose you much care either way as
> long as ia64 boot works again. :-)
Yup ;^) FWIW, I still haven't been able to create a simple test
program that shows this behavior. For these tests I've had to resort to
putting printks in xen. There must be some build option we use that
tickles this issue. Still, not good for an option that claims to have
no side effects. Thanks,
Alex
--
Alex Williamson HP Open Source & Linux Org.
next prev parent reply other threads:[~2008-03-31 16:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200803261016.m2QAGPsq017512@latara.uk.xensource.com>
2008-03-26 15:11 ` [PATCH] Re: [Xen-staging] [xen-unstable] Explicitly tag every anonymous aggregate in the public headers Alex Williamson
2008-03-27 14:37 ` Alex Williamson
2008-03-28 21:04 ` Alex Williamson
2008-03-28 21:47 ` Keir Fraser
2008-03-31 15:49 ` Alex Williamson
2008-03-31 16:21 ` Keir Fraser
2008-03-31 16:28 ` Alex Williamson [this message]
2008-03-28 22:37 ` Keir Fraser
2008-03-28 22:55 ` Alex Williamson
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=1206980939.7735.14.camel@lappy \
--to=alex.williamson@hp.com \
--cc=keir.fraser@eu.citrix.com \
--cc=samuel.thibault@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-devel@lists.xensource.com \
/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.