public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Victor Kaplansky <VICTORK@il.ibm.com>
To: Zdenek Dvorak <rakdver@kam.mff.cuni.cz>
Cc: gcc-patches@gnu.org
Subject: Re: [PATCH] [4.3 projects] Verctorizer - versioning for alias
Date: Tue, 14 Aug 2007 12:23:00 -0000	[thread overview]
Message-ID: <OF94C78A7C.48FF497A-ONC2257337.0041683C-C2257337.0041FC1E@il.ibm.com> (raw)
In-Reply-To: <20070814113727.GB30867@kam.mff.cuni.cz>



Zdenek Dvorak <rakdver@kam.mff.cuni.cz> wrote on 14/08/2007 02:37:27 PM:

>
> could you also add some test that checks the situation where the IN and
> OUT pointers overlap in such a way that the vectorized copy of the loop
> would produce wrong results (if it were used)?

OK, I'll add some.

>
> There should be an empty line between the comment and the function.
>

OK.

> > +                logical and operation.
>
>                    ^ with
>
> > +   LOOP_VINFO - fields of the loop information are used.
>
>                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ I am not
>          sure what this sentence is supposed to mean.

I'll fix this.

>
> > +      part_cond_expr =
> > +         fold_build2 (TRUTH_OR_EXPR, boolean_type_node,
> > +     fold_build2 (LT_EXPR, boolean_type_node,
> > +       fold_build2 (PLUS_EXPR, ptr_type_node,
>
>                          ^^^^^^^^^
> should be POINTER_PLUS_EXPR.  It is a bit suspicious that this passes
> testing, as it should ICE in build2.  Can you check why it does not?

Interesting indeed. I'll try to step thru build2 to see why it doesn't ICE.
Anyway, I'll replace PLUS_EXPR by POINTER_PLUS_EXPR.

> The params should be documented in invoke.texi.
OK, I'll ad the docimentation.

 Otherwise, the patch is
> OK.
>
> Zdenek

Thanks, I'll resend fixed patch shortly.
-- Victor

  reply	other threads:[~2007-08-14 12:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-14 11:02 Victor Kaplansky
2007-08-14 11:38 ` Zdenek Dvorak
2007-08-14 12:23   ` Victor Kaplansky [this message]
2007-08-14 17:07 ` Dorit Nuzman
     [not found] <OF128D770D.7C095078-ONC2257337.00562B23-C2257337.005E3D6E@LocalDomain>
2007-08-16 11:07 ` Victor Kaplansky
2007-08-16 13:09   ` Dorit Nuzman
     [not found] <OF531586B8.1BD86F22-ONC2257339.0046568C-C2257339.00487D11@LocalDomain>
2007-08-16 13:49 ` Victor Kaplansky
     [not found] <OFD8F5F2C8.37DFE3DF-ONC2257339.004A59E3-C2257339.004BD2B1@LocalDomain>
2007-08-18  7:54 ` Dorit Nuzman
2007-08-19  9:20 ` Dorit Nuzman
2007-08-19 15:13 ` Dorit Nuzman

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=OF94C78A7C.48FF497A-ONC2257337.0041683C-C2257337.0041FC1E@il.ibm.com \
    --to=victork@il.ibm.com \
    --cc=gcc-patches@gnu.org \
    --cc=rakdver@kam.mff.cuni.cz \
    /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).