public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/34928]  New: volatile does not accept a common block name
@ 2008-01-22 23:50 bdavis at gcc dot gnu dot org
  2008-01-23  7:39 ` [Bug fortran/34928] " burnus at gcc dot gnu dot org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: bdavis at gcc dot gnu dot org @ 2008-01-22 23:50 UTC (permalink / raw)
  To: gcc-bugs

$ cat vol.f
       integer A
       common /C/ A
       volatile /C/
       end
$ gfortran --version
GNU Fortran (GCC) 4.3.0 20071217 (experimental)
Copyright (C) 2007 Free Software Foundation, Inc.

GNU Fortran comes with NO WARRANTY, to the extent permitted by law.
You may redistribute copies of GNU Fortran
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING

$ gfortran -c vol.f 
vol.f:3.15:

       volatile /C/                                                     
              1
Error: Syntax error in VOLATILE statement at (1)
$ g77 vol.f


-- 
           Summary: volatile does not accept a common block name
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: bdavis at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34928


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug fortran/34928] volatile does not accept a common block name
  2008-01-22 23:50 [Bug fortran/34928] New: volatile does not accept a common block name bdavis at gcc dot gnu dot org
@ 2008-01-23  7:39 ` burnus at gcc dot gnu dot org
  2008-01-23 12:12 ` fxcoudert at gcc dot gnu dot org
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: burnus at gcc dot gnu dot org @ 2008-01-23  7:39 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #1 from burnus at gcc dot gnu dot org  2008-01-23 07:12 -------
The following is invalid standard Fortran 77/90/95/2003 syntax,
       volatile /C/
however, it seems to be a not uncommon Fortran 77 vendor extension, supported
by g77, ifort, sunf95, openf95, ...


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34928


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug fortran/34928] volatile does not accept a common block name
  2008-01-22 23:50 [Bug fortran/34928] New: volatile does not accept a common block name bdavis at gcc dot gnu dot org
  2008-01-23  7:39 ` [Bug fortran/34928] " burnus at gcc dot gnu dot org
@ 2008-01-23 12:12 ` fxcoudert at gcc dot gnu dot org
  2008-02-05 15:03 ` burnus at gcc dot gnu dot org
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: fxcoudert at gcc dot gnu dot org @ 2008-01-23 12:12 UTC (permalink / raw)
  To: gcc-bugs



-- 

fxcoudert at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2008-01-23 11:01:56
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34928


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug fortran/34928] volatile does not accept a common block name
  2008-01-22 23:50 [Bug fortran/34928] New: volatile does not accept a common block name bdavis at gcc dot gnu dot org
  2008-01-23  7:39 ` [Bug fortran/34928] " burnus at gcc dot gnu dot org
  2008-01-23 12:12 ` fxcoudert at gcc dot gnu dot org
@ 2008-02-05 15:03 ` burnus at gcc dot gnu dot org
  2009-03-29  9:16 ` [Bug fortran/34928] Extension: volatile common blocks fxcoudert at gcc dot gnu dot org
  2010-05-09 19:28 ` dfranke at gcc dot gnu dot org
  4 siblings, 0 replies; 6+ messages in thread
From: burnus at gcc dot gnu dot org @ 2008-02-05 15:03 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #2 from burnus at gcc dot gnu dot org  2008-02-05 15:02 -------
We need to add a "volatile_" attribute to COMMON; and, either add the VOLATILE
attribute to all its symbols in resolve.c or change the if block in
trans-common.c, which has been added in PR 35037.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34928


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug fortran/34928] Extension: volatile common blocks
  2008-01-22 23:50 [Bug fortran/34928] New: volatile does not accept a common block name bdavis at gcc dot gnu dot org
                   ` (2 preceding siblings ...)
  2008-02-05 15:03 ` burnus at gcc dot gnu dot org
@ 2009-03-29  9:16 ` fxcoudert at gcc dot gnu dot org
  2010-05-09 19:28 ` dfranke at gcc dot gnu dot org
  4 siblings, 0 replies; 6+ messages in thread
From: fxcoudert at gcc dot gnu dot org @ 2009-03-29  9:16 UTC (permalink / raw)
  To: gcc-bugs



-- 

fxcoudert at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement
            Summary|volatile does not accept a  |Extension: volatile common
                   |common block name           |blocks


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34928


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug fortran/34928] Extension: volatile common blocks
  2008-01-22 23:50 [Bug fortran/34928] New: volatile does not accept a common block name bdavis at gcc dot gnu dot org
                   ` (3 preceding siblings ...)
  2009-03-29  9:16 ` [Bug fortran/34928] Extension: volatile common blocks fxcoudert at gcc dot gnu dot org
@ 2010-05-09 19:28 ` dfranke at gcc dot gnu dot org
  4 siblings, 0 replies; 6+ messages in thread
From: dfranke at gcc dot gnu dot org @ 2010-05-09 19:28 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #3 from dfranke at gcc dot gnu dot org  2010-05-09 19:28 -------
Since PR35037 we can have VOLATILE variables in COMMON blocks. But VOLATILE
COMMON blocks are still unsupported (gcc version 4.6.0 20100509 (experimental)
(GCC)). Demand is low, besides this PR, there's nothing in the ML. Even if
supported by g77 - WONTFIX (maybe with a note in the docs)?


-- 

dfranke at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dfranke at gcc dot gnu dot
                   |                            |org
             Status|NEW                         |WAITING


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34928


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2010-05-09 19:28 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-01-22 23:50 [Bug fortran/34928] New: volatile does not accept a common block name bdavis at gcc dot gnu dot org
2008-01-23  7:39 ` [Bug fortran/34928] " burnus at gcc dot gnu dot org
2008-01-23 12:12 ` fxcoudert at gcc dot gnu dot org
2008-02-05 15:03 ` burnus at gcc dot gnu dot org
2009-03-29  9:16 ` [Bug fortran/34928] Extension: volatile common blocks fxcoudert at gcc dot gnu dot org
2010-05-09 19:28 ` dfranke at gcc dot gnu dot org

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).