This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: is trunk broken on i686?

From: Jerry DeLisle <jvdelisle at verizon dot net>
To: Thomas Koenig <Thomas dot Koenig at online dot de>
Cc: "Christopher D. Rickett" <crickett at lanl dot gov>, Andrew Pinski <pinskia at physics dot uc dot edu>, fortran at gcc dot gnu dot org
Date: Sat, 20 May 2006 13:23:06 -0700
Subject: Re: is trunk broken on i686?
References: <Pine.LNX.4.58.0605181116490.30232@lennox.lanl.gov> <3F105C3B-4C02-4C3A-8F3A-1D1F81F17CB0@physics.uc.edu> <Pine.LNX.4.58.0605181136250.30232@lennox.lanl.gov> <20060520193442.GA9770@meiner.onlinehome.de> <20060520193903.GA32533@meiner.onlinehome.de>

Thomas Koenig wrote:

I wrote:
On Thu, May 18, 2006 at 11:38:34AM -0600, Christopher D. Rickett wrote:

build/genconstants.o(.text+0x182): In function `VEC_rtx_base_last': /home/crickett/svnGcc/trunk/gcc/rtl.h:194: undefined reference to `vec_assert_fail'
I'm seeing the same thing on i686-pc-cygwin, building a native compiler.
See my comment on http://gcc.gnu.org/PR27251 .
... and on i686-pc-linux-gnu. Looks nasty.

I just did an update and full bootstrap about 12 hours ago on i686-pc-linux-gnu and had no failures. So there must be something odd going on here recently.

Jerry

Follow-Ups:
- Re: is trunk broken on i686?
  - From: Andrew Pinski

References:
- is trunk broken on i686?
  - From: Christopher D. Rickett
- Re: is trunk broken on i686?
  - From: Andrew Pinski
- Re: is trunk broken on i686?
  - From: Christopher D. Rickett
- Re: is trunk broken on i686?
  - From: Thomas Koenig
- Re: is trunk broken on i686?
  - From: Thomas Koenig

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]