This is the mail archive of the gcc@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: Mainline bootstrap failure in toplev.c

From: Wolfgang Bangerth <bangerth at ices dot utexas dot edu>
To: Zack Weinberg <zack at codesourcery dot com>
Cc: Richard Henderson <rth at redhat dot com>, Andrew Pinski <pinskia at physics dot uc dot edu>, gcc at gcc dot gnu dot org, rth at gcc dot gnu dot org
Date: Wed, 1 Dec 2004 14:12:30 -0600
Subject: Re: Mainline bootstrap failure in toplev.c
References: <200412010932.02561.bangerth@ices.utexas.edu> <20041201172009.GC12839@redhat.com> <87oehdkiyh.fsf@codesourcery.com>

> Uh, why is linux/compiler.h getting dragged into the compilation of a
> user space program in the first place?

Through the following chain:

  signal.h
  bits/sigcontext.h
  asm/sigcontext.h
  linux/compiler.h

The redefinition of "inline" is guarded like so:
  #if __GNUC_MINOR__ >= 1 && defined __KERNEL__
  # define inline		__inline__ __attribute__((always_inline))
  # define __inline__	__inline__ __attribute__((always_inline))
  # define __inline	__inline__ __attribute__((always_inline))
  #endif

I have no idea, however, why __KERNEL__ is apparently set during gcc 
bootstrapping.

W.

-------------------------------------------------------------------------
Wolfgang Bangerth              email:            bangerth@ices.utexas.edu
                               www: http://www.ices.utexas.edu/~bangerth/

Follow-Ups:
- Re: Mainline bootstrap failure in toplev.c
  - From: Richard Henderson

References:
- Mainline bootstrap failure in toplev.c
  - From: Wolfgang Bangerth
- Re: Mainline bootstrap failure in toplev.c
  - From: Richard Henderson
- Re: Mainline bootstrap failure in toplev.c
  - From: Zack Weinberg

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