public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "richard at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/27770] [4.2 Regression] wrong code in spec tests for -ftree-vectorize -maltivec
Date: Tue, 06 Jun 2006 16:06:00 -0000	[thread overview]
Message-ID: <20060606155345.3027.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27770-4503@http.gcc.gnu.org/bugzilla/>



------- Comment #14 from richard at codesourcery dot com  2006-06-06 15:53 -------
Subject: Re:  [4.2 Regression] wrong code in spec tests for -ftree-vectorize
-maltivec

"dje at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes:
> We're performing the auto-vectorization in unit-at-a-time-mode, so
> maybe we need to recompile the other functions.  It seems that we're
> going to encounter more problems along these lines with LTO.

Well, I'm not convinced recompilation is the way to go.  I can't imagine
it scaling well in pathological cases.  If we're talking about long-term
fixes, I think we should just make sure that we vectorise all functions
before applying rtl optimisations to any of them.  But that's all moot
anyway: either approach will take a long time to implement.  (Note that,
as things stand, we've already written out the asm code for bar() by the
time we vectorise foo().)

As far as 4.2 fixes go, does anyone disagree with my earlier comment?

Richard


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27770


  parent reply	other threads:[~2006-06-06 15:53 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-25 16:23 [Bug target/27770] New: " janis at gcc dot gnu dot org
2006-05-25 16:31 ` [Bug target/27770] " janis at gcc dot gnu dot org
2006-05-25 16:45 ` pinskia at gcc dot gnu dot org
2006-05-25 17:28 ` dje at gcc dot gnu dot org
2006-05-29 23:18 ` [Bug target/27770] [4.2 Regression] " pinskia at gcc dot gnu dot org
2006-06-04 19:31 ` mmitchel at gcc dot gnu dot org
2006-06-05 10:34 ` steven at gcc dot gnu dot org
2006-06-05 21:01 ` janis at gcc dot gnu dot org
2006-06-05 21:26 ` dje at gcc dot gnu dot org
2006-06-06  9:02 ` rsandifo at gcc dot gnu dot org
2006-06-06 14:34 ` pinskia at gcc dot gnu dot org
2006-06-06 15:10 ` richard at codesourcery dot com
2006-06-06 15:16 ` dje at gcc dot gnu dot org
2006-06-06 15:18 ` richard at codesourcery dot com
2006-06-06 15:23 ` pinskia at gcc dot gnu dot org
2006-06-06 15:43 ` dje at gcc dot gnu dot org
2006-06-06 16:06 ` richard at codesourcery dot com [this message]
2006-06-06 16:37 ` rguenth at gcc dot gnu dot org
2006-06-07 21:52 ` dje at gcc dot gnu dot org
2006-07-02 13:14 ` [Bug middle-end/27770] " hubicka at gcc dot gnu dot org
2006-07-02 13:39 ` richard at codesourcery dot com
2006-07-23 19:04 ` dorit at il dot ibm dot com
2006-07-29 20:30 ` patchapp at dberlin dot org
2006-08-03 20:35 ` dorit at gcc dot gnu dot org
2006-08-04  6:05 ` bonzini at gnu dot org
2006-08-04 16:48 ` janis at gcc dot gnu dot org
2006-08-04 17:03 ` pinskia at gcc dot gnu dot org
2006-08-07  7:09 ` dorit at il dot ibm dot com
2006-08-22 16:06 ` howarth at nitro dot med dot uc dot edu
2006-08-22 16:08 ` 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=20060606155345.3027.qmail@sourceware.org \
    --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).