https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94905
Manuel López-Ibáñez changed:
What|Removed |Added
CC||manu at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94905
--- Comment #8 from Chris Moller ---
Created attachment 48825
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48825=edit
Preprocessed testcase
gunzip then compile with
g++ -DHAVE_CONFIG_H -I. -I..-Wall -I sql -Werror -rdynamic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94905
Chris Moller changed:
What|Removed |Added
CC||moller at mollerware dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94905
--- Comment #6 from Arseny Solokha ---
Thank you.
(In reply to Dr. Jürgen Sauermann from comment #5)
> Not sure how I can create a testcase file other than preprocessing or
> minimizing it.
Of course preprocessing is what you've been asked to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94905
--- Comment #5 from Dr. Jürgen Sauermann ---
Hi,
above is one preprocessed source file for which the warning has occurred. g++
version was 11.0.0 (latest from github).
Compiled with:
g++ -E -DHAVE_CONFIG_H -I. -I..-Wall -I sql -Werror
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94905
--- Comment #4 from Dr. Jürgen Sauermann ---
Created attachment 48431
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48431=edit
preprocessed apl-Bif_F12_FORMAT.cc, gzip'ed
preprocessed source file apl-Bif_F12_FORMAT.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94905
Arseny Solokha changed:
What|Removed |Added
CC||asolokha at gmx dot com
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94905
--- Comment #2 from Dr. Jürgen Sauermann ---
I checked different g++ versions; the problem occurs in versions 9, 10, and 11
of g++ but not in version 8.
I tried to shrink the code to the bare minimum but if I do so then the warning
is no longer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94905
--- Comment #1 from Marc Glisse ---
Several of us asked, and it was rejected. Your next step is to provide a
self-contained testcase (preprocessed sources?). You may also want to check if
it still warns in gcc-10.
