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: Target specific behaviour

From: NightStrike <nightstrike at gmail dot com>
To: "David Daney" <ddaney at avtrex dot com>
Cc: "Kevin André" <kevin dot andre at student dot ua dot ac dot be>, gcc-help at gcc dot gnu dot org
Date: Sat, 23 Feb 2008 17:04:59 -0500
Subject: Re: Target specific behaviour
References: <20d882600802230417i2cd920a0tacb63c556805cc32@mail.gmail.com> <47C06F10.70503@avtrex.com>

On 2/23/08, David Daney <ddaney@avtrex.com> wrote:
> >  So I was wondering: what is there in GCC
> > (except generating the actual assembler instructions) that is specific
> > for the target that GCC was configured for?
> >
> Look in the GCC sources in the gcc/config/* directories.  Each of these
> target specific directories contains code for GCC's target.  GCC's
> architecture is such that only a single target is allowed for any given
> instance of GCC.

Could you in theory configure one *build* of gcc to target multiple
platforms?  Something like this:

./configure --target=x86_64-pc-mingw32 --target=i686-pc-mingw32
--target=x86_64-pc-linux

And have the resulting 'make install' create a set of binaries
prefixed appropriately once for each target?

Follow-Ups:
- Re: Target specific behaviour
  - From: Brian Dessent

References:
- Target specific behaviour
  - From: Kevin AndrÃ
- Re: Target specific behaviour
  - From: David Daney

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