Re: [fpc-devel] I've asked this before, but perhaps I wasn't specific enough that time: what do ...

Hi! 19.12.2021 19:28, J. Gareth Moreton via fpc-devel: To throw my hat into the ring, I'd be willing to help out with developing some library routines. I did experiment once with using a truncated and factorised MacLaurin series to calculate Double-precision sin and cos simultaneously in

Re: [fpc-devel] I've asked this before, but perhaps I wasn't specific enough that time: what do ...

Hi! 19.12.2021 12:33, Florian Klämpfl via fpc-devel: And the main obstacle for 80 bit softfloat support are the library routines (log, exp etc.). Just out of curiosity, couldn't bochs' x87 fpu implementation be of some use here? It is approx 12k of C code and it is LGPL. Supposedly it is not

Re: [fpc-devel] Building trunk of today fails on Windows: Error: Invalid DLL C:\WINDOWS\system32\common.dll, invalid header size

Hi, 23.08.2021 0:46, Bart via fpc-devel: I have now finally resorted to that. Wrote a simple program to do that for me (no sed on windows). Just in case: http://gnuwin32.sourceforge.net/packages/sed.htm Regards, Nikolai Then adjusted my build script to run that program, build fpc, then

Re: [fpc-devel] (ref types / circles) Re: Defer keyword

Hi Martin, 07.05.2021 2:41, Martin Frb via fpc-devel: On 07/05/2021 01:36, Nikolai Zhubr via fpc-devel wrote: Indeed. However, unfortunately classes are substantially different in that they can cause reference circles, You can already cause ref circles, no classes needed. Yes, records

Re: [fpc-devel] Defer keyword

Hi, 07.05.2021 1:32, Ryan Joseph via fpc-devel: [...] it's kind of frustrating that we have ref counted types but that isn't extended to classes. Indeed. However, unfortunately classes are substantially different in that they can cause reference circles, which then cause damage to ref

Re: [fpc-devel] Compiler message colour scheme

Hi! 25.11.2020 1:52, Tomas Hajny via fpc-devel: On 2020-11-24 19:17, J. Gareth Moreton via fpc-devel wrote: Sorry for being a bit slow - I've been doing my own work on x86. I gave your patch (and new file) a test run on x86_64-win64, and that seems to work fine. At least the warning messages

Re: [fpc-devel] Minor heads-up

Hi, 09.08.2020 20:03, J. Gareth Moreton: Hmmm, that's a good idea! Silly question... what does OSS mean?! Open-Source Software, presumbly? :) Regards, Nikolai Gareth aka. Kit ___ fpc-devel maillist - fpc-devel@lists.freepascal.org

Re: [fpc-devel] reference/pointer to class function/constructor ?

Hi, 20.02.2020 10:21, Harald Houppermans via fpc-devel: [...] Now I need a type to the initialize function which is a class function, I simply tried: type Tinitializer = class function; // this don't work in Delphi I also tried: Tinitializer = ^class function; // this don't work in Delphi.

Re: [fpc-devel] Linux Binary - Socket Output affected by SystemCtl, HELP!

Hi! 29.01.2020 19:04, Ozz Nixon via fpc-devel: cat /etc/test.txt ls -alrt /etc/test.txt -rw-r--r-- 1 root root 0 Jan 29 10:54 /tmp/test.txt Make sure there is no naming confusion (such as e.g. /tmp/test.txt and /etc/test.txt unintentionally intermixed) Another point is that a binary

Re: [fpc-devel] Linux Binary - Socket Output affected by SystemCtl, HELP!

Hi! 29.01.2020 18:07, Ozz Nixon via fpc-devel: 1. My code does not directly interact with any environment variables. Ok. ExecStart=/usr/local/bin/coderunner2 I'd suggest, as a quick and horrible temporary hack/test, replace this direct binary call with a shell wrapper, lets name it e.g.

Re: [fpc-devel] inline... and philosophy

08.11.2019 16:28, J. Gareth Moreton: [...] No gain? Wow, is whole-program optimisation that underperforming? Given the bloated size of FPC's binaries compared to, say, what a mainstream C++ compiler than do, I would have thought that there could be a lot Keep in mind that pretty much any tiny

Re: [fpc-devel] moved project from CentOS to a new install of CentOS...

Hi Ozz, 28.07.2019 22:02, Ozz Nixon: /usr/bin/ld: BFD version 2.20.51.0.2-5.42.el6 20100205 internal error, This binutils version is likely too old, and because C6 is getting close to EOL, I'd not count on someone fixing this ld bug. I recently had to update 2.24 to 2.30 (on opensuse) to

