Hello,
gfortran is certainly an option, I use an installation from equation.com,
but there are other possibilities as well. The best solution does depend a
bit on your actual requirements.
Regards,
Arjen
Op di 22 aug 2023 om 15:06 schreef Mamadou Diop via Fortran <
fortran@gcc.gnu.org>:
> I
I would say it is indeed very hard to capture all false positves.
Regards,
Arjen
Op wo 12 jul 2023 om 17:05 schreef Vivek Rao via Fortran <
fortran@gcc.gnu.org>:
> For the code
>
> program main
> implicit none
> integer, parameter :: n = 10
> real :: x(n), dx(n)
> integer :: i
> call
You might be better asking a question on comp.lang.fortran newsgroup or the
Fortran discourse site (https://fortran-lang.discourse.group/). This
mailing list is specifically for the gfortran compiler, not user questions.
Also, I might add, the title and the contents of your message may be
As you do not specify what kind of system you have, such advice can only be
very general. But with a decent search engine it should not be too hard to
find a site that allows you to download the software specifically for your
system.
Regards,
Arjen
Op do 25 mei 2023 om 13:47 schreef [Student]
Right, 3270 was the terminal. Wonderful beasts :).
Anyway, this reminded me of an experiment I did a couple of years ago with
wrapping the BerkeleyDB library in Fortran. I never had much use for it,
but it works for small enough value of "work".
But this is diverting a lot from the purpose of
Well, that is indeed something completely different.My main frame of
reference (pun not intentional) of that era was our IBM mini, I am not
quite sure of the type number, 3270? It had a very specific record
structure for unformatted files. Normally that was almost completely
hidden, except in the
I have never worked much with VAXes, but I do remember that VAX used a file
system where you made a new version of a file and the older versions were
automatically kept. I guess that is the purpose of the INDEXED
organisation. It is not so much a limitation of gfortran that it does not
support
Hi Patrick,
you might have a look at fpt - http://www.simconglobal.com/. Not sure if it
will do what you want exactly, but you never know and the people behind it
are well prepared to help out.
Regards,
Arjen
Op vr 16 dec. 2022 om 15:01 schreef Patrick Begou via Fortran <
fortran@gcc.gnu.org>:
The backslash is probably an extension to keep the cursor on the same. You
can achieve that by using advance='no' in the write statement.
Note that some compilers may require a flush statement to actually make the
text visible.
Regards,
Arjen
Op za 27 aug. 2022 15:19 schreef Lars G Golmen :
>
Diederichs <
kay.diederi...@uni-konstanz.de>:
> On 6/3/22 08:47, Arjen Markus via Fortran wrote:
> > Do you know why the strings command does not show the identification
> > string,
> > which clearly present in the executable file, even though it should
> examine
> > t
Hm, I was using a file viewer, not strings to examine the file and I looked
for the text "GCC". That must be the difference. Indeed, strings does not
show that string nor any string containing "GCC"
Here is a small part of the text in the file (compiled without -O2, as with
it some characters
Are you sure that -g is the trigger? It may very well be that you need to
make sure that the optimiser does not eliminate the variable that holds the
identification. That is why I write the first character of these strings,
to make sure that the variables are retained. That could be achieved in
Hm, I ran it without any options - would that be equivalent to -g then? A
rather awkward workaround might be to compile one source file containing
this code with -g, but that is pushing things to the limit.
Regards,
Arjen
Op wo 1 jun. 2022 om 12:16 schreef Kay Diederichs <
Well, if you call these functions in the code, the text is available in the
executable file. I used:
! staticv.f90 --
! Static information about the compiler? Not via parameters
!
program staticv
use iso_fortran_env
implicit none
character(len=200) :: c, d
c =
I thought you might get this information by using these two functions in a
parameter definition, but that is not allowed, alas.
Regards,
Arjen
Op wo 1 jun. 2022 om 11:50 schreef Andre Vehreschild via Fortran <
fortran@gcc.gnu.org>:
> Hi Kay,
>
> did you try:
>
> $ strings
Are you perhaps looking for the compiler_version() and compiler_options()
functions? I use them like this, they were defined in Fortran 2008 if I am
not mistaken:
WRITE( lurep, '(a)' ) 'Report of simulation'
WRITE( lurep, '(a)' ) ''
An alternative is to use a prebuilt distribution. See my answer to William
Carter.
Regards,
Arjen
Op di 26 apr. 2022 om 03:57 schreef Elliot Cramer <
elliottcra...@bellsouth.net>:
> Windows 10; how can we do this?
> Elliot
>
> On 4/23/2022 10:00 PM, Jerry D wrote:
> > Elliot,
> >
> > Let me
There are various solutions to install gfortran (or in general the GCC
compiler suite) on Windows: Cygwin and MinGW-w64/MSYS2 are both
environments that mimick to a certain extent Linux and allow you to manage
all manner of packages, among which the GCC compiler suite. I use both but
I also use
MicroSoft's Fortran compiler is a very old compiler that has not been
maintained in a very long time. The gfortran compiler and the Intel Fortran
oneAPI compiler, both freely available, would easily handle such arrays as
you mention. What system are you running on?
Regards,
Arjen
Op vr 22 apr.
I am not sure I understand your question correctly, but Fortran uses the
KIND mechanism to declare the precise characteristics of floating-point
variables and constants. Typically, these are identifying integer numbers
for single precision, double precision and quadruple precision. A custom
?
Regards,
Arjen
Op ma 23 aug. 2021 om 21:36 schreef Tobias Burnus :
> Hi Arjen,
>
> On 23.08.21 20:59, Arjen Markus via Fortran wrote:
> > as promised, here is an overview of the unexpectedly failing tests. I got
> > these after applying the patches by Steve Kargl for bug ID
Hello,
as promised, here is an overview of the unexpectedly failing tests. I got
these after applying the patches by Steve Kargl for bug ID 101951 and
101967. The platform I used to build it is Cygwin on WIndows 10.
FAIL: gfortran.dg/analyzer/pr96949.f90 -O (internal compiler error)
FAIL:
Hi Steve,
yes, the extra macro did the job, so the testuite has run. So, this means
the patch has to be adapted.
I will report the unexpectedly failing tests in a separate mail.
Regards,
Arjen
Op ma 23 aug. 2021 om 19:18 schreef Steve Kargl <
s...@troutmask.apl.washington.edu>:
> Hi Arjen,
>
I defined both CFLAGS and CXXFLAGS as -D_GNU_SOURCE and it did the trick. I
see a number of unexpected failures in the log, so I will look into those.
But the good news is that the procedure does work.
Regards,
Arjen
Op vr 20 aug. 2021 om 15:17 schreef Arjen Markus :
> Ah, thanks, I restarted
Ah, thanks, I restarted the build with _GNU_SOURCE instead.
Regards,
Arjen
Op vr 20 aug. 2021 om 15:11 schreef Jonathan Wakely :
> On Fri, 20 Aug 2021 at 14:09, Jonathan Wakely wrote:
> >
> > On Fri, 20 Aug 2021 at 13:59, Arjen Markus wrote:
> > >
> > > Going the WSL2 route (I am not all that
Okay, that solved that error, now I get:
-Wall -Wextra -Wwrite-strings -Wcast-qual -Wabi=2
-fdiagnostics-show-location=once -ffunction-sections -fdata-sections
-frandom-seed=fs_ops.lo -fimplicit-templates -g -O2 -c
../../../../../../libstdc++-v3/src/c++17/fs_ops.cc -o fs_ops.o
In file
Op vr 20 aug. 2021 om 11:54 schreef Richard Biener:
>
>
> The easiest is probably to build them in-tree by means of
> executing ./contrib/download_prerequesites which will download
> and unpack them into your source tree.
>
>
Well, I do have the libraries (source and all) and I copied the built
I am trying to build the compiler suite to test the two patches Steve Kargl
posted. But I run into a problem with the mpfr and mpc libraries: the
linker claims it cannot find them.
I checked this, in fist instance they were not present in the location they
were assumed to be, but I had copies
Yes, I already had arranged for that copyright one and a half years ago,
but my first attempts failed (learning curve, real life getting in the way
etc.)
Op vr 20 aug. 2021 om 08:47 schreef Steve Kargl <
s...@troutmask.apl.washington.edu>:
> Feel free to ask questions. I forgot to point to
>
Hi Steve,
thanks for this detailed workflow. I am familiar enough with git to know
that there are myriads of procedures possible ;). Like you said, the first
three steps have been done. I will get working on step 4 and work my way
down the list.
Regards,
Arjen
Op do 19 aug. 2021 om 18:23
I have applied the patches locally (take care to restore the tabs ;)).
Should I now commit these changes or is there a more formal procedure
involved?
Regards,
Arjen
Op do 19 aug. 2021 om 08:59 schreef Arjen Markus :
> Hi Steve,
>
> I am willing to take up this challenge ;), as well as the
Hi Steve,
I am willing to take up this challenge ;), as well as the patch for C949.
It would be my next attempt to get acquainted with the source code (a first
step hopefully to actively contribute).
Regards,
Arjen
Op di 17 aug. 2021 om 21:02 schreef Steve Kargl via Fortran <
An alternative is to post your questions on either comp.lang.fortran or
Fortran Discourse (https://fortran-lang.discourse.group/).
Regards,
Arjen
Op ma 5 jul. 2021 om 09:15 schreef Iain Sandoe via Fortran <
fortran@gcc.gnu.org>:
> Hi Soumyadip,
>
> this mailing list is primarily for discussion
I am not sure that your diagnosis is correct: the survey was announcement
by Stack Overflow. See https:// stackoverflow.blog/ 2021/ 05/
25/the-2021-developer-survey-is-now-open/
?utm_source=Iterable_medium=email_campaign=the_overflow_newsletter
(to avoid an embedded link just in case, I have added
34 matches
Mail list logo
