public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at tat dot physik dot uni-tuebingen dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/11841] [3.3 Regression] The code compiled with -funroll-loops crashes
Date: Wed, 28 Apr 2004 11:13:00 -0000 [thread overview]
Message-ID: <20040428095010.3863.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030807012210.11841.panov@canopus.iacp.dvo.ru>
------- Additional Comments From rguenth at tat dot physik dot uni-tuebingen dot de 2004-04-28 09:50 -------
Subject: Re: [3.3 Regression] The code compiled with
-funroll-loops crashes
Using -fno-force-mem doesn't pessimize generated code for my POOMA
testcases, so maybe we can disable it if -funroll-loops is specified, or
disable it completely by default.
Maybe someone can do a SPEC run with -fno-force-mem/-fforce-mem. Also in
3.5 we have
2004-03-20 Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz>
* emit-rtl.c (set_mem_attributes_minus_bitpos): Set MEM_POINTER
flag.
* explow.c (force_not_mem): Set REG_POINTER flag according to
MEM_POINTER one.
* rtl.h (MEM_POINTER): New macro.
(struct rtx_def): Use integrated for MEM_SCALAR_P and frame_related
for MEM_POINTER.
but I don't know wether this is a bugfix or not.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11841
next prev parent reply other threads:[~2004-04-28 9:50 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 1:22 [Bug c/11841] New: " panov at canopus dot iacp dot dvo dot ru
2003-08-07 1:24 ` [Bug c/11841] " panov at canopus dot iacp dot dvo dot ru
2003-08-07 1:54 ` [Bug optimization/11841] [3.3 Regression] " pinskia at physics dot uc dot edu
2003-08-07 12:42 ` steven at gcc dot gnu dot org
2003-08-07 13:14 ` bangerth at dealii dot org
2003-08-07 13:16 ` s dot bosscher at student dot tudelft dot nl
2003-08-07 13:18 ` steven at gcc dot gnu dot org
2003-08-07 13:36 ` bangerth at dealii dot org
2003-08-07 13:42 ` s dot bosscher at student dot tudelft dot nl
2003-08-07 13:46 ` bangerth at dealii dot org
2003-08-07 13:47 ` bangerth at dealii dot org
2003-09-07 16:34 ` ebotcazou at gcc dot gnu dot org
2003-09-28 22:04 ` pinskia at gcc dot gnu dot org
2003-10-08 23:26 ` panov at canopus dot iacp dot dvo dot ru
2003-10-16 17:13 ` mmitchel at gcc dot gnu dot org
2003-11-18 3:07 ` panov at canopus dot iacp dot dvo dot ru
2003-11-18 4:33 ` pinskia at gcc dot gnu dot org
2003-12-12 8:11 ` ebotcazou at gcc dot gnu dot org
2004-01-23 18:21 ` dhazeghi at yahoo dot com
2004-01-23 18:21 ` dhazeghi at yahoo dot com
2004-02-15 12:35 ` gdr at gcc dot gnu dot org
2004-03-30 21:38 ` reichelt at gcc dot gnu dot org
2004-03-30 21:43 ` bangerth at dealii dot org
2004-03-30 21:43 ` pinskia at gcc dot gnu dot org
2004-03-30 21:44 ` pinskia at gcc dot gnu dot org
2004-03-30 21:57 ` reichelt at igpm dot rwth-aachen dot de
2004-03-30 23:13 ` reichelt at gcc dot gnu dot org
2004-04-27 6:32 ` gdr at gcc dot gnu dot org
2004-04-27 12:46 ` reichelt at gcc dot gnu dot org
2004-04-27 14:50 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-04-27 15:32 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-04-27 19:35 ` ebotcazou at gcc dot gnu dot org
2004-04-27 21:00 ` ebotcazou at gcc dot gnu dot org
2004-04-27 22:11 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-04-28 9:52 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-04-28 11:13 ` rguenth at tat dot physik dot uni-tuebingen dot de [this message]
2004-04-28 14:44 ` ebotcazou at gcc dot gnu dot org
2004-04-28 14:47 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-05-13 1:59 ` reichelt at gcc dot gnu dot org
2004-05-13 7:48 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-05-18 13:56 ` [Bug rtl-optimization/11841] " cvs-commit at gcc dot gnu dot org
2004-05-18 14:02 ` ebotcazou 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=20040428095010.3863.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).