Recent changes to Project ideas

Project ideas modified by Philipp Klaus Krause

Philipp Klaus Krause — Wed, 30 Oct 2024 14:25:22 -0000

--- v27
+++ v28
@@ -94,8 +94,3 @@
 --

 The Microchip PIC devices are still popular. SDCC has had "in-development" backends for them for quite a while, but they never became stable. Also, the backends depend on mostly unmaintained upstream gputils. There are many possible improvements, that could bring the pic14 and pic16 backends closer to being stable. This requires some knowledge of the PIC devices. It probably wouldn't be a good GSoC project, since we don't have a mentor familiar with PIC.
-
-Git mirror (help wanted)
---
-
-We have an experimental git repo at sf/p/sdcc/git-mirror with a provisional_trunk branch that is supposed to follow svn/trunk. Also, we have a semi/un-official mirror over at https://codeberg.org/sdcc/code. To make any sense for a broader circle of users and contributors, we need a mechanism that updates it automatically. There is some testing in progress, once it works (and nobody intervenes with better plans), we can make it official. (No, SDCC is not going to "switch", "migrate" or "upgrade" to git, git*\*b or anything similar anytime soon, please browse the mailing list archive for more background.)

Project ideas modified by Philipp Klaus Krause

Philipp Klaus Krause — Wed, 30 Oct 2024 14:24:28 -0000

--- v26
+++ v27
@@ -22,7 +22,6 @@
 * https://sourceforge.net/p/sdcc/feature-requests/332/
 * https://sourceforge.net/p/sdcc/feature-requests/450/
 * https://sourceforge.net/p/sdcc/feature-requests/654/
-* https://sourceforge.net/p/sdcc/feature-requests/23/


 Merge the sdas fork of asxxxx 3 with current upstream asxxxx 5.

Project ideas modified by Felix

Felix — Mon, 13 Nov 2023 16:38:31 -0000

--- v25
+++ v26
@@ -99,4 +99,4 @@
 Git mirror (help wanted)
 --

-We have a semi/un-official git code repository over at https://codeberg.org/sdcc/code, that follows svn/trunk.  To make any sense for a broader circle of users and contributors, we need a mechanism that updates it automatically. Then we can make it official. Maybe the repo should be hosted here at sf, together with an update hook (if possible)... speak to us if you use git and know the ropes. (No, SDCC is not going to "switch", "migrate" or "upgrade" to git, git*\*b or anything similar anytime soon, please browse the mailing list archive for more background.)
+We have an experimental git repo at sf/p/sdcc/git-mirror with a provisional_trunk branch that is supposed to follow svn/trunk. Also, we have a semi/un-official mirror over at https://codeberg.org/sdcc/code. To make any sense for a broader circle of users and contributors, we need a mechanism that updates it automatically. There is some testing in progress, once it works (and nobody intervenes with better plans), we can make it official. (No, SDCC is not going to "switch", "migrate" or "upgrade" to git, git*\*b or anything similar anytime soon, please browse the mailing list archive for more background.)

Project ideas modified by Felix

Felix — Sat, 11 Nov 2023 15:10:40 -0000

--- v24
+++ v25
@@ -99,4 +99,4 @@
 Git mirror (help wanted)
 --

-We have a semi/un-official git code repository over at https://codeberg.org/sdcc/code, that follows svn/trunk.  To make any sense for a broader circle of users and contributors, we need a mechanism that updates it automatically. Then we can make it official. Maybe the repo should be hosted here at sf, together with an update hook (if possible)... speak to us if you use git and know the ropes.
+We have a semi/un-official git code repository over at https://codeberg.org/sdcc/code, that follows svn/trunk.  To make any sense for a broader circle of users and contributors, we need a mechanism that updates it automatically. Then we can make it official. Maybe the repo should be hosted here at sf, together with an update hook (if possible)... speak to us if you use git and know the ropes. (No, SDCC is not going to "switch", "migrate" or "upgrade" to git, git*\*b or anything similar anytime soon, please browse the mailing list archive for more background.)

Project ideas modified by Felix

Felix — Fri, 10 Nov 2023 12:31:38 -0000

--- v23
+++ v24
@@ -95,3 +95,8 @@
 --

 The Microchip PIC devices are still popular. SDCC has had "in-development" backends for them for quite a while, but they never became stable. Also, the backends depend on mostly unmaintained upstream gputils. There are many possible improvements, that could bring the pic14 and pic16 backends closer to being stable. This requires some knowledge of the PIC devices. It probably wouldn't be a good GSoC project, since we don't have a mentor familiar with PIC.
+
+Git mirror (help wanted)
+--
+
+We have a semi/un-official git code repository over at https://codeberg.org/sdcc/code, that follows svn/trunk.  To make any sense for a broader circle of users and contributors, we need a mechanism that updates it automatically. Then we can make it official. Maybe the repo should be hosted here at sf, together with an update hook (if possible)... speak to us if you use git and know the ropes.

