Displaying 20 results from an estimated 6353 matches for "castes".
Did you mean:
cases
2012 Nov 29
2
[LLVMdev] [cfe-dev] UB in TypeLoc casting
Moving to LLVM dev to discuss the possibility of extending the cast
infrastructure to handle this.
On Tue, Nov 20, 2012 at 5:51 PM, John McCall <rjmccall at apple.com> wrote:
> On Nov 18, 2012, at 5:05 PM, David Blaikie <dblaikie at gmail.com> wrote:
>> TypeLoc casting looks bogus.
>>
>> TypeLoc derived types return true from classof when the dynamic type
>>
2012 Nov 30
0
[LLVMdev] [cfe-dev] UB in TypeLoc casting
On Thu, Nov 29, 2012 at 3:49 PM, David Blaikie <dblaikie at gmail.com> wrote:
> Moving to LLVM dev to discuss the possibility of extending the cast
> infrastructure to handle this.
>
> On Tue, Nov 20, 2012 at 5:51 PM, John McCall <rjmccall at apple.com> wrote:
>> On Nov 18, 2012, at 5:05 PM, David Blaikie <dblaikie at gmail.com> wrote:
>>> TypeLoc
2018 Feb 14
1
[vhost:vhost 22/23] drivers/firmware/qemu_fw_cfg.c:130:36: sparse: incorrect type in initializer (different base types)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost
head: 3d22d7c1190db3209b644b8a13a75a9802b4587f
commit: b3a8771f409b74c42deee28aee3092fc5d2c8dab [22/23] fw_cfg: write vmcoreinfo details
reproduce:
# apt-get install sparse
git checkout b3a8771f409b74c42deee28aee3092fc5d2c8dab
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
2005 Jun 09
1
[LLVMdev] gmake check failures on FreeBSD 5.4
FAIL:
/usr/home/jeffc/llvm/obj/../test/Regression/Transforms/InstCombine/2004-11-27-SetCCForCastLargerAndConstant.ll:
%Y = cast sbyte %SB to uint ; <uint> [#uses=1]
%Y = cast sbyte %SB to int ; <int> [#uses=1]
%Y = cast sbyte %SB to int ; <int> [#uses=1]
%Y = cast ubyte %SB to uint ; <uint> [#uses=1]
%Y = cast ubyte %SB to
2007 Feb 24
3
[LLVMdev] cast instruction
I need to create a cast instruction that casts an sbyte* to another
pointer type. Previously I was using the CastInst::createInferredCast()
function to do that; however, that function has been removed. Which of
the create() functions from CastInst should I use to do that? It seems
like the obdvious answer should be createPointerCast(). However, the
documentation for createPointerCast
2013 Apr 21
2
[LLVMdev] How to cast Value* to ConstantDataArray*
ConstantDataArray * cda = cast<ConstantDataArray>(v);
throws this error: Assertion failed: (isa<X>(Val) && "cast<Ty>() argument
of incompatible type!"), function cast, file
/Users/rcatlin1/lldb/llvm/include/llvm/Support/Casting.h, line 208
Thanks for the help.
Richard Catlin
On Sat, Apr 20, 2013 at 3:37 PM, Sean Silva <silvas at purdue.edu> wrote:
2014 Apr 15
2
[LLVMdev] unique_ptr and llvm cast machinery
Anyone have opinions on whether the cast machinery should be taught to
handle unique_ptr?
Presumably that'd involve cast, etc, returning raw pointers when it
was passed references to unique_ptr, which might be
surprising/error-prone?
But the only errors would be:
1) double delete - if the result of the cast was used to take
ownership because the caller didn't realize there was a
2012 Jan 22
0
Compiler warnings: cast from pointer to integer of different size
I encounter the following compiler warnings while compiling kernel 3.3.0-rc1+
...
CC fs/btrfs/super.o
CC fs/btrfs/ctree.o
CC fs/btrfs/extent-tree.o
fs/btrfs/extent-tree.c: In function ‘btrfs_check_data_free_space’:
fs/btrfs/extent-tree.c:3314:11: warning: cast from pointer to integer
of different size [-Wpointer-to-int-cast]
fs/btrfs/extent-tree.c: In function
2017 Jul 14
3
error:Ran out of lanemask bits to represent subregister
Do your 32768 registers also have sub registers?
I can't tell you exactly what to change. I'm not familiar with the code. I
would just be running grep or something.
~Craig
On Fri, Jul 14, 2017 at 10:23 AM, hameeza ahmed <hahmed2305 at gmail.com>
wrote:
> Thank you so much. I think there is no issue with my definitions since i
> have to use larger registers i.e 65536 bit
2017 Jul 19
5
error:Ran out of lanemask bits to represent subregisterr
I have made changes in 3 files:
LaneBitmask.h, codegenregisters.cpp and miparser.cpp. files are attached
here.
Now i am getting following errors. which means registerinfo.inc file is not
generated successfully.
/PIM/lib/Target/X86/MCTargetDesc/X86BaseInfo.h:733:24: error:
no member named 'XMM8' in namespace 'llvm::X86'
if ((RegNo >= X86::XMM8 && RegNo <=
2015 Mar 19
2
[LLVMdev] Cast to SCEVAddRecExpr
Hi Nick,
Thanks for looking into it.
I have tried that as well but it didn't worked.
"AddExpr->getOperand(0))" node is:
" (4 * (sext i32 {2,+,2}<%for.body4> to i64))<nsw>"
When I cast this to "SCEVAddRecExpr" it returns NULL.
Regards,
Ashutosh
-----Original Message-----
From: Nick Lewycky [mailto:nicholas at mxc.ca]
Sent: Thursday, March 19,
2012 Nov 30
3
[LLVMdev] [cfe-dev] UB in TypeLoc casting
On Thu, Nov 29, 2012 at 7:43 PM, Eli Friedman <eli.friedman at gmail.com>wrote:
> On Thu, Nov 29, 2012 at 3:49 PM, David Blaikie <dblaikie at gmail.com> wrote:
> > Moving to LLVM dev to discuss the possibility of extending the cast
> > infrastructure to handle this.
> >
> > On Tue, Nov 20, 2012 at 5:51 PM, John McCall <rjmccall at apple.com> wrote:
2007 Oct 25
0
6 commits - libswfdec/swfdec_as_interpret.c test/trace
libswfdec/swfdec_as_interpret.c | 89 ++++++++++++++++++++++++-------
test/trace/Makefile.am | 9 +++
test/trace/cast-5.swf |binary
test/trace/cast-5.swf.trace | 2
test/trace/cast-6.swf |binary
test/trace/cast-6.swf.trace | 2
test/trace/cast-7.swf |binary
2015 Feb 18
2
[LLVMdev] local variable in Pattern definition?
Hi guys,
When I am trying to define pattern in a multi class, I got something like this:
“
multi class P_PAT<string sty, SDNode tNode>
{
def : Pat<( !cast<ValueType>(“v2” # sty) (tNode !cast<ValueType>(“v2” # sty):$src1, !cast<ValueType>(“v2” # sty):$src2) ),
( add !cast<ValueType>(“v2” # sty):$src1, !cast<ValueType>(“v2” #
2012 Dec 05
0
[LLVMdev] [cfe-dev] UB in TypeLoc casting
On Thu, Nov 29, 2012 at 8:16 PM, Richard Smith <richard at metafoo.co.uk> wrote:
> On Thu, Nov 29, 2012 at 7:43 PM, Eli Friedman <eli.friedman at gmail.com>
> wrote:
>>
>> On Thu, Nov 29, 2012 at 3:49 PM, David Blaikie <dblaikie at gmail.com> wrote:
>> > Moving to LLVM dev to discuss the possibility of extending the cast
>> > infrastructure to
2015 Mar 19
3
[LLVMdev] Cast to SCEVAddRecExpr
Yes, I can get "SCEVAddRecExpr" from operands of "(sext i32 {2,+,2}<%for.body4> to i64)".
So whenever SCEV cast to "SCEVAddRecExpr" fails, we have drill down for such patterns ?
Is that the right way ?
Regards,
Ashutosh
-----Original Message-----
From: Nick Lewycky [mailto:nicholas at mxc.ca]
Sent: Thursday, March 19, 2015 1:02 PM
To: Nema, Ashutosh
Cc:
2015 Mar 19
2
[LLVMdev] Cast to SCEVAddRecExpr
Hi,
I'm trying to cast one of the SCEV node to "SCEVAddRecExpr".
Every time cast return NULL, and I'm unable to do this.
SCEV Node:
((4 * (sext i32 {2,+,2}<%for.body4> to i64))<nsw> + %var)<nsw>
Casting:
const SCEVAddRecExpr *AR = dyn_cast<SCEVAddRecExpr>(SCEVNode);
'var' is of type float pointer (float*).
Without 'sext' it works, but
2007 Nov 21
1
Help Required in using cast (reshape package) function
Hello everyone,
I am new to R. I have data in the form of excel pivot table format and I
want to cast it into a format which can make it compatible with
computation.
Since I already have the package in pivot format; I avoid melt function
and use the cast directly.
I inspect the
dataread <- read.csv(".....", header=TRUE)
Data in the format
Id Region Country Industry
2013 May 24
1
FLAC for Android: warning: cast increases required alignment of target type
Now that I can build FLAC again with Janne's patch I would like to report
about the warnings I get when building for Android:
android-make | grep warn
md5.c: In function 'format_input_':
md5.c:282:25: warning: cast increases required alignment of target type
[-Wcast-align]
md5.c:288:24: warning: cast increases required alignment of target type
[-Wcast-align]
decode.c: In function
2003 Nov 15
2
[LLVMdev] C++ Casting
In compiling my software to use LLVM, I have noticed many occurrences of
C style casting in LLVM header files. Since I compile with the
-Wold-style-cast flag to g++, I get warnings about each of them. This
isn't a big deal but I try to keep my code compilations both error
and warning free (makes spotting true errors easier).
I'm wondering why a new C++ (LLVM) would choose to use C style