llvm dev - Jul 2011 - [LLVMdev] r135144

Nadav,
   Is
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20110711/123994.html
the full
implementation of vector-select to fix http://llvm.org/bugs/show_bug.cgi?id=2314
or are there
still more parts of this to be committed? If PR2314 is fixed, hopefully Duncan
can get dragonegg
fixed for current llvm svn soon so we can confirm that fixing PR2314 also fixed
PR9716 and PR10018
as well.
       Jack

Hi Jack, 

The vector-select patch is not ready yet. R135144 is only a small increment. I
am close to finishing the
type-legalization work, after which implementing the vector-select x86 support
would be easy.  I will write
to LLVM-dev when I am close to finishing this. 

Thanks for checking, 
Nadav

-----Original Message-----
From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On
Behalf Of Jack Howarth
Sent: Thursday, July 14, 2011 15:54
To: llvmdev at cs.uiuc.edu
Cc: llvm-commits%40cs.uiuc.edu at bromo.med.uc.edu
Subject: [LLVMdev] r135144

Nadav,
   Is
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20110711/123994.html
the full
implementation of vector-select to fix http://llvm.org/bugs/show_bug.cgi?id=2314
or are there
still more parts of this to be committed? If PR2314 is fixed, hopefully Duncan
can get dragonegg
fixed for current llvm svn soon so we can confirm that fixing PR2314 also fixed
PR9716 and PR10018
as well.
       Jack
_______________________________________________
LLVM Developers mailing list
LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

On Thu, Jul 14, 2011 at 05:12:12PM +0300, Rotem, Nadav
wrote:
> Hi Jack, 
> 
> The vector-select patch is not ready yet. R135144 is only a small
increment. I am close to finishing the
> type-legalization work, after which implementing the vector-select x86
support would be easy.  I will write
> to LLVM-dev when I am close to finishing this. 
> 
> Thanks for checking, 
> Nadav
Nadav,
    FYI, the last major issue with dragonegg on gcc 4.6.1 was resolved today...

http://llvm.org/bugs/show_bug.cgi?id=10200

which leaves PR2314 as our biggest issue. Is there an ETA for patches to enable
vector-select?
My main concern is that we able to test dragonegg against those well before llvm
3.0 branches
for release in case this exposes a whole new set of bugs with
-fplugin-arg-dragonegg-enable-gcc-optzns
that may be currently obscured by PR2314. Thanks in advance for any information.
                 Jack
> 
> -----Original Message-----
> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at
cs.uiuc.edu] On Behalf Of Jack Howarth
> Sent: Thursday, July 14, 2011 15:54
> To: llvmdev at cs.uiuc.edu
> Cc: llvm-commits%40cs.uiuc.edu at bromo.med.uc.edu
> Subject: [LLVMdev] r135144
> 
> Nadav,
>    Is
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20110711/123994.html
the full
> implementation of vector-select to fix
http://llvm.org/bugs/show_bug.cgi?id=2314 or are there
> still more parts of this to be committed? If PR2314 is fixed, hopefully
Duncan can get dragonegg
> fixed for current llvm svn soon so we can confirm that fixing PR2314 also
fixed PR9716 and PR10018
> as well.
>        Jack
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
> ---------------------------------------------------------------------
> Intel Israel (74) Limited
> 
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.