From: Dan Gohman (gohmandj_at_[hidden])
Date: 2002-06-13 14:22:14
On Wed, Jun 12, 2002 at 12:08:04PM -0500, Rene Rivera wrote:
> Cool. I've just updated "features.jam" to include the "address-model"
> feature. And also split the "architecture" into "architecture" and
> "instruction-set". And added entries for MIPS to the architecture and
> instruction-set, using the names that GCC uses/gives.
> I also updated the "gcc-tools.jam" to use and generate the flags for MIPS as
> an example.
address-model looks good.
mips3 and mips4 are instruction sets; mips4 is a link-compatible superset of
mips3 containing extra instructions that some cpus don't support. I know
that other instruction sets on other architectures often have a similar
relationship. It would be nice to be able to express this in Boost.Build but
I don't know how it would look.
> >By the way, is there a standard way for a toolset to say that it doesn't
> >support a particular option? For example, MIPSpro doesn't support a 16-bit
> >address model.
> Not really... But take a look at what I did for gcc... it's a kludge, but it
> kinda works.
-- Dan Gohman gohmandj_at_[hidden]
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk