From: Daniel Jacobowitz <drow@false.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Dorit Nuzman <DORIT@il.ibm.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Create VECTOR_CST instead of CONSTRUCTORs where possible in the vectorizer (PR tree-optimization/33993)
Date: Wed, 07 Nov 2007 17:05:00 -0000 [thread overview]
Message-ID: <20071107170501.GA27807@caradoc.them.org> (raw)
In-Reply-To: <20071107170051.GP5451@devserv.devel.redhat.com>
On Wed, Nov 07, 2007 at 12:00:51PM -0500, Jakub Jelinek wrote:
> Actually, this is ppc64-linux -m32 -maltivec, no -mabi=altivec, so
> these regs aren't call_used, but must be saved by foo when they are used.
> But they don't seem to be saved/restored even when foo uses them...
I posted a patch for this a couple of weeks ago. Ulrich Weigand has
since suggested a better approach but I haven't had time to revise
yet.
http://sourceware.org/ml/gdb-patches/2007-10/msg00758.html
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-11-07 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 12:13 Jakub Jelinek
2007-11-06 2:44 ` Mark Mitchell
2007-11-07 3:19 ` Dorit Nuzman
2007-11-07 16:37 ` Jakub Jelinek
2007-11-07 17:01 ` Jakub Jelinek
2007-11-07 17:05 ` Daniel Jacobowitz [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=20071107170501.GA27807@caradoc.them.org \
--to=drow@false.org \
--cc=DORIT@il.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
/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).