This is the mail archive of the 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: [PATCH] powerpc-eabi board support for Xilinx

Nathan Froyd wrote:
On Tue, Nov 04, 2008 at 04:34:53PM -0500, Michael Meissner wrote:
On Wed, Oct 22, 2008 at 10:58:00AM -0700, Michael Eager wrote:
The attached patch does two things:  First, it creates a
--with-board=<board> option which will set the default
target board for a build with --target=powerpc-*-eabi.  The
user can still override this with a -m<board> option.  Second,
it creates -mxilinx, which specifies target options for
using various Xilinx PowerPC development boards.
I thought most of the ppc board packages had moved away from adding -m<option>,
and instead were using specs files or shell script wrappers to add the
particular libraries that were used.  This way they could use an off the shelf
compiler and not have to add libraries.  I must admit to not really knowing
that part of the market these days.

For what it's worth, we use linker scripts (specified by the user, but by-and-large provided by us; the user is welcome to create board-specific linker scripts, of course) to handle most of the bits that the -m<board> options currently handle. (Libraries and linker scripts bits seem to be all that -m<board> is used for anyway, and linker scripts can fill in for both.)

Linker scripts partially address the user's needs, but not completely. Like specifying -m<board>, they require that the user specify this on every gcc invocation that generates an executable.

I will resubmit the patch and remove the --with-board configure
option and move the default into a target-specific header file
similar to what is done for --target=powerpc-eabisim.

-- Michael Eager 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077

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