Difference between revisions of "Open tasks"

From Lazarus wiki
Jump to navigationJump to search
(m68k and MIPS are supported nowadays)
 
(14 intermediate revisions by 8 users not shown)
Line 1: Line 1:
 +
{{Open tasks}}
 +
 
Here is a list of open tasks in FPC.
 
Here is a list of open tasks in FPC.
 +
 +
There is a special page about the [[Systems 2005]] fair in Munich, October 2005, regarding topics discussed between the FPC and Lazarus core developers.
  
 
== Compiler development ==
 
== Compiler development ==
  
* Port the m68k code generator to 1.9.x: [[M68k port]]
+
* Document the compiler
* Create a MIPS code generator for 1.9.x: [[MIPS port]]
+
* SSA framework
 +
* Instruction scheduler
 +
* Rework exception handling to "gcc style"
 +
* <strike>Port the m68k code generator to 2.3.x: [[M68k port]]</strike>
 +
* <strike>Create a MIPS code generator for 2.3.x: [[MIPS port]]</strike>
 
* For missing language constructs, see: [[Language related articles]]
 
* For missing language constructs, see: [[Language related articles]]
* Package support and dynamic library handling in general(partially language, but has a lot of implications)
+
* Package support and dynamic library handling in general (partially language, but has a lot of implications)
 
* (more) DWARF debugformat support. This might cut back the size of binaries with debuginfo
 
* (more) DWARF debugformat support. This might cut back the size of binaries with debuginfo
* Working regvar support for the 1.9.x port.
+
* Auto inlining
* debug {$packrecord C} with regard to 16 and 64-bit sizes.
 
* leafnode stackframereduction (and auto inlining?)
 
 
* improve PowerPC port:
 
