Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-pascal / 2016-04

FPC releases for Win64 - 2.6.2 & 2.6.4 versus 3.0.0

8 messages · 5 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Graeme Geldenhuys

Hi,

No my Win64 VM I have FPC 2.6.2 and 2.6.4 installed using the official FPC installers. For example: fpc-2.6.4.x86_64-win64.exe

I wanted to upgrade my VM to FPC 3.0.0, but I don't seem to find an official Win64 release like prior versions. All I can find as a what I assume is a 32-bit cross-complier to win64:

fpc-3.0.0.i386-win32.cross.x86_64-win64.exe

Why did FPC stop making official native win64 compilers? Or is this just a naming convension change?

ps:
How do I know if a program (executable) is 32-bit or 64-bit under Windows? Using Unix-like OSes, I can simply use the "file" command. What is the equivalent under Windows?

ps #2:
Why doesn't the Free Pascal SourceForge page contain a "Win64" folder. The prior FPC releases, the native 64-bit installations are filed under the "Win32" folder. This seems a bit confusing.

Regards,
- Graeme -

fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://fpgui.sourceforge.net/ My public PGP key: http://tinyurl.com/graeme-pgp
Michael Van Canneyt
to Graeme Geldenhuys
Graeme Geldenhuys wrote 13 lines
Hi, No my Win64 VM I have FPC 2.6.2 and 2.6.4 installed using the official FPC installers. For example: fpc-2.6.4.x86_64-win64.exe I wanted to upgrade my VM to FPC 3.0.0, but I don't seem to find an official Win64 release like prior versions. All I can find as a what I assume is a 32-bit cross-complier to win64: fpc-3.0.0.i386-win32.cross.x86_64-win64.exe Why did FPC stop making official native win64 compilers? Or is this just a naming convension change?

The windows team doesn't think there are sufficient reasons/arguments for a 64-bit native compiler.

(So, I roll my own. Luckily, this is not that hard)

ps: How do I know if a program (executable) is 32-bit or 64-bit under Windows? Using Unix-like OSes, I can simply use the "file" command. What is the equivalent under Windows?

Right-click in explorer, 'Properties', and then 'details' or so ?

Show quoted text 5 lines
ps #2: Why doesn't the Free Pascal SourceForge page contain a "Win64" folder. The prior FPC releases, the native 64-bit installations are filed under the "Win32" folder. This seems a bit confusing.

See above.

Michael.

Graeme Geldenhuys
to Michael Van Canneyt
Michael Van Canneyt wrote
The windows team doesn't think there are sufficient reasons/arguments for a 64-bit native compiler.

Lazy buggers! ;-)

(So, I roll my own. Luckily, this is not that hard)

I'll do the same, thanks.

Show quoted text 5 lines
> How do I know if a program (executable) is 32-bit or 64-bit under > Windows? Using Unix-like OSes, I can simply use the "file" > command. What is the equivalent under Windows? Right-click in explorer, 'Properties', and then 'details' or so ?

Nope, that's the firs place I looked. I've got 64-bit Windows 7 installed. The "Properties -> Details" dialog list the file type, version, copyright etc... but nowhere does it say 32-bit or 64-bit.

I can see the "*32" in the Windows Task Manager which indicates 32-bit or 64-bit applications. But that is only useful for long running apps.For very fast running applications (eg: many console utilities) it appears and disappears to quickly for me to see.

Regards,
- Graeme -

fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://fpgui.sourceforge.net/ My public PGP key: http://tinyurl.com/graeme-pgp
Dimitrios Chr. Ioannidis
to Graeme Geldenhuys: No my Win64 VM I have FPC 2.6.2 and 2.6.4 installed using the official FPC installers.…

Hi Graeme,

Στις 2016-04-07 19:07, Graeme Geldenhuys έγραψε:

How do I know if a program (executable) is 32-bit or 64-bit under Windows? Using Unix-like OSes, I can simply use the "file" command. What is the equivalent under Windows?

you can use file ;)

http://gnuwin32.sourceforge.net/packages/file.htm

http://superuser.com/questions/103071/quick-way-to-tell-if-an-installed-application-is-64-bit-or-32-bit

regards,

Dimitrios Chr. Ioannidis
Marco van de Voort
to Dimitrios Chr. Ioannidis

In our previous episode, Dimitrios Chr. Ioannidis said:

Show quoted text 10 lines
???? 2016-04-07 19:07, Graeme Geldenhuys ??????: > How do I know if a program (executable) is 32-bit or 64-bit under > Windows? Using Unix-like OSes, I can simply use the "file" > command. What is the equivalent under Windows? you can use file ;) http://gnuwin32.sourceforge.net/packages/file.htm http://superuser.com/questions/103071/quick-way-to-tell-if-an-installed-application-is-64-bit-or-32-bit

or PE Explorer iirc even some objdump builds (maybe even the ones that come with FPC)

Jonas Maebe
to Graeme Geldenhuys: No my Win64 VM I have FPC 2.6.2 and 2.6.4 installed using the official FPC installers.…

Graeme Geldenhuys wrote on Thu, 07 Apr 2016:

Show quoted text 8 lines
I wanted to upgrade my VM to FPC 3.0.0, but I don't seem to find an official Win64 release like prior versions. All I can find as a what I assume is a 32-bit cross-complier to win64: fpc-3.0.0.i386-win32.cross.x86_64-win64.exe Why did FPC stop making official native win64 compilers? Or is this just a naming convension change?

It's a naming change: the previous Win64 releases were also cross-compilers. There is no advantage I'm a aware of to having a "native" Win64 release compiler, and there are disadvantages such as the inability to compile for any other x86-64 target (because the x87 fpu is deprecated for 64 bit on Windows).

Jonas

Graeme Geldenhuys
to Jonas Maebe
Jonas Maebe wrote
It's a naming change: the previous Win64 releases were also cross-compilers.

I have the installs (with unintall support) for 2.6.0 & 2.6.2 on my system, and they are both native Win64 compilers. I believe they are official installers. The 2.6.4 and 3.0.0 installers on SF.net are definitely cross-compilers.

No matter, like Michael said, it is quite easy to build your own, which I did.

There is no advantage I'm a aware of to having a "native" Win64 release compiler

Well, at the moment you need to do two downloads & installs to get Win64 support. First you need to install the win32 compiler, then the win64 cross-compiler. But yes, I guess that is minor - how often does one install release compilers anyway. ;-)

Thanks for the info though.

Regards,
- Graeme -

fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://fpgui.sourceforge.net/ My public PGP key: http://tinyurl.com/graeme-pgp
Graeme Geldenhuys
to Michael Van Canneyt: The windows team doesn't think there are sufficient reasons/arguments for a 64-bit native…
Michael Van Canneyt wrote
Right-click in explorer, 'Properties', and then 'details' or so ?

I checked again, and you were on the right track. The easiest way, without installing another program or running the GNU "file" command, is just to right click on the file, choose Properties, and then go the the Compatibility tab. If there are no greyed out options and Windows XP and 9x modes are offered, it's 32-bit. If there are greyed out options and Vista is the earliest mode offered, it's 64-bit.

Regards,
- Graeme -

fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://fpgui.sourceforge.net/ My public PGP key: http://tinyurl.com/graeme-pgp