The screenshot did not make it (restrictions probably of the email
service), but in any case:
- Why store an executable that you created in the installation directory
of gfortran?
- If you want to do that, why not simply copy it with your favourite
file manager or via a copy command?
https://gcc.gnu.org/wiki/GFortranBinaries
Op wo 10 jan 2024 om 11:54 schreef abhay dutta :
>
>
I use the version of gfortran that can be found at equation.com. There are
several other possibilities, such using the packages found in
MinGW-w64/MSYS2 or Cygwin, but this works fine for me and under plain
Windows (i.e. in an ordinary command window).
Regards,
Arjen
Op ma 16 okt 2023 om 18:08 s
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 am
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 random_num
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
understa
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] Au
had hoped Gnu Fortran did the same.
>
> C/C++ never provided any indexed file or "record" level support. FORTRAN
> always did, so I had hopes.
>
> Thanks,
>
> Roland
> On 3/8/23 08:30, Arjen Markus wrote:
>
> Well, that is indeed something completely differen
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 j
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 this
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
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
the
entire file (the --all option does not alter the output)?
Regards,
Arjen
Op vr 3 jun. 2022 om 07:22 schreef Janne Blomqvist <
blomqvist.ja.
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 appe
all
manner of ways to fool the optimiser. Note that with -O2 and the program I
posted I still get the strings.
Regards,
Arjen
Op wo 1 jun. 2022 om 13:36 schreef Arjen Markus :
> Hm, I ran it without any options - would that be equivalent to -g then? A
> rather awkward workaround might
rings | grep GNU .
> If -g is not used, no option info is in the executable.
>
> Best wishes,
> Kay
>
> On 01.06.22 12:00, Arjen Markus wrote:
> > staticv.f90 --
> > ! Static information about the compiler? Not via parameters
> > !
> > progr
= compiler_version()
d = compiler_options()
write(*,*) c(1:1), d(1:)1
end program staticv
to force the text strings to appear. I think a long character string is
required.
Regards,
Arjen
Op wo 1 jun. 2022 om 11:53 schreef Arjen Markus :
> I thought you might get this information by using these
priate. However, programs distributed to others for
> > production use should not output this because it confuses users (as does
> > "Note: The following floating-point exceptions are signalling:
> > IEEE_INVALID_FLAG" which I need to switch off with -ffpe-summary=none).
>
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 kno
oid
> <https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers&af_wl=ym&af_sub1=Internal&af_sub2=Global_YGrowth&af_sub3=EmailSignature>
>
> On Sun, Apr 24, 2022 at 9:39, Arjen Markus
> wrote:
> MicroSoft's
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. 2
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
floatin
?
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: gfor
" statement will need to be changed to use
> the "gfc_notify_std()" method reporting errors.
>
> --
> steve
>
> On Thu, Aug 19, 2021 at 08:59:05AM +0200, Arjen Markus wrote:
> > Hi Steve,
> >
> > I am willing to take up this challenge ;), as well as
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 restar
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
lib.h. It is protected by a symbol __GNU_VISIBLE. I will try to define
that and see what happens.
Regards,
Arjen
Op vr 20 aug. 2021 om 14:31 schreef Richard Biener <
richard.guent...@gmail.com>:
> On Fri, Aug 20, 2021 at 12:55 PM Arjen Markus
> wrote:
> >
> > Okay, that
guess this is my
mistake, as I set the install directory to "d:/gfortran/work" - that should
become "/cygdrive/d/gfortran/work". Easily fixed, but I do not know what to
do about the first error.
Regards,
Arjen
Op vr 20 aug. 2021 om 12:10 schreef Arjen Markus :
>
>
&g
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
li
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 from
point to
> the contributing page
>
> https://gcc.gnu.org/contribute.html
>
> At one time, you need to assign copyright to the FSF.
> That is no longer required. Scan the above page for
> details.
>
> --
> steve
>
> On Fri, Aug 20, 2021 at 08:36:42AM +0200, Arjen M
review.
>
> I do not know if you need any explicit access/permission to
> commit a patch. I iknow very little about git and how it
> works.
>
> At this point, you can either backport the patch to release
> branches or close the PR. For me, I always did a backport
> if it w
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 we
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 <
fortran@gcc.gnu.or
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&utm_medium=email&utm_campaign=the_overflow_newsletter
(to avoid an embedded link just in case, I hav
39 matches
Mail list logo
