public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/104424] New: -fvolatile, not documented in gcc-4.3.3
@ 2022-02-07 16:23 swaroop.tekale at se dot com
  2022-02-07 16:56 ` [Bug c/104424] " schwab@linux-m68k.org
                   ` (6 more replies)
  0 siblings, 7 replies; 8+ messages in thread
From: swaroop.tekale at se dot com @ 2022-02-07 16:23 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 104424
           Summary: -fvolatile, not documented in gcc-4.3.3
           Product: gcc
           Version: 4.3.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: swaroop.tekale at se dot com
  Target Milestone: ---

"-fvolatile" flag is not listed in the below gcc-4.3.6:
https://gcc.gnu.org/onlinedocs/gcc-4.3.6/gcc/Option-Summary.html#Option-Summary

Can you please confirm if this is explicitly removed, as it should not be
configured ?

Or if it is a gcc document miss in above link?

We are still able to use the -fvolatile flag as part of compiler options, So
need confirmation if this is still a valid flag ?

This will help us to understand if we still have to keep "-fvolatile" flag in
our environment or consider removing it.

Compiler version: gnu 4.3.3

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

* [Bug c/104424] -fvolatile, not documented in gcc-4.3.3
  2022-02-07 16:23 [Bug c/104424] New: -fvolatile, not documented in gcc-4.3.3 swaroop.tekale at se dot com
@ 2022-02-07 16:56 ` schwab@linux-m68k.org
  2022-02-07 17:04 ` swaroop.tekale at se dot com
                   ` (5 subsequent siblings)
  6 siblings, 0 replies; 8+ messages in thread
From: schwab@linux-m68k.org @ 2022-02-07 16:56 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #1 from Andreas Schwab <schwab@linux-m68k.org> ---
Such a flag never existed, there is only -Wvolatile.

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

* [Bug c/104424] -fvolatile, not documented in gcc-4.3.3
  2022-02-07 16:23 [Bug c/104424] New: -fvolatile, not documented in gcc-4.3.3 swaroop.tekale at se dot com
  2022-02-07 16:56 ` [Bug c/104424] " schwab@linux-m68k.org
@ 2022-02-07 17:04 ` swaroop.tekale at se dot com
  2022-02-07 17:10 ` redi at gcc dot gnu.org
                   ` (4 subsequent siblings)
  6 siblings, 0 replies; 8+ messages in thread
From: swaroop.tekale at se dot com @ 2022-02-07 17:04 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #2 from Swaroop Tekale <swaroop.tekale at se dot com> ---
It seems to be there on or before gcc-3.3.6:

https://gcc.gnu.org/onlinedocs/gcc-3.3.6/gcc/Option-Summary.html#Option-Summary

Code Generation Options
See Options for Code Generation Conventions.
          -fcall-saved-reg  -fcall-used-reg 
          -ffixed-reg  -fexceptions 
          -fnon-call-exceptions  -funwind-tables 
          -fasynchronous-unwind-tables 
          -finhibit-size-directive  -finstrument-functions 
          -fno-common  -fno-ident  -fno-gnu-linker 
          -fpcc-struct-return  -fpic  -fPIC 
          -freg-struct-return  -fshared-data  -fshort-enums 
          -fshort-double  -fshort-wchar  -fvolatile 
          -fvolatile-global  -fvolatile-static 
          -fverbose-asm  -fpack-struct  -fstack-check 
          -fstack-limit-register=reg  -fstack-limit-symbol=sym 
          -fargument-alias  -fargument-noalias 
          -fargument-noalias-global  -fleading-underscore 
          -ftls-model=model 
          -ftrapv  -fbounds-check

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

* [Bug c/104424] -fvolatile, not documented in gcc-4.3.3
  2022-02-07 16:23 [Bug c/104424] New: -fvolatile, not documented in gcc-4.3.3 swaroop.tekale at se dot com
  2022-02-07 16:56 ` [Bug c/104424] " schwab@linux-m68k.org
  2022-02-07 17:04 ` swaroop.tekale at se dot com
@ 2022-02-07 17:10 ` redi at gcc dot gnu.org
  2022-02-07 17:10 ` redi at gcc dot gnu.org
                   ` (3 subsequent siblings)
  6 siblings, 0 replies; 8+ messages in thread
From: redi at gcc dot gnu.org @ 2022-02-07 17:10 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
It's not there because it was removed in GCC 3.4:
https://gcc.gnu.org/gcc-3.4/changes.html

You will get an error if you try to use it with 4.3.3

There is no bug report here, so I think it would have been more appropriate on
the gcc-help mailing list, https://gcc.gnu.org/lists.html

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

