This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/11307] Random printf values under different optimization levels.
- From: "paudley at compbio dot dundee dot ac dot uk" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 24 Jun 2003 22:41:30 -0000
- Subject: [Bug c/11307] Random printf values under different optimization levels.
- References: <20030624144643.11307.paudley@compbio.dundee.ac.uk>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11307
------- Additional Comments From paudley at compbio dot dundee dot ac dot uk 2003-06-24 22:41 -------
Subject: Re: [bugc/11307] Random printf values under different optimization levels.
>> Why do people not learn to include the proper function
>> declarations?
Did I not say in my bug that this was a distilled test case?
jsm> Why do people not read our bug reporting documentation? It
jsm> clearly says first to test with -Wall to see if that shows up
jsm> problems in the code - what can we do to improve the
jsm> documentation so that it gets followed?
I _did_ test it with -Wall and saw the warnings my question was
why the incorrect specification of the first format led to the
incorrect value of the second. I recieved a tip from a kind person to
look at the implementation of varargs and think I know why now. I can
honestly understand the frustration that most people have when they
talk of reporting bugs. The process of reporting bugs is made no
easier by snide comments like the first one. We are not all compiler
gods you know...