public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Gary.White at ColoState dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/109865] different results when routine moved inside the contains statement
Date: Mon, 15 May 2023 21:54:04 +0000	[thread overview]
Message-ID: <bug-109865-4-2aoCw9j7fP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109865-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865

--- Comment #7 from GARY.WHITE at ColoState dot edu <Gary.White at ColoState dot edu> ---
Sorry I can't simplify this down to a nice compact piece of code, but ...

In the attached test_case.zip file are all the *.f90 files, makefile, and some
library files that work on ubuntu with gfortran-12.  I can provide Windows
libraries if that is easier.

  Create the executable file, mark64,  by a  simple
 make
or
 make type=mark64

Right now, the makefile does not have an -O0 on the va09ad.f90 compile line. 
As we found out, over-riding -O3 on va09ad.f90 compilation produces correct
code.

Execute the test case with

 ./mark64 i=dipper.inp o=dipper.out

I've included 2 output files, dipper_correct.out and dipper_incorrect.out so
you can see what correct and incorrect outputs look like.

Hopefully this all works out.

Thanks.

Gary

Gary C. White, CWB(r)
Professor Emeritus
Department of Fish, Wildlife, and Conservation Biology
10 Wagar
Colorado State University
Fort Collins, CO 80523
(515)450-2768 Mobile
Gary.White@ColoState.edu
https://sites.warnercnr.colostate.edu/gwhite/
he/him/his

See where we are!

"Leadership is a privilege to better the lives of others. It is not an
opportunity to satisfy personal greed." Mwai Kibaki

-----Original Message-----
From: kargl at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org>
Sent: Monday, May 15, 2023 2:42 PM
To: White,Gary <Gary.White@colostate.edu>
Subject: [Bug fortran/109865] different results when routine moved inside the
contains statement

** Caution: EXTERNAL Sender **

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865

--- Comment #6 from kargl at gcc dot gnu.org --- (In reply to
GARY.WHITE@ColoState.edu from comment #5)
> (In reply to Steve Kargl from comment #4)

> > I assume you've also tried with -fcheck=all.
> > Your report states you're using og12.  If it supports the sanitizer,
> > can you add -fsanitize=undefined to the options?
>
> -fcheck=all does not generate any warnings.
> -fsanitize=undefined returns pages when loading of:
>
> undefined reference to `__ubsan_handle_pointer_overflow'
>
> which makes no sense to me????

Hmmm.  Thanks for checking.  Either your version of gcc is not built with
--enable-libsanitizer or gfortran cannot find the library.  At this point, it
seems we're going to need a complete testcase.

--
You are receiving this mail because:
You reported the bug.

  parent reply	other threads:[~2023-05-15 21:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15 18:19 [Bug fortran/109865] New: " Gary.White at ColoState dot edu
2023-05-15 18:32 ` [Bug fortran/109865] " anlauf at gcc dot gnu.org
2023-05-15 18:50 ` kargl at gcc dot gnu.org
2023-05-15 19:11 ` Gary.White at ColoState dot edu
2023-05-15 19:24 ` sgk at troutmask dot apl.washington.edu
2023-05-15 20:32 ` Gary.White at ColoState dot edu
2023-05-15 20:41 ` kargl at gcc dot gnu.org
2023-05-15 21:54 ` Gary.White at ColoState dot edu [this message]
2023-05-15 22:01 ` Gary.White at ColoState dot edu
2023-05-16 15:55 ` Gary.White at ColoState dot edu
2023-05-16 21:51 ` sgk at troutmask dot apl.washington.edu
2023-05-16 22:32 ` Gary.White at ColoState dot edu
2023-05-17  0:56 ` Gary.White at ColoState dot edu
2023-05-17  0:56 ` Gary.White at ColoState dot edu
2023-05-17  1:09 ` Gary.White at ColoState dot edu
2023-05-17  3:08 ` jvdelisle at gcc dot gnu.org
2023-05-17 16:49 ` Gary.White at ColoState dot edu
2023-05-17 16:55 ` pinskia at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-109865-4-2aoCw9j7fP@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).