public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug middle-end/24095] New: use of garbage-collected memory with -ftree-vectorize
@ 2005-09-27 22:50 janis187 at us dot ibm dot com
2005-09-27 22:52 ` [Bug middle-end/24095] " janis187 at us dot ibm dot com
2005-09-27 23:29 ` pinskia at gcc dot gnu dot org
0 siblings, 2 replies; 3+ messages in thread
From: janis187 at us dot ibm dot com @ 2005-09-27 22:50 UTC (permalink / raw)
To: gcc-bugs
GCC mainline for powerpc-linux segfaults when compiling several of the
SPEC CPU2000 tests with "-ftree-vectorize -maltivec -mabi=altivec".
For most of them this happens with both -m32 and -m64.
The minimized test case (to be attached) causes the failure when
compiled with "-O2 -ftree-vectorize -maltivec --param ggc-min-expand=0
--param ggc-min-heapsize=0". The segfault is in fold_convert with
orig having the value 0xa5a5a5a5.
A reghunt identified the following patch from rth@gcc.gnu.org:
http://gcc.gnu.org/ml/gcc-cvs/2005-09/msg00635.html
This could be a latent bug, since on one of the systems I use regularly
I was not able to reproduce the failure.
--
Summary: use of garbage-collected memory with -ftree-vectorize
Product: gcc
Version: 4.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: middle-end
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: janis187 at us dot ibm dot com
CC: gcc-bugs at gcc dot gnu dot org,rth at gcc dot gnu dot
org
GCC target triplet: powerpc-linux
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24095
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug middle-end/24095] use of garbage-collected memory with -ftree-vectorize
2005-09-27 22:50 [Bug middle-end/24095] New: use of garbage-collected memory with -ftree-vectorize janis187 at us dot ibm dot com
@ 2005-09-27 22:52 ` janis187 at us dot ibm dot com
2005-09-27 23:29 ` pinskia at gcc dot gnu dot org
1 sibling, 0 replies; 3+ messages in thread
From: janis187 at us dot ibm dot com @ 2005-09-27 22:52 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From janis187 at us dot ibm dot com 2005-09-27 22:52 -------
Created an attachment (id=9824)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=9824&action=view)
minimized test case
Test case mentioned in the submittal message.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24095
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug middle-end/24095] use of garbage-collected memory with -ftree-vectorize
2005-09-27 22:50 [Bug middle-end/24095] New: use of garbage-collected memory with -ftree-vectorize janis187 at us dot ibm dot com
2005-09-27 22:52 ` [Bug middle-end/24095] " janis187 at us dot ibm dot com
@ 2005-09-27 23:29 ` pinskia at gcc dot gnu dot org
1 sibling, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-09-27 23:29 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-09-27 23:29 -------
There is an even shorter testcase in PR 24049, there was another bug about this somewhere too which
was fixed and a bug which was opened for being able to call ggc_collect in the loop optimizers but I
cannot find either of them right now.
*** This bug has been marked as a duplicate of 24049 ***
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |DUPLICATE
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24095
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-09-27 23:29 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-09-27 22:50 [Bug middle-end/24095] New: use of garbage-collected memory with -ftree-vectorize janis187 at us dot ibm dot com
2005-09-27 22:52 ` [Bug middle-end/24095] " janis187 at us dot ibm dot com
2005-09-27 23:29 ` pinskia at gcc dot gnu dot org
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).