public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/24378] [4.1/4.2 Regression] gcc.dg/vect/pr24300.c (test for excess errors) fails
Date: Wed, 07 Dec 2005 18:18:00 -0000	[thread overview]
Message-ID: <20051207181806.4810.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24378-230@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from ebotcazou at gcc dot gnu dot org  2005-12-07 18:18 -------
[Thanks for the very detailed plan.]

> You can assign this to me, but I won't be able to get to this for the next
> week, so maybe I better have it assigned to me when I actually have time to
> work on this (in about a week, if it's not fixed by then). Either way is fine
> with me. 

I think I can try to implement what you have sketched, but only for mainline,
as I'll first need to familiarize myself further with Tree-SSA and the
vectorizer, and this is low priority for the time being.  I probably won't be
able to do so in time for the 4.1 release.

So it's up to you to decide what to do for the 4.1 branch.  I personally think
that punting would be just fine there, at least until we have a real fix.  So
I'd lean towards installing the workaround on the 4.1 branch only and leaving
the PR open until you or I get a chance to really tackling the problem.

What do you think?


-- 


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


  parent reply	other threads:[~2005-12-07 18:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-14 23:53 [Bug target/24378] New: " jsm28 at gcc dot gnu dot org
2005-10-16  5:47 ` [Bug target/24378] " phython at gcc dot gnu dot org
2005-11-20 22:18 ` [Bug target/24378] [4.1 Regression] " phython at gcc dot gnu dot org
2005-12-05  8:52 ` ebotcazou at gcc dot gnu dot org
2005-12-06  9:22 ` [Bug target/24378] [4.1/4.2 " ebotcazou at gcc dot gnu dot org
2005-12-07 16:35 ` dorit at il dot ibm dot com
2005-12-07 18:18 ` ebotcazou at gcc dot gnu dot org [this message]
2005-12-07 20:49 ` dorit at il dot ibm dot com
2005-12-08  8:33 ` ebotcazou at gcc dot gnu dot org
2005-12-14 15:38 ` dorit at il dot ibm dot com
2005-12-14 16:38 ` [Bug tree-optimization/24378] " ebotcazou at gcc dot gnu dot org
2005-12-18  8:46 ` dorit at gcc dot gnu dot org
2005-12-18 11:20 ` dorit at gcc dot gnu dot org
2005-12-22 13:05 ` 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=20051207181806.4810.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).