Re: [fpc-devel] Cortex-M0 (SAMD21G18A) and gcc-arm-none-eabi-8-2018-q4-major-win32

2019-05-27 Thread Michael Ring
Quite a number is already in on trunk, but as the support for devices is getting bigger and bigger (at least on my harddisc) there is a need for an inteligent mechanism to handle the huge amount of devices as the header files eat up a lot of space in svn and only a very few will actually get us

Re: [fpc-devel] Cortex-M0 (SAMD21G18A) and gcc-arm-none-eabi-8-2018-q4-major-win32

2019-05-27 Thread Dimitrios Chr. Ioannidis via fpc-devel
Hi Michael, On 2019-05-26 14:14, Michael Ring wrote: Just one note of caution: When you encounter strange behaviour of your Code on Cortex-M0 in respect to DIV commmand then check the mailinglist, Jeppe has provided a fix but I am not quite sure if the fix has made it into official trunk. thx

Re: [fpc-devel] [Core] Haiku merges: Revision 42117

2019-05-27 Thread Karoly Balogh (Charlie/SGR)
Hi, On Mon, 27 May 2019, Pierre Muller wrote: > The merge of the two commits generate 3 conflicts, but those are easily > solved. > See attached patch. > > Olivier, did you test the fixes_3_2 branch? > Do you think it is reasonable to enable x86_64-haiku target in that branch? I think if al

Re: [fpc-devel] [Core] Haiku merges: Revision 42117

2019-05-27 Thread Pierre Muller
The merge of the two commits generate 3 conflicts, but those are easily solved. See attached patch. Olivier, did you test the fixes_3_2 branch? Do you think it is reasonable to enable x86_64-haiku target in that branch? charlie, you wrote those patches, thus it is probably best if you or O

Re: [fpc-devel] Compiler picks wrong overload

2019-05-27 Thread Martok
> More broadly I think the bigger problem is FPC's internal over-eagerness to > implicitly cast things to other things... for example, if you have a type with > an ":=" operator overload (or as Delphi calls it, an "Implicit" operator > overload) from both "Pointer" and "TObject", FPC will always pi