public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/7041: a.out gives different results when compiled by g++ 3.1 and g++ 3.1 -O Date: Sun, 06 Oct 2002 21:56:00 -0000 [thread overview] Message-ID: <20021007045601.7305.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/7041; it has been noted by GNATS. From: Andrew Pinski <pinskia@physics.uc.edu> To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, alphonse@lri.fr Cc: Subject: Re: optimization/7041: a.out gives different results when compiled by g++ 3.1 and g++ 3.1 -O Date: Sun, 6 Oct 2002 21:54:27 -0700 Looks fixed for 3.3 (gcc version 3.3 20021003 (experimental) ): hodgepodge:~/src/gnu/gcctest>!g+ g++ pr7041.cc hodgepodge:~/src/gnu/gcctest>g++ pr7041.cc -Wall pr7041.cc: In function `int main()': pr7041.cc:63: warning: unused variable `prng gen' hodgepodge:~/src/gnu/gcctest>./a.out 2629073562d hodgepodge:~/src/gnu/gcctest>g++ pr7041.cc -Wall -O pr7041.cc: In function `int main()': pr7041.cc:63: warning: unused variable `prng gen' ^[[Ahodgepodge:~/src/gnu/gcctest>./a.out 2983301384d hodgepodge:~/src/gnu/gcctest> hodgepodge:~/src/gnu/gcctest>g++ pr7041.cc -Wall -O -march=i586 pr7041.cc: In function `int main()': pr7041.cc:63: warning: unused variable `prng gen' ^[[Ahodgepodge:~/src/gnu/gcctest>./a.out 2983301384d hodgepodge:~/src/gnu/gcctest>g++ pr7041.cc -Wall -O -march=i386 pr7041.cc: In function `int main()': pr7041.cc:63: warning: unused variable `prng gen' hodgepodge:~/src/gnu/gcctest>!./ ./a.out 2983301384d hodgepodge:~/src/gnu/gcctest> http://gcc.gnu.org/cgi-bin/gnatsweb.pl
next reply other threads:[~2002-10-07 4:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-06 21:56 Andrew Pinski [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-07 0:16 rth 2002-06-15 11:06 alphonse
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20021007045601.7305.qmail@sources.redhat.com \ --to=pinskia@physics.uc.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).