public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug optimization/12828] -floop-optimize is unstable on PowerPC (float to int conversion problem) Date: Thu, 30 Oct 2003 04:45:00 -0000 [thread overview] Message-ID: <20031030044405.18320.qmail@sources.redhat.com> (raw) In-Reply-To: <20031029174045.12828.chlunde+bug@ifi.uio.no> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12828 pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Component|c++ |optimization
next prev parent reply other threads:[~2003-10-30 4:44 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-10-29 17:42 [Bug c++/12828] New: -floop-optimize is unstable on PowerPC chlunde+bug at ifi dot uio dot no 2003-10-29 18:08 ` [Bug c++/12828] -floop-optimize is unstable on PowerPC (float to int conversion problem) pinskia at gcc dot gnu dot org 2003-10-30 4:45 ` pinskia at gcc dot gnu dot org [this message] 2003-10-30 5:12 ` [Bug optimization/12828] " pinskia at gcc dot gnu dot org 2003-10-30 5:18 ` pinskia at gcc dot gnu dot org 2003-10-30 6:14 ` pinskia at gcc dot gnu dot org 2003-11-02 20:46 ` debian-gcc at lists dot debian dot org 2003-12-08 20:25 ` pinskia at gcc dot gnu dot org 2003-12-19 7:26 ` pinskia at gcc dot gnu dot org 2003-12-22 19:00 ` cvs-commit at gcc dot gnu dot org 2003-12-22 19:01 ` dalej at gcc dot gnu dot org 2004-04-13 22:45 ` pinskia at gcc dot gnu dot org 2004-08-18 2:29 ` [Bug rtl-optimization/12828] " pinskia at gcc dot gnu dot org 2005-03-05 1:27 ` pinskia at gcc dot gnu dot org
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=20031030044405.18320.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).