Re: [fpc-devel] FPC 3.0.4 ld error on opensuse 13.2

Hi, 09.07.2019 22:32, Florian Klämpfl: /usr/bin/ld: /usr/lib64/fpc/3.0.4/units/x86_64-linux/rtl/prt0.o: unrecognized relocation (0x2a) in section `.text' [...] As windows uses a different binary format, it is not possible to judge from windows to linux. I am pretty convinced, a newer ld

[fpc-devel] FPC 3.0.4 ld error on opensuse 13.2

Hi all, I've just discovered fpc-3.0.4-1.x86_64.rpm does not quite work on opensuse 13.2. That is, linking helloworld fails with: fpc hello.pas Free Pascal Compiler version 3.0.4 [2017/10/02] for x86_64 Copyright (c) 1993-2017 by Florian Klaempfl and others Target OS: Linux for x86-64

Re: [fpc-devel] "Blank slate" next version of FPC

Hi, 09.03.2019 21:06, Anton Shepelev: [...] Pascal is a language where declaration and use of variables is separated. It makes it easy to see what [...] a := a + Func1( b ); int b := Func2( a ); a := a - Func3( b ); Also worth reference are Bart's thoughts on the subject, in two

Re: [fpc-devel] Regressions on i386-win32 and x86_64-win64

Hi, 02.03.2019 19:59, J. Gareth Moreton: It might need double-checking, but I'm getting a couple of regressions on the trunk for i386-win32 and x86_64-win64: Failed, compilation successful webtbf/tw4893d.pp 2018/12/06 07:01:14 Failed, compilation successful webtbf/tw4893e.pp 2018/12/06

Re: [fpc-devel] fpc-devel Digest, Vol 178, Issue 38

Hi, 21.02.2019 17:41, Martin Frb: On 20/02/2019 19:31, Franz Müller wrote: It's a nice example why scoped variables would be in fact better, because the value of i is undefined if the for loop is exited normally. So even the original code wouln't work as expected, you cannot rely on

Re: [fpc-devel] "Blank slate" next version of FPC

Hi, 20.02.2019 23:33, Florian Klämpfl: Am 20.02.19 um 08:36 schrieb Paul van Helden: > As a big fan of the Pascal language, I'd rather break compatibility and see the language evolve than the stoic attitude of the core devs as seen on this list. People could change this attitude by

Re: [fpc-devel] "Blank slate" next version of FPC

20.02.2019 21:28, Giuliano Colla: [...] Moreover, using a modern tool such as Lazarus, you never need to scroll 1000 lines to find a declaration: you just press alt+Up to go to the declaration of the symbol over the cursor, and Ctrl+H to go back to the line of code. It's a bit like car

Re: [fpc-devel] "Blank slate" next version of FPC

Hi, 20.02.2019 23:56, wkitt...@windstream.net: [...] How this example is different from e.g. using normally declared "I, J: Integer" and employing "J" as a loop variable? Wouldn't it do the same error anyway? i think he's pointing out the two instances of var I in the code... one at the

Re: [fpc-devel] "Blank slate" next version of FPC

Hi, 20.02.2019 21:28, Giuliano Colla: [...] I have just met such a situation: I ported from C++ to Pascal an algorithm for the computation of the kinematics of a Delta Robot, and I was badly bitten. In that case you are just dealing with X,Y,Z coordinates, and Theta0,Theta1,and Theta2 angles,

Re: [fpc-devel] "Blank slate" next version of FPC

Hi, 20.02.2019 18:24, Dimitrios Chr. Ioannidis via fpc-devel: [...] I'd like to see an example how this is less safe. Well one of the answer in the Cantu blog has this ( which I changed to lets say a "real world" relative big function ) : How this example is different from e.g. using

Re: [fpc-devel] "Blank slate" next version of FPC

Hi, 20.02.2019 17:56, Martin Frb: 1) "for" (and other) loops with a long body also exist. So the problem is still there, if I encounter "i" in the middle of a This is correct. Inline declaration will not be able to solve all problems in the galaxy, it could just help to relieve some of them.

Re: [fpc-devel] "Blank slate" next version of FPC

Hi Sven, 20.02.2019 16:51, Sven Barth via fpc-devel: [...] Pascal is a language where declaration and use of variables is separated. I can understand that a language can (and should) try to follow some aesthetic tradition (which, btw, has already been horribly broken many times, imho,

Re: [fpc-devel] "Blank slate" next version of FPC

Hi all, 20.02.2019 13:21, Sven Barth via fpc-devel: [...] And we don't agree here. For us inline variables is one of the most horrid if not *the* most horrid thing Embarcadero could have done to Object Pascal. Could you elaborate a bit about it? While I'm not really sure what they have done

Re: [fpc-devel] ref count types / threadsave question

Hi, 03.01.2019 15:25, Benito van der Zander: The ref count is stored in the same memory block as the string itself. If core 2 could not see the new ref count, it could not see what is in the string and thus not use the string for anything . If string content modification is supposed to be

Re: [fpc-devel] Building cross-compiler for arm-linux on win32

16.12.2018 22:44, Florian Klämpfl: Well, problem is a little bit that arm is really a moving target. Yes, I know. Besides, the exact difference between the "arm-linux" target and "armv7-linux-gnueabi" target is afaics just nowhere explicitely documented.(Though, binutils is opensource, one

Re: [fpc-devel] Building cross-compiler for arm-linux on win32

Hi, Yes, "armv7-linux-gnueabi" did the trick for cross-compiling on windows as well. I just had to manually rename binary files of binutils so that thay match the naming pattern fpc build system expacts. I can provide my ready-to-use win32-to-arm binutils 2.31.1 zip if someone is interested.

Re: [fpc-devel] Building cross-compiler for arm-linux on win32

t all including the cross-fpc and my helloworld test on host x86_64-linux box again, I do not get much complaints from the build process anymore and the resulting executable appeared runnable on the arm device! Now going to retry it on windows again... Thank you! Regards, Nikolai 1

Re: [fpc-devel] Building cross-compiler for arm-linux on win32

16.12.2018 20:01, I wrote: Hi, 16.12.2018 17:10, I wrote: I'm wondering what version of binutils was used to release fpc 3.0.4 for arm? I've suddenly noticed that there is apparently no binary 3.0.4 release for arm! Well, at least not officially presented on fpc website. The Not exactly

Re: [fpc-devel] Building cross-compiler for arm-linux on win32

Hi, 16.12.2018 17:10, I wrote: I'm wondering what version of binutils was used to release fpc 3.0.4 for arm? I've suddenly noticed that there is apparently no binary 3.0.4 release for arm! Well, at least not officially presented on fpc website. The download link goes to 3.0.2 version

Re: [fpc-devel] Building cross-compiler for arm-linux on win32

16.12.2018 18:13, Jonas Maebe: Which instructions does it show if you run the program in gdb and do "x/2i $pc-4" when it crashes? I made some additional steps in gdb in order to check if the program in question actually starts executing anything at all. Looks like it does: GNU gdb (GDB;

Re: [fpc-devel] Building cross-compiler for arm-linux on win32

16.12.2018 17:03, Florian Klämpfl: [...] https://svn.freepascal.org/svn/fpcbuild/binaries/i386-win32/ ? They work for me with the command line you mentioned. However, we have to support newer ones, I'll look into this. With binutils from svn, the cross-build itself succeeded for me out of

Re: [fpc-devel] Building cross-compiler for arm-linux on win32

Hi Florian, 16.12.2018 16:41, Florian Klämpfl: I followed the thread, but didn't find it: what binutils do you use? I've tried 3 version so far: * binutils-2.15.94 (prebuilt) from fpc website is unusable because assembler refuses some instructions (I've mentioned it earlier) *

Re: [fpc-devel] Building cross-compiler for arm-linux on win32

Hi all, (Sorry for flooding so much, but I've done some more testing!) In order to isolate any possible wierd windows-specific issues, I've redone everything on x86_64-linux as a host, with the same 3.0.4 version starting compiler, same fpcbuild-3.0.4.zip as a source for cross-build, same

Re: [fpc-devel] Building cross-compiler for arm-linux on win32

Hi, 16.12.2018 13:51, I wrote: [...] So inserting ASTARGET+=-mfpu=softvfp allowed full cross-build to succeed. I have yet to see if the generated binaries are actually usable. Ok, now the resulting elf executable has this (supposedly correct) flag: private flags = 600: [APCS-32] [VFP float

Re: [fpc-devel] Building cross-compiler for arm-linux on win32

Hi all, 16.12.2018 3:44, I wrote: [...] Got it, somewhat: -mfpu=softvfp is passed to arm-linux-as while compiling intermediate .s files (when using -Cfsoft), not sure if it is correct and intentional, and no special flags passed to arm-linux-as while compiling assembler sources. Hence the

Re: [fpc-devel] Building cross-compiler for arm-linux on win32

Hi, 16.12.2018 2:13, I wrote: Is there any easy way to see how exactly ppcrossarm.exe invokes assembler (command-line arguments passed) during a cross-compiler build and also to inspect intermediate .s files? Got it, somewhat: -mfpu=softvfp is passed to arm-linux-as while compiling

Re: [fpc-devel] Building cross-compiler for arm-linux on win32

Hi, Is there any easy way to see how exactly ppcrossarm.exe invokes assembler (command-line arguments passed) during a cross-compiler build and also to inspect intermediate .s files? Thing is, object files compiled from pascal (like system.o) still get this suspicious VFP flag even after I

Re: [fpc-devel] Building cross-compiler for arm-linux on win32

Hi again, 15.12.2018 19:52, Nikolai Zhubr: 15.12.2018 18:24, Florian Klämpfl: Now, I'm targeting an A20-olinuxino-micro board, which is afaik armv7a with VPFv4. The board is running either openwrt or opensuse. (And actually, the binaries produced by the pre-built native compiler have been

Re: [fpc-devel] Building cross-compiler for arm-linux on win32

15.12.2018 19:09, wkitt...@windstream.net: On 12/15/18 10:36 AM, Nikolai Zhubr wrote: So I suppose I should be using CROSSOPT="-CpARMV7A -CfFPV4_S16" ? is this a typo? should it be -CfVPF4_S16 with F and V swapped? No. From ppcrossarm.exe -i: Supported FPU instruction sets: S

Re: [fpc-devel] Building cross-compiler for arm-linux on win32

15.12.2018 18:24, Florian Klämpfl: Now, I'm targeting an A20-olinuxino-micro board, which is afaik armv7a with VPFv4. The board is running either openwrt or opensuse. (And actually, the binaries produced by the pre-built native compiler have been tested in both environments already) So I

Re: [fpc-devel] Building cross-compiler for arm-linux on win32

15.12.2018 17:38, Jonas Maebe: T:\...3.0.4\fpcsrc\rtl\units\arm-linux>arm-linux-objdump.exe -p system.o system.o: file format elf32-littlearm private flags = 600: [APCS-32] [VFP float format] [software FP] I suspect this is an inintended flag set by my arm-linux-as.exe for some reason...

Re: [fpc-devel] Building cross-compiler for arm-linux on win32

15.12.2018 16:58, I wrote: C:\FPC\3.0.4\bin\i386-Win32\arm-linux-ld.exe: error: T:\_tmp\fpcbuild-3.0.4\fpcsrc\rtl\units\arm-linux\system.o uses VFP instructions, whereas .\pp does not C:\FPC\3.0.4\bin\i386-Win32\arm-linux-ld.exe: failed to merge target specific data of file Hm, indeed, objdump

Re: [fpc-devel] Building cross-compiler for arm-linux on win32

Hi all, Ok, apparently the binutils-2.15.94-win32-arm-linux.zip (provided on the fpc website) is somewhat outdated to be really usable for arm target. Retrying with (self-built) binutils-2.28 apparently solves the previous problem but now I have another: ld yells something about VFP

[fpc-devel] Building cross-compiler for arm-linux on win32

Hi all, I'm trying to build a cross-compiler for arm-linux target on a win32 host. It fails at assembling system.s (produced from system.pp) with the following output: T:\_tmp\fpcbuild-3.0.4\fpcsrc\rtl\units\arm-linux\system.s: Assembler messages:

Re: [fpc-devel] @Gareth messages thread

Hi, 31.07.2018 19:05, J. Gareth Moreton: I can only apologise for that. I can only send and receive emails through a webmail system on this address, and it doesn't seem to honour the threading of the messages. I'm not sure what option I'm missing if there is one. Sorry if I sound dumb, but

Re: [fpc-devel] Wrong docs: not initialized global variables

Hi, 05.04.2018 10:12, Ondrej Pokorny пишет: [...] 1.) Global variables are initialized. (Why is simple global variables initialization needed for internal bookkeeping of the compiler?) IIRC this was historically introduced by Borland (ages ago) because it was very cheap and easy to ask an OS

Re: [fpc-devel] BacktraceStrFunc on linux x86_64?

01.05.2017 14:35, Bernd Mueller: On 05/01/2017 11:36 AM, Michael Van Canneyt wrote: Only 3.0.2 linux for i386 CPU has the problem. 64-bit is OK. hmm, I don't get the lineinfo on x86-64 (Ubuntu 16.04/Mate, 64-Bit). armel and armhf are affected too. Personally, for now I'll stick to 2.6.4 --

Re: [fpc-devel] BacktraceStrFunc on linux x86_64?

01.05.2017 11:46, Florian Klämpfl: [...] And I'm still getting just an address anyway... 3.0.x is broken in this regard (stack back trace on x86-64 elf targets), see other threads on the fpc mailing lists regarding this. This is why we discussing a quick as possibile 3.0.4 release. Ah,

Re: [fpc-devel] BacktraceStrFunc on linux x86_64?

01.05.2017 11:21, Michael Van Canneyt: [...] No, but the units that we distribute do not have debug information included. So if the error is in the RTL, then there is no debug information. Ok, right, but then I suppose it should show line number as soon as the example is modified like this:

[fpc-devel] BacktraceStrFunc on linux x86_64?

Hello all, I'm having some trouble to get BacktraceStrFunc to find line numbers. This is with fpc 3.0.0 on linux x86_64 (Centos 7 if it matters). If I compile the following example with #fpc -gl tt.pas I only get this output: Started... Exception: $00455540 Done. Evidently line

[fpc-devel] Links to current .rpm packages are broken on download pages.

Hi all, I've noticed that (at least some) download links are slightly wrong currently, e.g.: ftp://freepascal.stack.nl/pub/fpc/dist/3.0.2/x86_64-linux/rpm/fpc-3.0.2-1.x86_64.rpm should instead read: ftp://freepascal.stack.nl/pub/fpc/dist/3.0.2/x86_64-linux/fpc-3.0.2-1.x86_64.rpm (The

Re: [fpc-devel] A generic function for (multicore) cache flush?

31.10.2016 23:07, Vincent Snijders: Is there any good generic (portable) function to ensure memory cache flush for a thread on a multicore system? Maybe: http://www.freepascal.org/docs-html/rtl/system/readwritebarrier.html Oh yes! That's the thing! Thanks a lot! Nikolai Vincent

Re: [fpc-devel] A generic function for (multicore) cache flush?

31.10.2016 22:44, Jeppe Johansen: Is there any good generic (portable) function to ensure memory cache flush for a thread on a multicore system? What I'm trying to do is essentially fetch some debugging counters from multiple threads. They might happen to run on separate cores, thus having

[fpc-devel] A generic function for (multicore) cache flush?

Hello all, Is there any good generic (portable) function to ensure memory cache flush for a thread on a multicore system? What I'm trying to do is essentially fetch some debugging counters from multiple threads. They might happen to run on separate cores, thus having something pending in

Re: [fpc-devel] Ability to handle instance pointers as ordinal type.

Hi, 21.02.2016 13:37, tha...@thaddy.com: [...] x := (Sender As TComboBox); 8. 9. case x.Name of 10. 'ComboBox01':if x.ItemIndex = -1 then x.ItemIndex := PrjIndex else 11. begin And what's wrong with just this: if Sender = Combobox1 then ... else if Sender

Re: [fpc-devel] Fwd: While - Otherwise Statement

Hi all, 14.10.2015 23:44, Walter Prins: On 14 October 2015 at 07:28, Martin Schreiber > wrote: On Tuesday 13 October 2015 23:25:03 Michael Van Canneyt wrote: > However, I seem to be one of the very few thinking this given the >

Re: [fpc-devel] Proof of Concept ARC implementation

Hello Sven! 25.10.2014 0:23, Sven Barth: Hello together! I've now finished my Proof of Concept ARC implementation which is based on the RFC I published a few weeks back: [...] Could you please elaborate a bit on what will happen to cyclic references? Is there autodetection in place already?

Re: [fpc-devel] Suggestion: reference counted objects

22.09.2014 0:28, Peter Popov: [...] So, for classes which are reference counted, store the reference count @ the highest two bytes of the class instance (which in practice is a pointer to the VMT). This would let you ref-count up to 2^16. You need to mask it out from the rest of the pointer when

Re: [fpc-devel] MIPS big-endian program starts but does nothing

Hi, 09.09.2014 0:54, Sven Barth: [...] http://svn.freepascal.org/cgi-bin/viewvc.cgi?view=revisionrevision=28625 http://svn.freepascal.org/cgi-bin/viewvc.cgi?view=revisionrevision=28625 Since you're compiling with -CfSOFT this might be the solution. BTW, the kernel on the devel mips box has

Re: [fpc-devel] MIPS big-endian program starts but does nothing

07.09.2014 15:50, Florian Klämpfl: Am 07.09.2014 um 13:49 schrieb Sven Barth: Indeed. We have at least two testsuite runs on BigEndian that only have an overviewable amount of errors, so this indeed seems like something specific to the system or the way you compiled it. Can't help any

Re: [fpc-devel] MIPS big-endian program starts but does nothing

Hi! 06.09.2014 14:53, Reinier Olislagers: [...] Ok. It's running openwrt (also so that may well be the case; however I Prebuilt/preflashed openwrt images most definitely do not have normal glibc, which is supposedly expected by normal linux rtl. Although I haven't checked myself, I think

Re: [fpc-devel] MIPS64

15.08.2014 21:07, Florian Klämpfl: Am 13.08.2014 22:05, schrieb Nikolai Zhubr: What do you think? Would someone be interested in remote access to such device with some sort of linux environment? I want to work on aarch64 first. Ok. That is quite reasonable. Thank you. Nikolai

[fpc-devel] MIPS64

Hello devels, I've recently discovered that some mips64 devices have become quite affordable. Namely, EdgeRouter Lite (Dual-core mips64 500MHz, 512Mb RAM) is roughly $100. Because I already run two older (32-bit) mips boxes for fpc tasks, I thought I could probably add yet this newer device,

Re: [fpc-devel] Testsuite database

Hi Pierre, Sorry for late reply, my main computer (with mail) was temporarily out of order. I'm happy to confirm that the problem no longer exists. I do not get any error messages anymore. Also, it looks like query results are produced much faster now. Good work! Actually, I reported the

[fpc-devel] Testsuite database

Hello devels, Apparently the test suite database needs some love? E.g. see this URL (generated automatically by webpage, not by me): http://www.freepascal.org/testsuite/cgi-bin/testsuite.cgi?os=1cpu=8version=44date=submitter=machine=comment=cond=Category=1action=View+history The application

Re: [fpc-devel] mips-linux and mipsel-linux snapshots available

Hi Sergei and Mark, 16.12.2012 12:41, Sergei Gorelkin: [...] This was caused by insufficient alignment of Double-typed temp variables, fixed in r23146. Moreover, it appeared that function UnixToWinAge wasn't doing anything useful since year 2005, so it was removed in r23145, making

Re: [fpc-devel] mips-linux and mipsel-linux snapshots available

17.12.2012 19:12, michael.vancann...@wisa.be: [...] The FPC team has a MIPS device (longsoon?) available. It's currently switched off, but can be switched on at any time. Ah, ok. That's good news. If it is longsoon then it must be much faster than mine. (Though IIRC it only exists in little

Re: [fpc-devel] Testing MIPS: newbie questions

Hi, 15.10.2012 23:57, Mark Morgan Lloyd: [...] So most of the problems described in http://wiki.lazarus.freepascal.org/Native_MIPS_Systems should not be present anymore... I'll update that presently. What I want to try doing first is running the compiler natively (hosted by Qemu), later I

Re: [fpc-devel] Same 64bit assembly code compiles under windows but not in linux (fpc 260)

Hi, 03.10.2012 5:29, luiz americo pereira camara: [...] The complete procedure: {$ASMMODE INTEL} procedure AlphaBlendLineConstant(Source, Destination: Pointer; Count: Integer; ConstantAlpha, Bias: Integer); asm {$ifdef CPU64} // RCX contains Source // RDX contains Destination // R8D contains

Re: [fpc-devel] progress of freepascal for mips

Hi, 09.06.2012 5:27, Fuxin Zhang: I get a copy from my colleague for N32 ABI, no N64 found yet.See http://www.lemote.com/upfiles/mips-abi-n32.pdf. I put it here because no confidential sign in the document. But I am not sure whether it comes from MIPS as a material to licensee. Will check later.

Re: [fpc-devel] about freepascal for mips

Hi, 25.05.2012 23:04, Jeppe Græsdal Johansen: [...] When I tried to build from SVN trunk there would be an endless steam of internalerrors related to fpu registers, no matter if compiled with MIPS FPU or softfloat. I managed to remove the errors with the following patch, such that everything

Re: [fpc-devel] Bounty for MIPS

Hello Florian, 07.02.2012 1:49, Florian Klämpfl: Am 03.02.2012 01:37, schrieb Nikolai Zhubr: I can set up ssh for any FPC developer(s) (though I'll need some time to fix cables etc then) Let me know. It would be nice to get an account, currently I'am still busy with fixing compilation issue

Re: [fpc-devel] Bounty for MIPS

03.02.2012 14:26, Florian Klaempfl: How did you install debian? Or is it a chroot'ed debian? No, it it not chrooted. Basically I took kernel from openwrt 10.03.1 build tree (it is also 2.6.32 but modified slightly to better support platform-specific peripherials), disabled NAND-related

Re: [fpc-devel] Bounty for MIPS

03.02.2012 16:01, Nikolai Zhubr: 03.02.2012 14:26, Florian Klaempfl: How did you install debian? Or is it a chroot'ed debian? No, it it not chrooted. And by the way. If you somehow obtain wndr3800 and want debian on it, I can probably prepare ready-to-use images for hard disk and internal

Re: [fpc-devel] Bounty for MIPS

Hi, 31.01.2012 0:08, Pierre Free Pascal: Anyhow, I just discovered that the /home directory is 99% full on that GCC compile farm machine, meaning that only remote tests will be possible ☹ It seems that lots of developers have the same issue about finding MIPS machines for testing …. Would

Re: [fpc-devel] bounty: FPC based debugger

12.09.2011 11:08, Graeme Geldenhuys: [...] If anybody with the know how is interested in implementing a Object Pascal based debugger (or extending Duby specifically for use with FPC), please let me know. I am more than willing to pay a few hundred US dollars (or Euros) towards this bounty. I'd

Re: [fpc-devel] bounty: FPC based debugger

12.09.2011 15:01, Henry Vermaak: On 12/09/11 12:00, Martin Schreiber wrote: And a FPC only debugger can not debug linked c libraries which we can do Good point. I've found this very handy in the past. currently with gdb. And think of the remote debugging options gdb provides with many

Re: [fpc-devel] Server availability

06.09.2011 15:24, Alexander Klenin: On Tue, Sep 6, 2011 at 22:17, Jonas Maebejonas.ma...@elis.ugent.be wrote: For at least last few months, I write down bugs I encounter in the local file, since by the time the Report Issue page loads, I forget what I wanted to report. I suspect the server is

Re: [fpc-devel] New FPC target: JVM

20.08.2011 19:02, Graeme Geldenhuys: On 20 August 2011 13:30, Felipe Monteiro de Carvalho wrote: I ask because Android does not use Java Bytecode, it has it's own, completely different bytecode. Why did Google do that? Why not stay with the standardized Java and get the benefits of all

Re: [fpc-devel] New FPC target: JVM

Hi, 20.08.2011 12:49, Jonas Maebe: Hi, There is a new branch in svn (branches/jvmbackend) that contains support for compiling Pascal code into Java virtual machine bytecode. This is really amazing, even if functionality is somewhat limited at the moment. Thanks for the great work!

Re: [fpc-devel] volatile variables

30.06.2011 13:31, Hans-Peter Diettrich: If so, would it help to enclose above instructions in e.g. Synchronized begin update the links... end; If by such hypothetical synchronized operator you mean just memory barriers and nothing else, then AFAICS this would not be of much use in practice,

Re: [fpc-devel] volatile variables

29.06.2011 15:28, Hans-Peter Diettrich: But if so, which variables (class fields...) can ever be treated as non-volatile, when they can be used from threads other than the main thread? Without explicit synchronisation? Actually, none. Do you understand the implication of your answer? When

Re: [fpc-devel] volatile variables

29.06.2011 18:31, Michael Schnell: [...] So this is not supposed to work: Main thread: myThread := TmyThread.Create(True); while not myThread.Suspended sleep(0); //give up time slice to allow the worker thread to start myList := TThreadlist.Create; // set the variable in cache 1

Re: [fpc-devel] volatile variables

29.06.2011 19:57, Hans-Peter Diettrich: [...] imply that in detail all application specific objects must be either local to an thread, or must be protected against concurrent access (shareable)? IMHO yes. [...] Possibly the language could be extended to help in the determination of

Re: [fpc-devel] volatile variables

28.06.2011 19:42, Hans-Peter Diettrich wrote: Jonas Maebe schrieb: 2.) Blocking access as described in 4.11 does not address execution order. It does guarantee that if T1 locks the mutex, changes the value, unlocks the mutex [...] Can you explain please, to what changes the value applies?

Re: [fpc-devel] volatile variables

28.06.2011 22:38, Vinzent Höfler wrote: involving some mutex. Such proper constructs are not enforced by pascal language automatically (like say in java), so mistakes are quite possible (and sometimes do happen). JFTR, but they aren't /enforced/ in Java, neither. Well, ok, I didn't mean that

Re: [fpc-devel] Extended type

19.04.2011 13:43, Alexander Klenin: 2011/4/19 Nikolai Zhubrn-a-zh...@yandex.ru: Now, with the introduction of 64-bit processors IIRC AMD took care of this problem by providing some means to execute floating-point operations without the need for traditional FPU register space, thus allowing to

Re: [fpc-devel] Extended type

19.04.2011 14:12, Daniël Mantione: MS does preserve FPU states between processes. You can use the x87 on Windows, nothing prevents you from doing so. Maybe the calling Yes it does for 32-bit processes on win64, guaranteed. But do you have any evidence (tests/documents/links) proving it also

Re: [fpc-devel] Linux Signals

02.01.2011 13:43, Michael Van Canneyt: On Sat, 1 Jan 2011, Andrew Brunner wrote: Thanks, Nikolai. epoll looks like the silver bullet (for linux) and very promising. I can dump a bunch of sockets into it and get the kernel to let me know which ones get notifications for reset/read/write.

Re: [fpc-devel] Linux Signals

01.01.2011 20:27, Andrew Brunner: I'm trying to get signals to work with sockets under x64 Ubuntu 10.10 (all updates) I installed two handlers for two events SIGIO, and SIGHUP uising fpsigaction(SIGIO, @saAct, nil) . I was expecting to get a byte by byte signal under telnet to my server

Re: [fpc-devel] Linux Signals

02.01.2011 2:51, Andrew Brunner: Hi Nikolai, I'm trying to build a cross platform *event* driven socket signaling Ok, now its more clear :) mechanism that does not employ polling algorithms. Then use epoll (linux-specific invention, BSDs have kqueue instead). There is no exact match

Re: [fpc-devel] pqconnection.pp Code Review Needed Int64 data types not supported in PostgreSQL

22.10.2010 1:19, Andrew Brunner: As of right now the PostgreSQL component does not handle Int64 dataype and is crippling any use of the DBMS. If MySQL and PostgreSQL are broken - I just don't see the point of supporting SQL DBMSes. Just in case: also have a look at zeosdbo library. I'm not

Re: [fpc-devel] threadvar implementation

26.07.2010 13:04, Michael Schnell: On 07/24/2010 06:55 PM, Nikolai Zhubr wrote: I think only FS selector (and/or descriptor) varies across threads. Seemingly not the selector value (the FS content seems to stay constant among the threads), but the table entry it selects. You are right. Just

Re: [fpc-devel] is that intended? private type section in classes versus visibility

27.07.2010 0:15, Graeme Geldenhuys: On 26 July 2010 18:30, Marco van de Voortmar...@stack.nl wrote: If your idea was really so great, and this was really a solution, why don't you simply describe it? Yeah, yeah, we all know you have a terrible time maintaining FPC. Most people can maintain

Re: [fpc-devel] OO rewrite - technical questions

24.07.2010 6:55, Hans-Peter Diettrich: IMO the segment register is used implicitly in thread API calls, with no further use by application code. Exactly the opposite (at least delphi on windows). See delphi's RTL. In the Using Thread Local Storage entry in the MSDN library this value is the

Re: [fpc-devel] OO rewrite - technical questions

24.07.2010 17:16, Florian Klämpfl: Am 24.07.2010 13:42, schrieb Nikolai Zhubr: use them to implement this special management so as exceptions and threadvars can be actually used without explicitely using OS APIs. Delphi does not use a segment register for threadvar handling but OS calls

Re: [fpc-devel] OO rewrite - technical questions

24.07.2010 19:12, Hans-Peter Diettrich пишет: [...] I doubt that this address range really is excluded from the 4GB app address space, accessible through the other segment registers. IMHO the question is not how to avoid using FS trick altogether (which is of course possible, right), but on

Re: [fpc-devel] OO rewrite - technical questions

24.07.2010 19:46, Hans-Peter Diettrich: MOV EAX,TlsIndex MOV EDX,FS:tlsArray MOV EAX,[EDX+EAX*4] I wonder what TlsIndex here is? tlsArray = $2C; IIRC for an application (not a dll) TlsIndex is always 0 (But I might be wrong here though) Also FS:tlsArray seems to contain an address in the

  1   2   >