forums.silverfrost.com

DietmarSiepmann · Joined: 03 Jun 2013 Posts: 279

This is what I would have expected to work. But unfortunately it does not seem to work.

PaulLaidler · Posted: Thu Mar 31, 2016 2:29 pm Post subject:

My apologies. It turns out that this function was not in the export list for the 64 bit DLL. I have added it now for the next release.

DietmarSiepmann · Joined: 03 Jun 2013 Posts: 279

Paul,

in a 32 bit application we make use of subroutine

GET_GRAPHICS_MODES@

which for the corresponding 64 bit application results in runtime error: call to missing routine GET_GRAPHICS_MODES@ .

Is this routine available for 64 bit, and, if so, what is the interface?

Regards,
Dietmar

DietmarSiepmann · Joined: 03 Jun 2013 Posts: 279

Paul,

the same as for subroutine GET_GRAPHICS_MODES@ (of my last entry) seems to be true for SET_PALETTE@ .

Regards,
Dietmar

PaulLaidler · Posted: Fri Apr 01, 2016 2:40 pm Post subject:

Both of these are missing from the export table. I have added them now.

DanRRight · Posted: Sun May 15, 2016 7:54 pm Post subject:

In what state currently is the debugger and /check and /undef in 64bit mode? I still did not touch the current version. Reason is simple - this would kill me if i move beyond 32bits, i will not be able to find tons of such errors like these I make every day in my few large codes I use (mine and thirdparty) without exact pointing at the offending line

PaulLaidler · Posted: Mon May 16, 2016 7:07 am Post subject:

The current release (v8.0) does not have /check nor options that imply /check such as /undef. It does have /debug and comes with a beta release of the 64 bit debugger SDBG64.exe.

For the moment users are advised do their development in "32 bit" mode (using /check etc.) and then to switch to 64 bits in the final stages. In some projects this may require using memory parameters (e.g. array sizes) that must be scaled down during testing and development.

This is a temporary restriction and work on 64 bit /check has a high priority.

tbell · Joined: 06 Apr 2006 Posts: 34

Did you complete any timing test regarding the execution times of the 32-bit vs. the 64-bit compiled code? Thanks.

DanRRight · Posted: Mon May 16, 2016 9:43 pm Post subject:

What dpecifically /debug is doing, what errors it catches? I thought /debug is catches most of /check errors besides array size limit violations.

What plans are regarding Simpleplot in the Clearwin+? Little by little but over all these decades I bacame a heavy user of this handy %pl Clearwin option in addition to my own ones and OpenGL. Probably 50 subroutines now use %pl. Is it working? If not, can I still use older 32bit Clearwin+ with 64bit Fortran? I will probably live ok with the 32 bit size arrays for visualization when passing them to %pl function

What the funny situation I am in... I need 64 bit Fortran like a sunlight but afraid even to try it because this will wreck a major havos in my code

PaulLaidler · Posted: Tue May 17, 2016 7:46 am Post subject:

tbell:
At the current state of development, the 64-bit timings are generally on a par or somewhat better than the corresponding 32-bit timings. /optimise is currently not available but is planned for the next full release and the benefits of using /optimise will increase as more optimising features are added.

In some special contexts (e.g. the use of DOT_PRODUCT) 64-bit FTN95 will make use of SSE(2) or AVX instructions, potentially giving significantly improved times. These instructions will also be made available for users who are willing to write assembly code via CODE/EDOC.

In short, it is probably too early to switch to 64-bit FTN95 if improved timing is the only motivation.

DanRRight:
Primarily, /debug plants code for the debugger (SDBG/SDBG64) to use when stepping through the code etc.. It also gives a better trace-back on run-time failure. /check provides run-time checking (without or without using the debugger); for example, array bounds checking and checking that arguments passed to a subroutine are those that the subroutine expects to receive. However for convenience, /check implies /debug because you would normally want /debug when using /check. Both are designed as tools for testing and development and because of their overheads are not intended for use with the end result.

It would be nice if we could implement 64-bit %pl but this will depend on us either having access to the source code or the authors doing the port for us. I don't have any further information on this at the moment.

DanRRight · Posted: Tue May 17, 2016 8:01 am Post subject:

Paul,
Thanks. For the %pl to work with 64 bit option of the compiler can 32 bit Clearwin+ still be used?

PaulLaidler · Posted: Tue May 17, 2016 8:31 am Post subject:

No. You cannot mix 32-bit and 64-bit code. This is an OS restriction.

DanRRight · Posted: Tue May 17, 2016 11:55 am Post subject:

These Simpleplot devs for 20 years do not providing any feedback, let alone support or fixes. My feeling is that they will never move and Clearwin+ will be missing %pl.

How about OpenGL, does it work?

IanLambley · Joined: 17 Dec 2006 Posts: 506 Location: Sunderland

Dan,
I think you should refrain from that language. The writers Of SimplePlot are retired I believe.
Ian

DanRRight · Posted: Tue May 17, 2016 2:10 pm Post subject:

I do not know which version of my post you have seen as i usually write/rewrite/edit many times. They might be retired or not it does not matter at all. Is it hard to provide, sell, or give as a free gift their code to Silverfrost or may be somehow help to port it or just explain what we can expect from them (yes or no)?

We asked them that here, they participated in the discussion but said nothing definite. By the way besides royalties to them for Simpleplot from Salford Fortran I purchased, i also bought their another app for Android, gave it good review and supported with that their school programmers they were supervising.

If the source code for %pl will not be provided we should move to different application instead of waiting. This small app is handy but has too many defects and has primitive obsolete look

Without %pl the consistency of Clearwin+ is broken and the legacy applications now will not work with 64bit version.

It is only small simple part of Simpleplot source actually needed - the regular standard X-Y graphics plotting utility. Most part of %pl i believe is Silverfrost's own programming for Clearwin+. Graphics plotting engine actually can be taken from other graphics packages. We might all together write one here. I for example have my own ones too. As if it is a big deal to plot the axis, tick, number and connect two points with the line. Big deal is to make all look professional. Simpleplot has very amateurish look and feel