Recent

Poll

do you develop the 32 bit version first or the 64 bit version first

64 bit version first
32 bit version first

Author Topic: Which bitness first ?  (Read 5529 times)

Bart

  • Hero Member
  • *****
  • Posts: 5537
    • Bart en Mariska's Webstek
Re: Which bitness first ?
« Reply #15 on: June 25, 2024, 11:59:24 pm »
On Windows I mainly use 32-bit (because the compiler is natively 32 bit).
I only cross-compile to win64 if I see an advantage (or to check it compiles at all).
I maybe just too lazy to rebuild Lazarus to 64-bit and build all by default to 64-bit.
My hardware surely should not be a  problem.

Bart

Scoops

  • Full Member
  • ***
  • Posts: 103
Re: Which bitness first ?
« Reply #16 on: June 26, 2024, 07:26:54 am »
I only install 32 bit for now, in the readme file for 64bit windows download page its written.

The Lazarus team recommends to use the 32bit Version of Lazarus, even for working on 64bit platforms, or for generating 64 bit applications.

Is this advice still recommended or is it outdated ?
« Last Edit: June 26, 2024, 07:30:16 am by Scoops »

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 10902
  • Debugger - SynEdit - and more
    • wiki
Re: Which bitness first ?
« Reply #17 on: June 26, 2024, 07:37:53 am »
I only install 32 bit for now, in the readme file for 64bit windows download page its written.

The Lazarus team recommends to use the 32bit Version of Lazarus, even for working on 64bit platforms, or for generating 64 bit applications.

Is this advice still recommended or is it outdated ?

https://sourceforge.net/projects/lazarus/files/Lazarus%20Windows%2064%20bits/Lazarus%203.4/
Where is that written?

I would say it is outdated.

Especially since the 32bit IDE version can debug 64bit apps only with gdb, but not with FpDebug. While the 64bit IDE can debug both bitnesses (with FpDebug).

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 10902
  • Debugger - SynEdit - and more
    • wiki
Re: Which bitness first ?
« Reply #18 on: June 26, 2024, 07:40:06 am »
I found it. https://sourceforge.net/projects/lazarus/files/Lazarus%20Windows%2064%20bits/

It is outdated. That was SEH related. Only fpc 2.x.

Thaddy

  • Hero Member
  • *****
  • Posts: 16646
  • Kallstadt seems a good place to evict Trump to.
Re: Which bitness first ?
« Reply #19 on: June 26, 2024, 08:35:44 am »
And everybody still adheres to it since it still shows up everywhere without reason.
I have been cross compiling from 64 to 32 for many years against all advice to do it the other way around.
« Last Edit: June 26, 2024, 08:41:54 am by Thaddy »
But I am sure they don't want the Trumps back...

Thaddy

  • Hero Member
  • *****
  • Posts: 16646
  • Kallstadt seems a good place to evict Trump to.
Re: Which bitness first ?
« Reply #20 on: June 26, 2024, 12:07:33 pm »
To everybody: let's fix this. It does not need code (well, fpcupdeluxe needs a warning to remove), just a couple of doc maintainers.
But I am sure they don't want the Trumps back...

marcov

  • Administrator
  • Hero Member
  • *
  • Posts: 12107
  • FPC developer.
