Sorry if what I'm asking is dumb.
I'd like to get started helping to develop SDCC. However the first thing
is that I should understand as well as possible how its internal works.
I downloaded the sources and managed to compile them just fine, however
I'd like to know how I can find documentatio
Le 19.12.2013 11:12, Dave McGuire a écrit :
>Well, GCC supports AVR because people wrote AVR support into GCC. ;)
> AVR is a bit more "compiler friendly" than, say, the Z80.
Well, I'm not familiar with Z80, but by "compiler friendly" I guess this
basically means RISC right ? Each operation ca
Hello guys,
This might be out of topic, but while this was mentionned, I've asked me
this question a few times so I hope somebody has an answer.
How comes AVR can be targetted by gcc at all ? AVR might be RISC, true,
but it is a 8-bit architecture, and the standard gcc compiler is
optimized for
Ok,
therefore using automatic bankswitching should be done with caution, as
it could potentially result in a ridiculous number of unnecessary BBR
writes - say if I access a lot of variables in bankswitched area and
call functions that doesn't touch BBR.
For interrupts yeah it makes complete sen
Hello,
it really sounds incredible SDCC can do this automatically !
What if you call a function that itself call a function that will affect
the bank switching ? Can SDCC detect such cases and do all the
bank-switching automatically ?
This really sounds incredible. If SDCC can do all this, it's o
Le 16.03.2013 14:28, Borut Ražem a écrit :
> This is probably because the parentheses are used for expressions. In
> this case use of square brackets seems more appropriate to me. But I'm
> only guessing...
Yes, but it's not hard to test if an expression is itself fully
surrounded by parenthesis
Le 16.03.2013 01:13, Borut Ražem a écrit :
> Helo Jonathan,
>
> sdas and sdld are actually a fork of Alan Baldwin's AS assembler
> (see http://shop-pdp.net/ashtml/as.htm) with some sdcc related
> modifications. Only the targets supported by sdcc are included in
> sdas/sdld but the documenta
Hello everyone,
Without much surprise, I am unable to do contribute to SDCC during my
free time.
My plan is now to attempt to get, with my master project next year
(2014), a project where I'll do a 6502 and 65C816 port of SDCC, along
with some hardware simulation of both processors in order to
Le 05.09.2012 12:52, Groepaz a écrit :
>
> err, no - the PCE uses a NEC "HuC6280" CPU, which is "6502 like", but contains
> a bunch of rather specific extension which can not be found in any other CPU
> (eg block copy, paging support)
>
> an actual 65C02 can be found in the NES aka famicom :)
>
> t
Le 05.09.2012 09:32, Sebastien Lorquet a écrit :
> Hello,
>
> It depends on the port.
>
> [...]
>
> For your port, you can have both (as for mcs51): functions flagged with
> __reentrant will use the stack convention, the others will use the overlay
> convention.
>
Yes, this sounds like the way to
7;m sorry for the very long message. Hopefully someone can point
me to the "official" procedure to make a SDCC port while I'm studying
the internals of SDCC.
Regards.
Le 03.09.2012 06:33, Philipp Klaus Krause a écrit :
> On 03.09.2012 06:24, Masur Jonathan wrote:
>
> I suggest y
Hello,
I am an active developer on the Nintendo Entertainment System platform,
and currently I write all my programs in assembly language. Because this
is long and ask for more work than writing programs in C, I am looking
forward for a C compiler which can output optimized 6502 machine code.
12 matches
Mail list logo
