This is the mail archive of the
mailing list for the binutils project.
Re: 68hc11/12/s12x/xgate patch
- From: James Murray <jsm at jsm-net dot demon dot co dot uk>
- To: binutils at sourceware dot org
- Date: Tue, 13 Mar 2012 20:27:52 +0000
- Subject: Re: 68hc11/12/s12x/xgate patch
- References: <1298845471.12108.12.camel@jsm2> <1299515895.3262.1.camel@jsm2> <4D7F247D.firstname.lastname@example.org> <1300201861.20997.3.camel@jsm2> <1324419607.8652.84.camel@jsm2> <CABZhLO-Ye-G1nYW1eqpdjnYG1W4zaKq+TvgzFBebJk4ash5mtg@mail.gmail.com> <1324423375.8652.94.camel@jsm2> <4EF36049.email@example.com> <CABZhLO_RKXkcKRGH_b-f_iVYppcgBQ3XBf9STWjZeTCwrQJhzQ@mail.gmail.com> <1324575421.2430.42.camel@jsm2> <1325800936.20629.53.camel@jsm2> <4F0C4DFE.firstname.lastname@example.org> <1330300482.15684.10.camel@jsm2> <1331564819.2407.61.camel@jsm2> <CABZhLO_=6t=8EV5UcKN5LUqz0ZHBjQOqMZQhzNhx2V+HXEmewQ@mail.gmail.com>
On Mon, 2012-03-12 at 16:26 +0100, Fred Cooke wrote:
> Two things, for now:
> 1) Am I correct in saying that this is still one monolithic patch that
> makes multiple changes to the port?
Yes it is. Go ahead and take a look.
> 2) Am I correct in saying that this is still comprised mostly of a
> two-architectures-in-one-port code change?
Most of the patch is actually testsuite changes, due in part to revised
objdump output but also bringing m68hc11 up to date so that "make check"
works correctly. There are additional testcases for the newly added S12X
and XGATE functions.
Between the lines, it looks like you are referring to your earlier
binutils question "Supporting more than one CPU with the same gas
There are surely pros and cons to either method.
With the approach I took, only a single toolchain is required and there
is one linker. There are no devices currently that contain XGATE and any
other architecture other than hcs12 in production, nor are there any
currently mooted developments that the public are aware of.
With the approach that you appear to be advocating, two sets of tools
need to be built and installed. However, the XGATE target (as presented
by Sean) is not self-sufficient and relies on changes to the linker in
the m68hc11 target to support linking symbols within XGATE. Overall that
seems to complicate matters without offering any real advantage.