* improve PowerPC port:
** improve AIX abi-compatibility (e.g., we don't pass records as the AIX abi prescribes)
+
** improve AIX abi-compatibility (e.g., we don't return records as the AIX abi prescribes)
** create a PPC-optimizer (if only a peephole optimizer for starters)
+
** improve the PPC-optimizer (only a peephole optimizer available)
** re-enable support for register variables (that's not really  PPC-specific, but the PPC will benefit a *lot* of that)  
 
 
* improve ARM port:
 
* improve ARM port:
 
** create a ARM-optimizer
 
** create a ARM-optimizer
Line 21: Line 26:
 
** optimize set operations
 
** optimize set operations
 
* improve SPARC port
 
* improve SPARC port
** fix code generator internal bugs
 
 
** write code optimizer
 
** write code optimizer
 
** improve RTL implementation
 
** improve RTL implementation
 +
* provide [[Localization|localization]] to other languages
  
 
Information about compiler development can be found here: [[Compiler development articles]]
 
Information about compiler development can be found here: [[Compiler development articles]]
Line 29: Line 34:
 
== RTL development ==
 
== RTL development ==
  
* port the 1.0.10 BeOS port to 1.9.x: [[BeOS port]]
+
* <strike>port the 1.0.10 BeOS port to 2.1.x: [[BeOS port]]</strike>
* port the 1.0.6/1.0.10 SunOS port to 1.9.x: [[SunOS port]] (combine with Sparc port)
+
* <strike>port the 1.0.6/1.0.10 SunOS port to 2.1.x: [[SunOS port]] (combine with Sparc port)</strike>
* port the 1.0.6/1.0.10 QNX port to 1.9.x: [[QNX port]]
+
* port the 1.0.6/1.0.10 QNX port to 2.3.x: [[QNX port]]
 
* Implement crossplatform 64-bit fileroutines
 
* Implement crossplatform 64-bit fileroutines
* ARM port and RTL more userfriendly. (need users/contributors/betatesters first)
+
* <strike>ARM port and RTL more userfriendly. (need users/contributors/betatesters first)</strike>
* improve MacOS X rtl:
+
* improve Mac OS X rtl:
 
** Port the missing RTL units (mainly text console handling)
 
** Port the missing RTL units (mainly text console handling)
** Create a Mac OS X installer package definition
+
** Improve support for the Mac Pascal dialect
** Try to create some kind of plug-in so the compiler can be called  from XCode and Project Builder
 
** Run the test suite and fix bugs
 
** Replace as many of my handwritten assembler routines with calls to  libc versions, as Apple is much better at writing fast ppc assembler  code than I am. Do the same for the generic math routines.
 
** Support the Apple dialect so we can use the Universal Interfaces
 
 
** Finish Classic Mac OS support  
 
** Finish Classic Mac OS support  
* create a WinCE rtl: [[WinCE port]]
+
* <strike>create a WinCE rtl: [[WinCE port]]</strike>
* The unix ports (including derivatives as BeOS and QNX) should have a way to be rerouted to libc instead of syscalls. (Done, 1.9.2)
 
  
 
== FCL development ==
 
== FCL development ==
Line 58: Line 58:
 
== IDE development ==
 
== IDE development ==
  
* The text mode IDE needs currently a maintainer, have a look at this page for more information: [[Textmode IDE developement]]
+
* The text mode IDE needs currently a maintainer, have a look at this page for more information: [[Textmode IDE development]]
 
* there are a lot of bugs to fix, have a look at the bug repository: http://www.freepascal.org/bugs.html
 
* there are a lot of bugs to fix, have a look at the bug repository: http://www.freepascal.org/bugs.html
* get it working with [[FVISION]]
+
* <strike>get it working with [[FVISION]]</strike>
* Related to this is debugging the platform dependant parts, the former "API" (video, mouse,keyboard). Help from platform maintainers can be expected. (more about isolating bugs than solving in these units)
+
* Related to this is debugging the platform dependant parts, the former "API" (video, mouse,keyboard). Help from platform maintainers can be expected. (more about isolating bugs than solving in these units) See also [[KVM API and Crt future]]
 +
* DWARF support for the IDE
 +
* Colour selection dialogue compatible as available in TP/BP IDE (previously used code was not clean from copyright point of view)
  
 
== Demoes ==
 
== Demoes ==
Line 69: Line 71:
 
== Misc ==
 
== Misc ==
  
 +
* Packaging system
 
* some more tasks are listed on http://www.freepascal.org/future.html near the bottom
 
* some more tasks are listed on http://www.freepascal.org/future.html near the bottom
 +
 +
[[Category:FPC development]]

Latest revision as of 22:13, 16 January 2020

English (en)

Here is a list of open tasks in FPC.

There is a special page about the Systems 2005 fair in Munich, October 2005, regarding topics discussed between the FPC and Lazarus core developers.

Compiler development

  • Document the compiler
  • SSA framework
  • Instruction scheduler
  • Rework exception handling to "gcc style"
  • Port the m68k code generator to 2.3.x: M68k port
  • Create a MIPS code generator for 2.3.x: MIPS port
  • For missing language constructs, see: Language related articles
  • Package support and dynamic library handling in general (partially language, but has a lot of implications)
  • (more) DWARF debugformat support. This might cut back the size of binaries with debuginfo
  • Auto inlining
  • improve PowerPC port:
    • improve AIX abi-compatibility (e.g., we don't return records as the AIX abi prescribes)
    • improve the PPC-optimizer (only a peephole optimizer available)
  • improve ARM port:
    • create a ARM-optimizer
    • optimize helper routines some can use libgcc if linked against libc
    • optimize concatcopy code generation
    • optimize set operations
  • improve SPARC port
    • write code optimizer
    • improve RTL implementation
  • provide localization to other languages

Information about compiler development can be found here: Compiler development articles

RTL development

  • port the 1.0.10 BeOS port to 2.1.x: BeOS port
  • port the 1.0.6/1.0.10 SunOS port to 2.1.x: SunOS port (combine with Sparc port)
  • port the 1.0.6/1.0.10 QNX port to 2.3.x: QNX port
  • Implement crossplatform 64-bit fileroutines
  • ARM port and RTL more userfriendly. (need users/contributors/betatesters first)
  • improve Mac OS X rtl:
    • Port the missing RTL units (mainly text console handling)
    • Improve support for the Mac Pascal dialect
    • Finish Classic Mac OS support
  • create a WinCE rtl: WinCE port

FCL development

  • New classes
  • debug classes
  • more database support and abstraction

FVISION development

  • getting it fully up to speed and compatible with TV
  • endianness and 64-bit clean work.

IDE development

  • The text mode IDE needs currently a maintainer, have a look at this page for more information: Textmode IDE development
  • there are a lot of bugs to fix, have a look at the bug repository: http://www.freepascal.org/bugs.html
  • get it working with FVISION
  • Related to this is debugging the platform dependant parts, the former "API" (video, mouse,keyboard). Help from platform maintainers can be expected. (more about isolating bugs than solving in these units) See also KVM API and Crt future
  • DWARF support for the IDE
  • Colour selection dialogue compatible as available in TP/BP IDE (previously used code was not clean from copyright point of view)

Demoes

  • we can nearly always use more demoes.

Misc