Am 27.06.25 um 12:15 schrieb Borleis Jürgen via Sdcc-user:
Hi all,
I'm trying to run the "sdcdb" with a project for an 8051 CPU.
My environment:
OS: Linux
SDCDB: 0.9
SDCC :
mcs51/z80/z180/r2k/r2ka/r3ka/sm83/tlcs90/ez80_z80/z80n/r800/ds390/pic16/pic14/TININative/ds400/hc08/s08/stm8/pdk13/pdk14/
Good evening!
Following up on last Friday's developer meeting, I am pleased to
announce that, in addition to our slides*, the full transcripts of our
presentations* and subsequent discussions are now also available online,
and can be studied by all those that would have been interested in
par
We managed to get some footage, but the audio quality of the digital
photo camera's internal microphone leaves a lot to be desired and the
camera angle is not ideal, either.
It should be sufficient for a full transcript, though.
P.S.: The talks started at 14:15 CEST. I have a suspicion that you w
Hi!
Am 17.08.23 um 22:13 schrieb Michael A Hawkins:
Hello SDCC users,
I am sure this has been discussed before. So I apologize in advance for
repeating it.
With assembler, you can test for a reg/mem operation over/under flow by
checking the carry flag.
So for C, when overflows are involved, I
, 23 Apr 2023 at 20:53, Benedikt Freisen mailto:b.frei...@gmx.net>> wrote:
Good evening!
Both PIC ports are officially unmaintained. They have stability issues.
Unless you need the PIC ports, the path of least resistance is to simply
disable them, which hopefully solves the pro
Good evening!
Both PIC ports are officially unmaintained. They have stability issues.
Unless you need the PIC ports, the path of least resistance is to simply
disable them, which hopefully solves the problem. The manual lists the
relevant command line switches.
Greetings,
Benedikt
Am 22.04.23
If an appropriate libsdcc.lib exists somewhere in the directory tree,
this could be a linker path issue, presumably fixable via command line.
If not, the install package might be broken or the library has not been
compiled for some other reason.
Note that the PIC targets are officially unmaintaine
Hi!
Am 24.09.22 um 14:19 schrieb Nano:
Hi !
I got a codebase to build a gameboy ROM that was using sdcc some years
ago. Using the latest version of sdcc I can’t compile my source files
using `-mgbz80`, giving me this error : `error 131: cannot generate code
for target 'gbz80'`. I was wondering
Am 10.09.22 um 20:44 schrieb Richard Hodges:
On 9/10/22 12:32 PM, Benedikt Freisen wrote:
Hi!
Silly question: Does anything speak against using the predefined
__SDCCCALL macro that -- if present -- specifies the ABI version?
Sorry, I accidentally replied to the sender and not the list.
I
Hi!
Silly question: Does anything speak against using the predefined
__SDCCCALL macro that -- if present -- specifies the ABI version?
Am 10.09.22 um 20:06 schrieb Richard Hodges:
Hi, all.
I am finally getting to update my inline assembly for the new calling
version, started in 4.2 It is impor
Good morning!
Am 21.08.22 um 07:27 schrieb Michael Havenga:
Morning Everyone,
Would it be wrong in saying there is some level of renewed interest in
the PIC support and if the automated testing has been reviewed could
that potentially lead to a release at some point ?
Have a great day.
Michae
Hi Michael!
Am 17.08.22 um 21:41 schrieb Michael Havenga:
Hi Everyone,
I hope all are well.
Is there perhaps a resource that details what incomplete pic support
means, and what is on the to-do list?
Also, is there a dev actively working on the PIC support?
Have a great day!
Michael A Haveng
What about an additional pre-processing stage that transforms syntax
variant 1 to variant 2?
It could turn
__asm
add a,b
add a,c
__endasm
into
__asm__(
"add a,b\n"
"add a,c\n"
)
Another option would be to rely on a mechanism similar to C++11-style
raw string literals (i.e. R"")
The renaming was actually discussed rather extensively over the course
of about a year, albeit apparently only on the developer mailing list.
The actual renaming then took place in early December.
If you genuinely need the old target specific macros, you could use a
compatibility header via pre-in
Am 01.04.22 um 16:26 schrieb Tony Pavlov via Sdcc-user:
> Dear SDCC devs,
>
> can you please tell me, why target was renamed from gbz80 to sm83?
> who's brilliant idea? now we have to rework all gbdk-2020 build
> subsystem and that will definitely affect a lot of projects.
>
> WHAT FOR?!
>
There i
I cannot help with the overlaying issue, but when it comes to linker
output, switching to elf looks like the most obvious potential solution.
Greetings,
Benedikt
Am 20.02.22 um 13:15 schrieb Tony Pavlov via Sdcc-user:
> [...]
> ps: Not related with that problem, but another notice. SDLD linker is
Hi!
Am 31.10.21 um 13:00 schrieb Alan Cox:
> [...]
> If anyone is going to do any of this can I put in a plea to also allow
> the object files to be recognized if ending ".o". The weird, non-standard
> naming is the biggest single problem I hit because it breaks all the Make
> implied rules and th
Am 16.09.21 um 19:26 schrieb Ian Molton:
> Hi folks,
>
> I don't have a ton of experience with compilers, but I'm hitting
> problems with the PIC backend in SDCC - notably I've hit the issue of
> static local variables not being properly handled.
>
> I'd like to get involved - maybe take on maintai
Good afternoon!
To the best of my knowledge, the SDCC project does not currently have
any active developers with experience with the PIC architecture and the
PIC backends, which is why the PIC backends have been largely
unmaintained for about a decade.
The most recent release made that official an
Since a failed static assertion typically means that the program is
broken, I believe that turning the diagnostic warning into an error is
warranted.
Other warnings typically just mean that something _might_ go wrong, but
does not have to.
The only practical use case for a static assertion warning
20 matches
Mail list logo
