public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janis187 at us dot ibm dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/24095] New: use of garbage-collected memory with -ftree-vectorize Date: Tue, 27 Sep 2005 22:50:00 -0000 [thread overview] Message-ID: <20050927225026.24095.janis187@us.ibm.com> (raw) 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
next reply other threads:[~2005-09-27 22:50 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-09-27 22:50 janis187 at us dot ibm dot com [this message] 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
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=20050927225026.24095.janis187@us.ibm.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).