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/14947] Optimization leads to SegV for large locals on MAC Power PC
Date: Tue, 13 Apr 2004 22:45:00 -0000 [thread overview]
Message-ID: <20040413220012.25624.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040413213609.14947.fsmith@mathworks.com>
------- Additional Comments From pinskia at gcc dot gnu dot org 2004-04-13 22:00 -------
This is a dup of bug 12828 which is fixed for 3.4.0. The problem is -floop-optimize, you can disable it
by -fno-loop-optimize but that disables some loop optimizations.
*** This bug has been marked as a duplicate of 12828 ***
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Component|c |optimization
Keywords| |patch, wrong-code
Resolution| |DUPLICATE
Target Milestone|--- |3.4.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14947
prev parent reply other threads:[~2004-04-13 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 22:12 [Bug c/14947] New: " fsmith at mathworks dot com
2004-04-13 22:45 ` pinskia at gcc dot gnu dot org [this message]
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=20040413220012.25624.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: link
Be 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).