Re: Which bitness first ?
« Reply #21 on: June 26, 2024, 01:02:34 pm »
(FPC still has an issue afaik, when 64-bit to 32-bit cross-compilation on x86 doesn't yield the same results because the constants in the compiler are rounded differently (64 vs 80-bit I assume))

Thaddy

  • Hero Member
  • *****
  • Posts: 16646
  • Kallstadt seems a good place to evict Trump to.
Re: Which bitness first ?
« Reply #22 on: June 26, 2024, 02:21:33 pm »
For a cross compiler that should never be an issue. Extended should end up as 80 bits.
But I am sure they don't want the Trumps back...

marcov

  • Administrator
  • Hero Member
  • *
  • Posts: 12107
  • FPC developer.
Re: Which bitness first ?
« Reply #23 on: June 26, 2024, 02:35:32 pm »
For a cross compiler that should never be an issue. Extended should end up as 80 bits.

WIndows 64-bit doesn't have extended. So a 80-bit soft float need to be developed and valdiated.

Thaddy

  • Hero Member
  • *****
  • Posts: 16646
  • Kallstadt seems a good place to evict Trump to.
Re: Which bitness first ?
« Reply #24 on: June 26, 2024, 03:03:00 pm »
Which is perfecrly possible with softfloat.... and that is supported. It is also possible with some Florian specific tricks on x86_86-win64.(this is hardly documented, but works)
It is developed.
« Last Edit: June 26, 2024, 07:34:59 pm by Thaddy »
But I am sure they don't want the Trumps back...

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 10902
  • Debugger - SynEdit - and more
    • wiki
Re: Which bitness first ?
« Reply #25 on: June 26, 2024, 07:43:18 pm »
(FPC still has an issue afaik, when 64-bit to 32-bit cross-compilation on x86 doesn't yield the same results because the constants in the compiler are rounded differently (64 vs 80-bit I assume))

Maybe, but the add on on the lazarus download side, actually is a 32 bit ppc, marketed as cross compiler from 64 to 32 bit.

madref

  • Hero Member
  • *****
  • Posts: 1102
  • ..... A day not Laughed is a day wasted !!
    • Nursing With Humour
Re: Which bitness first ?
« Reply #26 on: June 26, 2024, 08:38:10 pm »
I don't have a choice. I am on a Mac... so 64 it is
You treat a disease, you win, you lose.
You treat a person and I guarantee you, you win, no matter the outcome.

Main Platform:
--------------
Mac OS X Sonoma 14.7.4
Lazarus 4.99 (rev main_4_99-1378-ga4855f6fa5) FPC 3.3.1 x86_64-darwin-cocoa

Windows 10 Pro
Lazarus 3.99 (rev cbfd80ce39)

Mr.Madguy

  • Hero Member
  • *****
  • Posts: 866
Re: Which bitness first ?
« Reply #27 on: June 26, 2024, 09:06:25 pm »
Both. High level languages like Pascal or C++ can produce fully 32bit<->64bit portable code, if some simple rules are followed. It's not ASM. I usually create both 32bit and 64bit building configurations right when I create new project and then compile and test them both. It's actually good idea, because some memory access issues don't show up on one bitness, but do on other. For example 32bit code can work properly, but 64bit one wouldn't.
Is it healthy for project not to have regular stable releases?
Just for fun: Code::Blocks, GCC 13 and DOS - is it possible?

VisualLab

  • Hero Member
  • *****
  • Posts: 639
Re: Which bitness first ?
« Reply #28 on: June 27, 2024, 02:17:56 pm »
Is your question only about developing Windows/Linux on x86/AMD64? Or maybe it also covers 32-bit ARM microcontrollers (e.g. RPi Pico)?
The question is meant to cover CPUs and O/Ss that support both bitnesses, e.g, on Windows it is possible (given the right O/S version) to run either a 32 bit program or a 64 bit program.   Since both options are available, I wanted to know if programmers had a preference as to which version to develop first given those possibilities.

On my home computer (typical PC) running Winows 10 64-bit, I use Lazarus 64-bit. On 2 small computers for experiments I use:
  • Up Squared (Intel Celeron, 4 GB RAM) - Windows 10 64-bit and Linux Kubuntu 23.04 64-bit are installed - Lazarus 64-bit is installed in both OSes,
  • on Raspberry Pi 3B - Raspberry Pi OS Bullseye 32-bit - Lazarus 32-bit are installed.

On Raspberry Pi 3B I tried to use Raspberry Pi OS Bookworm 64-bit, but the OS is slow.

PascalDragon

  • Hero Member
  • *****
  • Posts: 5899
  • Compiler Developer
Re: Which bitness first ?
« Reply #29 on: June 27, 2024, 09:24:15 pm »
Which is perfecrly possible with softfloat.... and that is supported. It is also possible with some Florian specific tricks on x86_86-win64.(this is hardly documented, but works)
It is developed.

Softfloat is still missing a few basic math routines like exp or ld that are necessary for complete coverage and thus consistent compilation from non-Extended targets to those that have Extended. Also the compiler currently does not support softfloat inside itself correctly, so it wouldn't work either currently.

 

TinyPortal © 2005-2018