Re: [fpc-devel] FPC 3.2.2-RC1 release, now with working link!
> >> We have placed the first release candidate of the Free Pascal > >> Compiler version 3.2.2 on our ftp servers. > >> > >> You can help improve the upcoming 3.2.2 release by downloading and > >> testing this release. If you want you can report what you have done > >> here: http://wiki.freepascal.org/Testers_3.2.2 or in the maillist. > >> > > > > Test step 11 is "Run testsuite". The last time we were testing a > > relese candidate, the test suite had a small number of failures, > > but to a casual tester it was not clear what to do about it; which > > tests are expected to be failing, which are dealbreakers, etc. > > Should the test step offer more detail on how to react to or report > > test suite results? > > Those are regression tests, so test against the results of the latest > releases. ___ Great, thanks. Testing ongoing. I'm seeing frequent Access Violations when running programs of any complexity that have been compiled with "-B -O- -Oodfa,deadstore"... but this seems to have been happening already in 3.2.0, so not a regression. I don't see a bug for this yet, so I'll try to come up with a minimal reproducible. We'll need to warn users about this if it can't be fixed for 3.2.2. ~Kirinn ___ fpc-devel maillist - fpc-devel@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
Re: [fpc-devel] FPC 3.2.2-RC1 release, now with working link!
> Am 02.04.2021 um 14:01 schrieb Kirinn via fpc-devel > : > We have placed the first release candidate of the Free Pascal Compiler version 3.2.2 on our ftp servers. You can help improve the upcoming 3.2.2 release by downloading and testing this release. If you want you can report what you have done here: http://wiki.freepascal.org/Testers_3.2.2 or in the maillist. >>> >>> Test step 11 is "Run testsuite". The last time we were testing a >>> relese candidate, the test suite had a small number of failures, >>> but to a casual tester it was not clear what to do about it; which >>> tests are expected to be failing, which are dealbreakers, etc. >>> Should the test step offer more detail on how to react to or report >>> test suite results? >> >> Those are regression tests, so test against the results of the latest >> releases. ___ > > Great, thanks. Testing ongoing. > > I'm seeing frequent Access Violations when running programs of any > complexity that have been compiled with "-B -O- -Oodfa,deadstore"... > but this seems to have been happening already in 3.2.0, so not a > regression. I don't see a bug for this yet, so I'll try to come up with > a minimal reproducible. We'll need to warn users about this if it can't > be fixed for 3.2.2. -Oodeadstore is not really reliable yet.___ fpc-devel maillist - fpc-devel@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
Re: [fpc-devel] Public access of FPC features and settings
> Am 07.03.2021 um 15:12 schrieb Florian Klämpfl via fpc-devel > : > > Am 07.03.21 um 12:05 schrieb Alfred via fpc-devel: >> Hello, >> As a follow-up on a Lazarus feature request. >> Among other applications, Lazarus uses some hard-coded list that represent >> FPC features. Like supported MCU and boards. It would be (much) more >> convenient to parse the FPC output itself to supply this info. And that >> could be made easy by using XML as FPC output. >> Besides the above, I would welcome more features to be available through FPC >> itself. >> FPC uses system files, located in "compiler/systems". With all kinds of >> settings. Like alignment and calling convention and linker to use. >> FPC uses search-paths. Some user defined through fpc.cfg, some build-in. See >> all -F... compiler settings. >> It would be nice to be able to get info through FPC itself about these >> settings and paths. >> As maintainer of fpcupdeluxe, often I need to parse fpc.cfg by hand. Or look >> into a file like fpmkunit.pp to find the valid FPC targets. Or parse the >> Makefile to find all available subarchs when building a cross-compiler. >> For a start, I would favor a XML/JSON output of fpc -i. Would be very nice >> to use its output. > > I added a first experimental implementation in r48897. It does not cover full > -i, so far only to show how it could look like. Any comments? Meanwhile I completed it. So if somebody thinks it’s useful, the json output can be added as well. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
Re: [fpc-devel] Public access of FPC features and settings
On Fri, 2 Apr 2021, Florian Klämpfl via fpc-devel wrote: Am 07.03.2021 um 15:12 schrieb Florian Klämpfl via fpc-devel : Am 07.03.21 um 12:05 schrieb Alfred via fpc-devel: Hello, As a follow-up on a Lazarus feature request. Among other applications, Lazarus uses some hard-coded list that represent FPC features. Like supported MCU and boards. It would be (much) more convenient to parse the FPC output itself to supply this info. And that could be made easy by using XML as FPC output. Besides the above, I would welcome more features to be available through FPC itself. FPC uses system files, located in "compiler/systems". With all kinds of settings. Like alignment and calling convention and linker to use. FPC uses search-paths. Some user defined through fpc.cfg, some build-in. See all -F... compiler settings. It would be nice to be able to get info through FPC itself about these settings and paths. As maintainer of fpcupdeluxe, often I need to parse fpc.cfg by hand. Or look into a file like fpmkunit.pp to find the valid FPC targets. Or parse the Makefile to find all available subarchs when building a cross-compiler. For a start, I would favor a XML/JSON output of fpc -i. Would be very nice to use its output. I added a first experimental implementation in r48897. It does not cover full -i, so far only to show how it could look like. Any comments? Meanwhile I completed it. So if somebody thinks it’s useful, the json output can be added as well. Will do, thanks! Michael.___ fpc-devel maillist - fpc-devel@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
Re: [fpc-devel] Public access of FPC features and settings
Florian, it seems you missed a comment on that topic I wrote a while ago. There is also the need to have a tuple that matches controllertype to controllerunit to get rid of a big peace of duplicated code from cpuinfo.pas in lazarus. Lazarus needs to know which unit to include so that codetools can do their magic. In current implementation parts of controllertypes are duplicated in lazarus code. To get rid of this lazarus will not only need to know the available controllertypes, it will also need to have the mapping from controllertype tu unitname like this: * * in the xml. Example: ~/fpcupdeluxe-test/fpc/bin/aarch64-darwin/fpc -Tembedded -Parm -ix ... ... ... ... ... ... ... ... *...* * ** *... ... FPC Am 02.04.21 um 15:07 schrieb Michael Van Canneyt via fpc-devel: On Fri, 2 Apr 2021, Florian Klämpfl via fpc-devel wrote: Am 07.03.2021 um 15:12 schrieb Florian Klämpfl via fpc-devel : Am 07.03.21 um 12:05 schrieb Alfred via fpc-devel: Hello, As a follow-up on a Lazarus feature request. Among other applications, Lazarus uses some hard-coded list that represent FPC features. Like supported MCU and boards. It would be (much) more convenient to parse the FPC output itself to supply this info. And that could be made easy by using XML as FPC output. Besides the above, I would welcome more features to be available through FPC itself. FPC uses system files, located in "compiler/systems". With all kinds of settings. Like alignment and calling convention and linker to use. FPC uses search-paths. Some user defined through fpc.cfg, some build-in. See all -F... compiler settings. It would be nice to be able to get info through FPC itself about these settings and paths. As maintainer of fpcupdeluxe, often I need to parse fpc.cfg by hand. Or look into a file like fpmkunit.pp to find the valid FPC targets. Or parse the Makefile to find all available subarchs when building a cross-compiler. For a start, I would favor a XML/JSON output of fpc -i. Would be very nice to use its output. I added a first experimental implementation in r48897. It does not cover full -i, so far only to show how it could look like. Any comments? Meanwhile I completed it. So if somebody thinks it’s useful, the json output can be added as well. Will do, thanks! Michael. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel ___ fpc-devel maillist - fpc-devel@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
Re: [fpc-devel] Public access of FPC features and settings
> Am 02.04.2021 um 16:21 schrieb Michael Ring via fpc-devel > : > > Florian, it seems you missed a comment on that topic I wrote a while ago. > > You are right. The controller unit is written now like: ___ fpc-devel maillist - fpc-devel@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
Re: [fpc-devel] Public access of FPC features and settings
On Fri, 2 Apr 2021, Florian Klämpfl via fpc-devel wrote: Am 02.04.2021 um 16:21 schrieb Michael Ring via fpc-devel : Florian, it seems you missed a comment on that topic I wrote a while ago. You are right. The controller unit is written now like: Seems a quote is missing after the name= value ? Michael.___ fpc-devel maillist - fpc-devel@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
