I was trying to build an fpc for clang 16 (same commands worked on a
diff machine for clang 11)
I changed the version in the make line:
make all OPT=" " OPTNEW=" -Clv16.0 " FPCMAKEOPT=" -Clv16.0 " LLVM=1
I also tried version 16.0.6
fpc 49cb7b256476409924c581145a760b863b9e755d
(I had tried
On 06/12/2023 22:25, Jonas Maebe via fpc-devel wrote:
https://releases.llvm.org/11.0.0/docs/SourceLevelDebugging.html#format-common-intrinsics
states that llvm.dbg.declare is identical to llvm.dbg.addr, except that it
works badly in the context of optimisations, and that as a result it is
On 06/12/2023 22:17, Martin Frb via fpc-devel wrote:
If I have enough code, so clang does not optimize the entire function
away in -O1, then clang writes info for some of the lines.
Actually the variable is in a (or several?) registers.
And clang misses some lines too.
But it covers some lines
On 06/12/2023 21:58, Martin Frb via fpc-devel wrote:
On 06/12/2023 21:05, Jonas Maebe via fpc-devel wrote:
On 06/12/2023 17:37, Martin Frb via fpc-devel wrote:
Not suer if the issue is within Fpc or clang...
Should this be reported against Fpc?
FPC defines the variables' debug info at the
On 06/12/2023 21:05, Jonas Maebe via fpc-devel wrote:
On 06/12/2023 17:37, Martin Frb via fpc-devel wrote:
Not suer if the issue is within Fpc or clang...
Should this be reported against Fpc?
FPC defines the variables' debug info at the start of the function and
defines their lifetime as
On 06/12/2023 17:37, Martin Frb via fpc-devel wrote:
Not suer if the issue is within Fpc or clang...
Should this be reported against Fpc?
FPC defines the variables' debug info at the start of the function and
defines their lifetime as starting at the beginning of the function and
continuing
Not suer if the issue is within Fpc or clang...
Should this be reported against Fpc?
- Fedora 33
- Fpc 3.3.1 from Sept 26th
- make all OPT=" " OPTNEW=" -Clv11.0 " FPCMAKEOPT=" -Clv11.0 " LLVM=1
- clang --version
clang version 11.0.0 (Fedora 11.0.0-3.fc33)
Target: x86_64-unknown-linux-gnu
