public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Thomas dot Koenig at online dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/18566] New: Can vary constants Date: Fri, 19 Nov 2004 13:23:00 -0000 [thread overview] Message-ID: <20041119132256.18566.Thomas.Koenig@online.de> (raw) Should the value of pi change... The following is very probably illegal code. Still, it would be nice if this could segfault instead of silently doing the Wrong Thing. $ cat variation-constants.f90 module a1 contains subroutine foo(b) real :: b b = 42. end subroutine foo end module a1 program main use a1 real, parameter :: pi = 3.1415926535 call foo(pi) print *,'pi equals ', pi end program main $ gfortran variation-constants.f90 && ./a.out pi equals 42.00000 $ gfortran -v Reading specs from /home/zfkts/lib/gcc/ia64-unknown-linux-gnu/4.0.0/specs Configured with: ../gcc-4.0-20041107/configure --prefix=/home/zfkts --enable-languages=c,c++,f95 Thread model: posix gcc version 4.0.0 20041107 (experimental) -- Summary: Can vary constants Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: Thomas dot Koenig at online dot de CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18566
next reply other threads:[~2004-11-19 13:23 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-11-19 13:23 Thomas dot Koenig at online dot de [this message] 2004-11-19 15:13 ` [Bug fortran/18566] " pinskia at gcc dot gnu dot org 2004-11-25 20:29 ` Thomas dot Koenig at online dot de 2004-11-29 14:13 ` [Bug target/18566] Can vary constants (undefined fortran) pinskia at gcc dot gnu dot org 2004-11-30 8:29 ` Thomas dot Koenig at online dot de 2004-12-07 18:48 ` pinskia at gcc dot gnu dot org 2005-01-05 3:44 ` wilson at gcc dot gnu dot 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=20041119132256.18566.Thomas.Koenig@online.de \ --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: linkBe 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).