This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC 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: 4.6.1 bootstrap failure on ia64

From: Salvatore Filippone <salvatore dot filippone at uniroma2 dot it>
To: Ian Lance Taylor <iant at google dot com>
Cc: gcc-help at gcc dot gnu dot org
Date: Sun, 16 Oct 2011 16:23:44 +0200
Subject: Re: 4.6.1 bootstrap failure on ia64
References: <1318583001.3486.32.camel@localhost.localdomain> <mcrk487549y.fsf@coign.corp.google.com> <1318694093.3109.2.camel@localhost.localdomain> <mcrvcrp4quo.fsf@coign.corp.google.com>
Reply-to: salvatore dot filippone at uniroma2 dot it

Il giorno sab, 15/10/2011 alle 19.23 -0700, Ian Lance Taylor ha scritto:
> It's normal for the stage3 .o file to include debugging info and the
> stage2 .o file to not include it.  The comparison script will ignore
> that.  So it's normal for the stage3 .o file to be significantly
> larger.
> 
> Ian 

>From a quick look at the output of objdump -x, as far as I understand,
the difference is only debug info. 
I just built 4.4.6, and with it I am bootstrapping 4.5.0; we'll see what
happens. 

Do I have to install my own binutils? The system binutils are at 2.14. 
Thanks
Salvatore

References:
- 4.6.1 bootstrap failure on ia64
  - From: Salvatore Filippone
- Re: 4.6.1 bootstrap failure on ia64
  - From: Ian Lance Taylor
- Re: 4.6.1 bootstrap failure on ia64
  - From: Salvatore Filippone
- Re: 4.6.1 bootstrap failure on ia64
  - From: Ian Lance Taylor

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