On Wed, 2012-03-21 at 15:12 -0700, Ian Lance Taylor wrote:
> I can understand why you are doing this. However, you should be aware
> that the compiler internals changed significantly in version 4.0. Time
> spent working on detailed optimizations of gcc 3.4 is almost certainly
> time wasted. Walk
James Murray writes:
> However, the generated code isn't as good as the output from 3.3.6. I
> swapped back to unpatched 3.4.4 and compared with unpatched 3.3.6.
I can understand why you are doing this. However, you should be aware
that the compiler internals changed significantly in version 4.
On Wed, 2011-01-26 at 14:55 +, James Murray wrote:
> On Wed, 2011-01-26 at 15:40 +0100, Richard Guenther wrote:
>
> > Stephane Carrez is listed as maintainer of the port, so he should
> > know how to contribute fixes to the port upstream.
> >
> Yes, but as I said... he is no longer active on
On 01/26/2011 03:55 PM, James Murray wrote:
On Wed, 2011-01-26 at 15:40 +0100, Richard Guenther wrote:
Stephane Carrez is listed as maintainer of the port, so he should
know how to contribute fixes to the port upstream.
Yes, but as I said... he is no longer active on this port. His last
publ
On Wed, 2011-01-26 at 15:40 +0100, Richard Guenther wrote:
> Stephane Carrez is listed as maintainer of the port, so he should
> know how to contribute fixes to the port upstream.
>
Yes, but as I said... he is no longer active on this port. His last
published contributions are 4+ years ago.
Jam
On Wed, Jan 26, 2011 at 3:36 PM, James Murray wrote:
> Unsure if this is the right place to mention this, so excuse me if it is
> not.
>
> The 68hc11/68hc12 port page http://www.gnu.org/software/m68hc11/
> is very out of date and was last updated in October 2003.
>
> The creator of that port Steph
