From: Hans-Peter Nilsson <hp@bitrange.com>
To: Andreas Tobler <andreast-list@fgznet.ch>
Cc: Diego Novillo <dnovillo@google.com>, gcc-patches@gcc.gnu.org
Subject: Re: VEC re-write [patch 01/25]
Date: Sun, 18 Nov 2012 19:50:00 -0000 [thread overview]
Message-ID: <alpine.BSF.2.02.1211181448190.92389@dair.pair.com> (raw)
In-Reply-To: <50A937BE.2010704@fgznet.ch>
On Sun, 18 Nov 2012, Andreas Tobler wrote:
> On 18.11.12 20:11, Hans-Peter Nilsson wrote:
> > On Sun, 18 Nov 2012, Andreas Tobler wrote:
> >> Is there a minimum gcc to bootstrap current trunk?
> >> I currently fail to bootstrap trunk with a 4.2.1 gcc, but a 4.6
> >> succeeds.
> >
> > A gcc-4.1.2 has worked for me in the past, before this recent
> > vec.h change. I think that's the minimum version reportedly
> > working.
>
> Up to 193594 a 4.2.1 did it fine on most of my platforms. But with
> 193595 it seems that I have to use a more recent gcc to bootstrap.
Yes, that's the vec.h-change revision. I hope we can revert
that behavior (the *behavior*, not the patch).
brgds, H-P
next prev parent reply other threads:[~2012-11-18 19:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 21:53 Diego Novillo
[not found] ` <50A61414.8070908@redhat.com>
2012-11-16 12:13 ` Diego Novillo
2012-11-16 12:22 ` Pedro Alves
2012-11-16 23:16 ` Ian Lance Taylor
2012-11-18 2:57 ` Diego Novillo
2012-11-18 17:05 ` Hans-Peter Nilsson
2012-11-18 17:12 ` Diego Novillo
2012-11-18 17:43 ` Hans-Peter Nilsson
2012-11-18 17:48 ` Diego Novillo
2012-11-18 19:15 ` Andrew Pinski
2012-11-19 19:57 ` Jack Howarth
2012-11-19 20:16 ` Jack Howarth
2012-11-25 13:11 ` Richard Biener
2012-11-25 15:25 ` Diego Novillo
2012-11-18 18:25 ` Andreas Tobler
2012-11-18 19:12 ` Hans-Peter Nilsson
2012-11-18 19:32 ` Andreas Tobler
2012-11-18 19:50 ` Hans-Peter Nilsson [this message]
2012-11-20 13:57 ` Ulrich Weigand
2012-11-18 21:28 David Edelsohn
2012-11-19 1:04 ` Diego Novillo
2012-11-19 1:14 ` David Edelsohn
2012-11-19 3:18 ` Ian Lance Taylor
2012-11-19 14:46 ` David Edelsohn
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=alpine.BSF.2.02.1211181448190.92389@dair.pair.com \
--to=hp@bitrange.com \
--cc=andreast-list@fgznet.ch \
--cc=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).