* [Bug c/104424] -fvolatile, not documented in gcc-4.3.3
  2022-02-07 16:23 [Bug c/104424] New: -fvolatile, not documented in gcc-4.3.3 swaroop.tekale at se dot com
                   ` (2 preceding siblings ...)
  2022-02-07 17:10 ` redi at gcc dot gnu.org
@ 2022-02-07 17:10 ` redi at gcc dot gnu.org
  2022-02-07 17:17 ` swaroop.tekale at se dot com
                   ` (2 subsequent siblings)
  6 siblings, 0 replies; 8+ messages in thread
From: redi at gcc dot gnu.org @ 2022-02-07 17:10 UTC (permalink / raw)
  To: gcc-bugs

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
.

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

* [Bug c/104424] -fvolatile, not documented in gcc-4.3.3
  2022-02-07 16:23 [Bug c/104424] New: -fvolatile, not documented in gcc-4.3.3 swaroop.tekale at se dot com
                   ` (3 preceding siblings ...)
  2022-02-07 17:10 ` redi at gcc dot gnu.org
@ 2022-02-07 17:17 ` swaroop.tekale at se dot com
  2022-02-07 17:43 ` schwab@linux-m68k.org
  2022-02-07 21:10 ` redi at gcc dot gnu.org
  6 siblings, 0 replies; 8+ messages in thread
From: swaroop.tekale at se dot com @ 2022-02-07 17:17 UTC (permalink / raw)
  To: gcc-bugs

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

Swaroop Tekale <swaroop.tekale at se dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|INVALID                     |WORKSFORME
             Status|RESOLVED                    |VERIFIED

--- Comment #5 from Swaroop Tekale <swaroop.tekale at se dot com> ---
As mentioned in the description: We are able to use the -fvolatile flag. We are
not getting any errors. 
And hence need to understand if this is a a document miss or really an invalid
flag for gcc 4.3.3 ?

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

* [Bug c/104424] -fvolatile, not documented in gcc-4.3.3
  2022-02-07 16:23 [Bug c/104424] New: -fvolatile, not documented in gcc-4.3.3 swaroop.tekale at se dot com
                   ` (4 preceding siblings ...)
  2022-02-07 17:17 ` swaroop.tekale at se dot com
@ 2022-02-07 17:43 ` schwab@linux-m68k.org
  2022-02-07 21:10 ` redi at gcc dot gnu.org
  6 siblings, 0 replies; 8+ messages in thread
From: schwab@linux-m68k.org @ 2022-02-07 17:43 UTC (permalink / raw)
  To: gcc-bugs

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

Andreas Schwab <schwab@linux-m68k.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|WORKSFORME                  |INVALID

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

* [Bug c/104424] -fvolatile, not documented in gcc-4.3.3
  2022-02-07 16:23 [Bug c/104424] New: -fvolatile, not documented in gcc-4.3.3 swaroop.tekale at se dot com
                   ` (5 preceding siblings ...)
  2022-02-07 17:43 ` schwab@linux-m68k.org
@ 2022-02-07 21:10 ` redi at gcc dot gnu.org
  6 siblings, 0 replies; 8+ messages in thread
From: redi at gcc dot gnu.org @ 2022-02-07 21:10 UTC (permalink / raw)
  To: gcc-bugs

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|VERIFIED                    |RESOLVED

--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The flag does not exist (and cannot be used) in the official GCC releases.
Maybe you are using a modified GCC provided by a third party, so that the
switch is silently ignored and doesn't give an error. In that case, you should
ask whoever provided you with that build.

The documentation on gcc.gnu.org applies to official releases, and -fvolatile
gives an error for those:

$ /home/jwakely/gcc/4.1.2/bin/gcc -x c /dev/null -fvolatile
cc1: error: unrecognized command line option "-fvolatile"
$ /home/jwakely/gcc/4.3.6/bin/gcc -x c /dev/null -fvolatile
cc1: error: unrecognized command line option "-fvolatile"

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

end of thread, other threads:[~2022-02-07 21:10 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-07 16:23 [Bug c/104424] New: -fvolatile, not documented in gcc-4.3.3 swaroop.tekale at se dot com
2022-02-07 16:56 ` [Bug c/104424] " schwab@linux-m68k.org
2022-02-07 17:04 ` swaroop.tekale at se dot com
2022-02-07 17:10 ` redi at gcc dot gnu.org
2022-02-07 17:10 ` redi at gcc dot gnu.org
2022-02-07 17:17 ` swaroop.tekale at se dot com
2022-02-07 17:43 ` schwab@linux-m68k.org
2022-02-07 21:10 ` redi at gcc dot gnu.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).