From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?iso-8859-1?B?R+Fib3IgTOlu4XJ0?= Subject: Re: SDCC porting feasibility study, part 1: the assembler Date: Mon, 27 Feb 2012 11:05:15 +0100 Message-ID: <20120227100515.GE27951@vega.lgb.hu> References: Reply-To: lgb@lgb.hu Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-8086-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="iso-8859-1" To: Brad Normand Cc: linux-8086@vger.kernel.org Re, On Sun, Feb 26, 2012 at 06:18:55PM -0600, Brad Normand wrote: > I've started looking at SDCC to try and get an idea how easy it is to > port this to target 8086. Maybe a bit off-topic, but: Hmm, I had a bad experience with SDCC with Z80 as target. Maybe I was not so smart, but I couldn't make it emit RODATA like stuff, it just ge= nerated Z80 code (!) to store data, instead of just the data. I just mention it, because it can be interesting problem for other targ= ets too. Since the problem is quite "funny", I assume it was only my mistake tha= t I left some option which would told SDCC not to do that, though ... etc. --- - G=E1bor -- To unsubscribe from this list: send the line "unsubscribe linux-8086" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html