Op 11-08-18 om 10:22 schreef Christo:
In my mind it was easier to think of subarch/abi options as extending the
target concept, so
each valid combination of CPU-OS-SUBARCH-ABI results in a unique target, which
ends up in a
separate directory. This concept seems to fit in well with the current
I am not sure when this started. It is certainly happening with fpc
3.0.4 and trunk.
I do not know if it worked with earlier versions, but afaik user
complaints only started since Lazarus was released with 3.0.4
- It happens with all versions of GDB. (So it is not something that
changed in
On Mon, Aug 13, 2018 at 5:24 AM Sven Barth via fpc-devel <
fpc-devel@lists.freepascal.org> wrote:
> It's odd that such expression compiles w/o any warnings or notes. (i.e.
>> "ignoring typecasting for constant value expressions")
>>
>
> Support for typecasts in untyped constants is by design and
Il 13/08/2018 16:29, J. Gareth Moreton ha scritto:
I haven't explored it too deeply myself, but from what I understand, a
jump table is only generated if there are a large number of branches
(over 50). If it's just a handful of branches, it simply subtracts
values from the input corresponding
I haven't explored it too deeply myself, but from what I understand, a
jump table is only generated if there are a large number of branches (over
50). If it's just a handful of branches, it simply subtracts values from
the input corresponding to the differences between the case labels, and
Hello,
I would need a clarification about the way the case statement is
translated into assembler by FPC. When the list of alternatives is
continous, does the compiler generate a jump table? And if yes, there is
some conditions for which a fall-through is performed anyway?
Thank you, Marco
Dmitry Boyarintsev schrieb am Mo., 13. Aug.
2018, 00:12:
> On Sun, Aug 12, 2018 at 5:40 PM Bart wrote:
>
>> const
>> x = ShortString('abc');
>> begin
>> writeln(SizeOf(x));
>> end.
>>
>> Delphi (7) prints 256, fpc prints 3.
>>
>> Is that a bug or an implementation detail?
>>
>
>
