[Bug c/20319] -fkeep-static-consts with -O asserted doesn't keep consts

2008-06-23 Thread hans at mesoscopic dot mines dot edu
--- Comment #9 from hans at mesoscopic dot mines dot edu 2008-06-23 18:03 --- FWIW- I ran into this "bug" too, in the same usecase as Gary. I think the current behavior is close to useless and should be changed as outlined above. Cheers Hans -- hans at mesoscopic dot mines dot ed

[Bug c/20319] -fkeep-static-consts with -O asserted doesn't keep consts

2007-11-13 Thread manu at gcc dot gnu dot org
--- Comment #8 from manu at gcc dot gnu dot org 2007-11-14 03:05 --- (In reply to comment #7) > - yes, the documentation, source code commments and -help are either > incomplete or do not accurately describe present behavior. Confirmed. Patches are welcome. > - -fkepp-static-consts be

[Bug c/20319] -fkeep-static-consts with -O asserted doesn't keep consts

2005-06-20 Thread gary at intrepid dot com
--- Additional Comments From gary at intrepid dot com 2005-06-20 23:40 --- I guess that tagging the bug with a "documentation" keyword doesn't necessarily say that the bug is being classified only as a defect in the documentation. However, if that is the meaning of this keyword, then

[Bug c/20319] -fkeep-static-consts with -O asserted doesn't keep consts

2005-06-19 Thread pinskia at gcc dot gnu dot org
-- What|Removed |Added Keywords||documentation http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20319

[Bug c/20319] -fkeep-static-consts with -O asserted doesn't keep consts

2005-03-18 Thread gary at intrepid dot com
--- Additional Comments From gary at intrepid dot com 2005-03-18 16:16 --- from http://gcc.gnu.org/ml/gcc/2005-03/msg00491.html I think that the switch name -fkeep-static-consts might be more consistenly named if it was given the opposite sense and named something like -fdelete-unused-s

[Bug c/20319] -fkeep-static-consts with -O asserted doesn't keep consts

2005-03-04 Thread gary at intrepid dot com
--- Additional Comments From gary at intrepid dot com 2005-03-04 21:54 --- Here is some detail on my proposed change in behavior: 1) Change the default setting to -fno-keep-static-consts: /* Nonzero means that we should emit static const variables regardless of whether or not opti

[Bug c/20319] -fkeep-static-consts with -O asserted doesn't keep consts

2005-03-04 Thread joseph at codesourcery dot com
--- Additional Comments From joseph at codesourcery dot com 2005-03-04 20:42 --- Subject: Re: -fkeep-static-consts with -O asserted doesn't keep consts On Fri, 4 Mar 2005, pinskia at gcc dot gnu dot org wrote: > Don't belive the comments in the source. Also the --help is way out of

[Bug c/20319] -fkeep-static-consts with -O asserted doesn't keep consts

2005-03-04 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-03-04 20:33 --- Don't belive the comments in the source. Also the --help is way out of date. you want to use the used attribute like so: static char const rcsid[]__attribute__((used)) = "$Id: f.c,v 5.4 1993/11/09 17:40:1

[Bug c/20319] -fkeep-static-consts with -O asserted doesn't keep consts

2005-03-04 Thread gary at intrepid dot com
--- Additional Comments From gary at intrepid dot com 2005-03-04 20:24 --- "Emit variables declared @code{static const} when optimization isn't turned on, even if the variables aren't referenced." How odd. I should've checked the docs, but this brief explanation in the help line made

[Bug c/20319] -fkeep-static-consts with -O asserted doesn't keep consts

2005-03-04 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-03-04 18:29 --- Nope, -fkeep-static-consts only control when optimization is not on: >From the docs: Emit variables declared @code{static const} when optimization isn't turned on, even if the variables aren't refer