Project ideas modified by Philipp Klaus Krause

Philipp Klaus Krause — Wed, 26 Jul 2023 08:16:36 -0000

--- v22
+++ v23
@@ -11,12 +11,6 @@

 * https://sourceforge.net/p/sdcc/feature-requests/593/

-Generalized constant propagation.
---
-
-Some relevant tickets:
-
-* https://sourceforge.net/p/sdcc/feature-requests/364/

 Improve standard compliance
 --

Project ideas modified by Philipp Klaus Krause

Philipp Klaus Krause — Tue, 01 Mar 2022 15:44:55 -0000

--- v21
+++ v22
@@ -93,8 +93,8 @@
 Documentation improvement usability glue stuff
 --

-The SDCC manul and documentationhas mstly been written on-the-go by SDCC developers; sometimes outdated bits haven't been cleaned up in time until years later. Many SDCC users use Windows, while developers mostly use GNU/Linux. Many SDCC users use it from an IDE, but most developers don't.
-This has resulted in a less-than-optimal state of documentation for mayn users.
+The SDCC manul and documentation has mostly been written on-the-go by SDCC developers; sometimes outdated bits haven't been cleaned up in time until years later. Many SDCC users use Windows, while developers mostly use GNU/Linux. Many SDCC users use it from an IDE, but most developers don't.
+This has resulted in a less-than-optimal state of documentation for many users.
 This could include finding usability / documentation issues e.g. by cognitive walkthroughs and fixing the issues found, looking into support of SDCC in IDEs and posibly updating the support (e.g. Code::Blocks has relatively up-to-date support of SDCC, but could still be improved, while the SDCC Eclipse plugin is unmaintained, and apparenly doesn't work for many users).

 PIC improvement (probably not for GSoc)

Project ideas modified by Philipp Klaus Krause

Philipp Klaus Krause — Tue, 09 Mar 2021 15:52:26 -0000

--- v20
+++ v21
@@ -81,7 +81,7 @@
 A modern preprocessor
 --

-Ihe current SDCC preprocessor is a fork of an old GNU preprocessor, 4.6.3. To be ready for modern requirements, such as upcoming C2X, it would be good to have a preprocessor, e.g. by merging the few additional features SDCC requires into a current GCU preprocessor to use for SDCC.
+Ihe current SDCC preprocessor is a fork of an old GNU preprocessor, 4.6.3. To be ready for modern requirements, such as upcoming C2X, it would be good to have a preprocessor, e.g. by merging the few additional features SDCC requires into a current GCC preprocessor to use for SDCC.

 double
 --

Project ideas modified by Philipp Klaus Krause

Philipp Klaus Krause — Mon, 17 Feb 2020 13:10:48 -0000

--- v19
+++ v20
@@ -100,4 +100,4 @@
 PIC improvement (probably not for GSoc)
 --

-The Microchip PIC devices are still popular. SDCC has had "in-development" backends for them for quite a while, but they never became stable. Also, thebackends depend on mostly unmaintained upstream gputils. There are many possible improvements, that could bring the pic14 and pic16 backends closer to being stable. This requires some knowledge of the PIC devices. It probably wouldn't be a good GSoC project, since we don't have mentor familiar with PIC.
+The Microchip PIC devices are still popular. SDCC has had "in-development" backends for them for quite a while, but they never became stable. Also, the backends depend on mostly unmaintained upstream gputils. There are many possible improvements, that could bring the pic14 and pic16 backends closer to being stable. This requires some knowledge of the PIC devices. It probably wouldn't be a good GSoC project, since we don't have a mentor familiar with PIC.

Project ideas modified by Philipp Klaus Krause

Philipp Klaus Krause — Tue, 04 Feb 2020 17:20:05 -0000

--- v18
+++ v19
@@ -97,3 +97,7 @@
 This has resulted in a less-than-optimal state of documentation for mayn users.
 This could include finding usability / documentation issues e.g. by cognitive walkthroughs and fixing the issues found, looking into support of SDCC in IDEs and posibly updating the support (e.g. Code::Blocks has relatively up-to-date support of SDCC, but could still be improved, while the SDCC Eclipse plugin is unmaintained, and apparenly doesn't work for many users).

+PIC improvement (probably not for GSoc)
+--
+
+The Microchip PIC devices are still popular. SDCC has had "in-development" backends for them for quite a while, but they never became stable. Also, thebackends depend on mostly unmaintained upstream gputils. There are many possible improvements, that could bring the pic14 and pic16 backends closer to being stable. This requires some knowledge of the PIC devices. It probably wouldn't be a good GSoC project, since we don't have mentor familiar with PIC.