On 2/2/21 11:06 PM, J. Gareth Moreton via fpc-devel wrote:
Hi everyone,
I've found a potential optimisation for conditions of the form "(x <>
0) and (y <> 0)", which are very common because this is semantically
equivalent to "Assigned(x) and Assigned(y)", for example, and such a
construct is
Hi everyone,
I've found a potential optimisation for conditions of the form "(x <> 0)
and (y <> 0)", which are very common because this is semantically
equivalent to "Assigned(x) and Assigned(y)", for example, and such a
construct is generated implicity in TObject.Destroy, for example. The
n
Hi,
Στις 2/2/2021 7:33 μ.μ., ο/η Dimitrios Chr. Ioannidis via fpc-devel έγραψε:
Hi,
On 2021-02-02 18:47, Christo Crause wrote:
On Tue, Feb 2, 2021 at 12:28 PM Dimitrios Chr. Ioannidis via fpc-devel
wrote:
Reading dwarf information with avr-embedded-objdump.exe --dwarf
returns
: "avr-embedde
Hi,
On 2021-02-02 18:47, Christo Crause wrote:
On Tue, Feb 2, 2021 at 12:28 PM Dimitrios Chr. Ioannidis via fpc-devel
wrote:
Reading dwarf information with avr-embedded-objdump.exe --dwarf
returns
: "avr-embedded-objdump.exe: Warning: Invalid CIE pointer 0x00c8
in
FDE at 0x14"
I get
On Tue, Feb 2, 2021 at 12:28 PM Dimitrios Chr. Ioannidis via fpc-devel <
fpc-devel@lists.freepascal.org> wrote:
>
> Reading dwarf information with avr-embedded-objdump.exe --dwarf returns
> : "avr-embedded-objdump.exe: Warning: Invalid CIE pointer 0x00c8 in
> FDE at 0x14"
>
I get the same
I have been trying out compiling my main application for the new Apple
M1 machines, and have two queries:
The traceback on crashes does not include line numbers, when the same
flags on other architectures does. Is this something that is easy to
fix? Any pointers as to how?
Related to this I
Hi,
while I investigate some problems I'm having regarding avr debugging,
I noticed that the dwarf 2 / 3 generation gives a warning when I call a
procedure from another unit. Is it a bug or because it's a warning I can
safely ignore it ?
Reading dwarf information with avr-embedded-objdump
