All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	"Xu, Quan" <quan.xu@intel.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: stubdom vtpm build failure in staging
Date: Fri, 30 Jan 2015 10:39:56 +0000	[thread overview]
Message-ID: <1422614396.12551.5.camel@citrix.com> (raw)
In-Reply-To: <20150130080921.GA15882@aepfle.de>

On Fri, 2015-01-30 at 09:09 +0100, Olaf Hering wrote:
> On Thu, Jan 29, Ian Campbell wrote:
> 
> > This compiles for me on Debian with gcc 4.7.2-5.
> 
> Same here.
> 
> > I'm honestly not sure what the C standard says about duplicate but
> > identical typedefs -- Ian?
> 
> How would that matter now? ;-) Old gcc can not deal with it, the commits
> cause a regression for gcc-4.5 and older.

If it is allowed then strictly speaking a bug in gcc-4.5 and older has
caused a regression with C compliant code. In some cases we might then
argue that people should fix their compiler, I doubt that will be needed
in this case, but it is an option.

Anyway, in more practical terms right now this might have an impact on
how invasive a fix we would be prepared to accept. In particular if the
current code is valid then we might want to make the fix conditional on
the gcc version so that we can eventually drop it. If the current code
is invalid then the first fix is to make it valid and see if that also
helps with the older gcc.

Ian.

  reply	other threads:[~2015-01-30 10:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-28 15:08 stubdom vtpm build failure in staging Olaf Hering
2015-01-28 15:13 ` Xu, Quan
2015-02-11 15:20   ` Olaf Hering
2015-02-12 16:56     ` Xu, Quan
2015-02-12 17:24       ` Xu, Quan
2015-02-12 17:40         ` Andrew Cooper
2015-02-13  2:07           ` Xu, Quan
2015-02-25 13:54             ` Ian Campbell
2015-02-27 15:07               ` Xu, Quan
2015-03-11 10:51                 ` Ian Campbell
2015-03-12  1:46                   ` Xu, Quan
2015-03-12  9:42                     ` Ian Campbell
2015-03-12 15:44     ` Xu, Quan
2015-03-13 13:30       ` Olaf Hering
2015-03-13 15:39         ` Xu, Quan
2015-01-28 15:24 ` Ian Campbell
2015-01-29  7:34   ` Xu, Quan
2015-01-29  8:27     ` Olaf Hering
2015-01-29  9:22       ` Xu, Quan
2015-01-29  9:36         ` Olaf Hering
2015-01-29 10:27           ` Olaf Hering
2015-01-29 10:46             ` Ian Campbell
2015-01-30  8:09               ` Olaf Hering
2015-01-30 10:39                 ` Ian Campbell [this message]
2015-01-30 11:03               ` Jan Beulich

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=1422614396.12551.5.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=olaf@aepfle.de \
    --cc=quan.xu@intel.com \
    --cc=xen-devel@lists.xen.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 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.