From: Keir Fraser <keir.xen@gmail.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Tim (Xen.org)" <tim@xen.org>,
Jeffrey Karrels <karrelsj@gmail.com>,
Jan Beulich <JBeulich@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Clang/LLVM version requirements
Date: Thu, 13 Sep 2012 16:51:03 +0100 [thread overview]
Message-ID: <CC77BF77.3EB11%keir.xen@gmail.com> (raw)
In-Reply-To: <1347550071.24226.128.camel@zakaz.uk.xensource.com>
On 13/09/2012 16:27, "Ian Campbell" <Ian.Campbell@citrix.com> wrote:
>> I should add, this is mainly a question of how aggressive we should be. I'm
>> quite happy to retire gcc-3.4 support if it happens it is now broken. In
>> that case, x86/Rules.mk should have its gcc version check updated. And
>> perhaps arch/arm may as well do the same? I would be happy to Ack a patch to
>> that effect.
>
> Some data points: Debian Squeeze (current stable) has gcc 4.4 as the
> default (but ships a bunch of others) and Lenny (previous stable) had
> 4.3. AFAICT RHEL5 and SLES10 both shipped 4.1, SLES11 shipped 4.3 and
> RHEL 6 4.4.
>
> Do we really want/need to support host OSes older than RHEL5/SLES10? We
> are talking 2006/7 vintage there.
Yes, I think that is where we are going to draw the line. Thanks.
next prev parent reply other threads:[~2012-09-13 15:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 22:32 Clang/LLVM version requirements Jeffrey Karrels
2012-09-07 8:50 ` Tim Deegan
2012-09-07 10:04 ` Jan Beulich
2012-09-13 10:11 ` Tim Deegan
2012-09-13 11:52 ` Jan Beulich
2012-09-13 12:21 ` Tim Deegan
2012-09-13 14:01 ` Jan Beulich
2012-09-13 14:55 ` Tim Deegan
2012-09-13 15:05 ` Keir Fraser
2012-09-13 15:09 ` Keir Fraser
2012-09-13 15:27 ` Ian Campbell
2012-09-13 15:51 ` Keir Fraser [this message]
2012-09-13 15:22 ` Jan Beulich
2012-09-13 15:34 ` Keir Fraser
2012-09-13 15:06 ` Jan Beulich
2012-09-13 12:40 ` Paolo Bonzini
2012-09-13 14:04 ` Jan Beulich
2012-09-13 14:13 ` Paolo Bonzini
2012-09-13 14:18 ` Jan Beulich
2012-09-07 15:58 ` Jeffrey Karrels
2012-09-11 18:43 ` Jeffrey Karrels
2012-09-12 10:24 ` Stefano Stabellini
2012-09-13 16:15 ` Ian Jackson
2012-09-13 16:41 ` Tim Deegan
2012-09-13 17:04 ` Ian Jackson
2012-09-12 10:31 ` Tim Deegan
2012-09-12 10:38 ` Ian Campbell
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=CC77BF77.3EB11%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=karrelsj@gmail.com \
--cc=pbonzini@redhat.com \
--cc=tim@xen.org \
--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.