Displaying 18 results from an estimated 18 matches for "memtmp".
Did you mean:
memcmp
2011 Jul 15
2
[LLVMdev] Missing optimization in constant propagation?
...#39;s a missing feature.
I have created the following simple test function in C:
int times_zero(int a)
{
return (a * 0);
}
Compiling this with GCC using dragonegg generates the following code:
%int = type i32
define i32 @times_zero(i32 %a) nounwind {
entry:
%a_addr = alloca i32, align 4
%memtmp = alloca i32
%"alloca point" = bitcast i32 0 to i32
store i32 %a, i32* %a_addr
%"ssa point" = bitcast i32 0 to i32
br label %"2"
"2": ; preds = %entry
store i32 0, i32* %memtmp, align 1
br label %retur...
2011 Aug 16
1
[LLVMdev] Missing metadata for volatile variables
...:8-i16:16:16-i32:32:32-i64:32:64-f32:32:32-f64:32:64-v64:64:64-v128:128:128-a0:0:64-f80:32:32-f128:128:128-n8:16:32"
target triple = "i386-pc-linux-gnu"
module asm "\09.ident\09\22GCC: (GNU) 4.5.2 LLVM: exported\22"
%int = type i32
define i32 @main() nounwind {
entry:
%memtmp = alloca i32
%memtmp1 = alloca i32
%"alloca point" = bitcast i32 0 to i32
%"ssa point" = bitcast i32 0 to i32
br label %"2", !dbg !6
"2": ; preds = %entry
call void @llvm.dbg.declare(metadata !{i32* %mem...
2011 Jul 15
0
[LLVMdev] Missing optimization in constant propagation?
...est function in C:
>
> int times_zero(int a)
> {
> return (a * 0);
> }
>
> Compiling this with GCC using dragonegg generates the following code:
>
> %int = type i32
>
> define i32 @times_zero(i32 %a) nounwind {
> entry:
> %a_addr = alloca i32, align 4
> %memtmp = alloca i32
> %"alloca point" = bitcast i32 0 to i32
> store i32 %a, i32* %a_addr
> %"ssa point" = bitcast i32 0 to i32
> br label %"2"
>
> "2": ; preds = %entry
> store i32 0, i32* %memt...
2012 Feb 29
4
[LLVMdev] Recovering variable names from bitcode
Hello,
I have been facing a few problems getting names of variables from the
bitcode. The bitcode does contain debug metadata. The first problem is
regarding `memtmp' variables (apparently, the original variable name is no
longer present in the bitcode). The other two problems concern OpenMP. In
one case, the instruction is not named and hence establishing a connection
to the debug metadata does not seem possible. In the other case, I am
noticing some extra...
2012 Jan 23
2
[LLVMdev] Possible bug in the dragonegg
..., align 8
@.cst1 = linker_private unnamed_addr constant [15 x i8]
c"bbbbbbbbbbbbbb\00", align 8
@.cst2 = linker_private unnamed_addr constant [24 x i8] c"a = %s, b =
%s, c = %s\0A\00", align 8
define i32 @main(i32 %argc, i8** nocapture %argv) nounwind uwtable ssp {
entry:
%memtmp = alloca [15 x i8], align 1
%memtmp1 = alloca [15 x i8], align 1
%0 = getelementptr inbounds [15 x i8]* %memtmp, i64 0, i64 0
%1 = getelementptr inbounds [15 x i8]* %memtmp1, i64 0, i64 0
call void @llvm.memcpy.p0i8.p0i8.i64(i8* %0, i8* getelementptr
inbounds ([15 x i8]* @.cst, i64 0,...
2012 Jan 24
0
[LLVMdev] Possible bug in the dragonegg
...unnamed_addr constant [15 x i8]
> c"bbbbbbbbbbbbbb\00", align 8
> @.cst2 = linker_private unnamed_addr constant [24 x i8] c"a = %s, b =
> %s, c = %s\0A\00", align 8
>
> define i32 @main(i32 %argc, i8** nocapture %argv) nounwind uwtable ssp {
> entry:
> %memtmp = alloca [15 x i8], align 1
> %memtmp1 = alloca [15 x i8], align 1
> %0 = getelementptr inbounds [15 x i8]* %memtmp, i64 0, i64 0
> %1 = getelementptr inbounds [15 x i8]* %memtmp1, i64 0, i64 0
> call void @llvm.memcpy.p0i8.p0i8.i64(i8* %0, i8* getelementptr
> inbound...
2012 Jan 24
1
[LLVMdev] Possible bug in the dragonegg
...15 x i8]
>> c"bbbbbbbbbbbbbb\00", align 8
>> @.cst2 = linker_private unnamed_addr constant [24 x i8] c"a = %s, b =
>> %s, c = %s\0A\00", align 8
>>
>> define i32 @main(i32 %argc, i8** nocapture %argv) nounwind uwtable ssp {
>> entry:
>> %memtmp = alloca [15 x i8], align 1
>> %memtmp1 = alloca [15 x i8], align 1
>> %0 = getelementptr inbounds [15 x i8]* %memtmp, i64 0, i64 0
>> %1 = getelementptr inbounds [15 x i8]* %memtmp1, i64 0, i64 0
>> call void @llvm.memcpy.p0i8.p0i8.i64(i8* %0, i8* getelementptr
>> inb...
2012 Feb 29
0
[LLVMdev] Recovering variable names from bitcode
On Feb 29, 2012, at 2:59 PM, Ashay Rane wrote:
> I have been facing a few problems getting names of variables from the bitcode. The bitcode does contain debug metadata. The first problem is regarding `memtmp' variables (apparently, the original variable name is no longer present in the bitcode). The other two problems concern OpenMP. In one case, the instruction is not named and hence establishing a connection to the debug metadata does not seem possible. In the other case, I am noticing some extra...
2012 Jan 23
0
[LLVMdev] Possible bug in the dragonegg
Hi Pablo,
> I came across something that seems to be a bug in the dragonegg option that
> emits LLVM IR. ¿Can anybody reproduce the error, or see what's wrong?
I can't reproduce this on x86-64 linux with latest LLVM+dragonegg+gcc-4.6.
¿Should I
> post it somewhere else in case it's really a bug? Thanks ahead!
>
> With this simple program:
> *
> #include
2012 Jan 23
2
[LLVMdev] Possible bug in the dragonegg
Hi all,
I came across something that seems to be a bug in the dragonegg option
that emits LLVM IR. ¿Can anybody reproduce the error, or see what's
wrong? ¿Should I post it somewhere else in case it's really a bug?
Thanks ahead!
With this simple program:
*
#include <stdio.h>
#include <string.h>
int main(int argc, char** argv){
char a[8] = "aaaaaaa";
2012 Feb 29
1
[LLVMdev] Recovering variable names from bitcode
...Wed, Feb 29, 2012 at 4:08 PM, Xi Wang <xi.wang at gmail.com> wrote:
> On Feb 29, 2012, at 2:59 PM, Ashay Rane wrote:
> > I have been facing a few problems getting names of variables from the
> bitcode. The bitcode does contain debug metadata. The first problem is
> regarding `memtmp' variables (apparently, the original variable name is no
> longer present in the bitcode). The other two problems concern OpenMP. In
> one case, the instruction is not named and hence establishing a connection
> to the debug metadata does not seem possible. In the other case, I am
>...
2008 Feb 16
0
[LLVMdev] [llvm-testresults] Grawp-PIC i386 nightly tester results
.../Volumes/Muggles/LLVM/nightlytest-pic/build/llvm/test/C+
+Frontend/2008-02-13-sret.cpp
Failed with exit(1) at line 1
while running: /usr/local/bin/llvm-gcc -emit-llvm -S -O0 -emit-llvm /
Volumes/Muggles/LLVM/nightlytest-pic/build/llvm/test/C++Frontend/
2008-02-13-sret.cpp -o - | grep {retva\
l\|memtmp} | grep S242 | grep {i32 1} | count 1
count: expected 1 lines and got 0.
child process exited abnormally
/usr/local/bin/llvm-gcc -v
Using built-in specs.
Target: i686-apple-darwin9
Configured with: /tmp/llvmgcc42.r46865.roots/llvmgcc42.r46865~obj/src/
configure --disable-checking --enable...
2008 Feb 16
2
[LLVMdev] [llvm-testresults] Grawp-PIC i386 nightly tester results
On Feb 16, 2008, at 11:32 AM, Evan Cheng wrote:
> But I am using llvm-gcc-4.2. Any idea why it's failing?
>
> Evan
All the failing testers are using gcc-4.0 according to the web pages
they point at.
> On Feb 16, 2008, at 11:24 AM, Dale Johannesen wrote:
>
>> On Feb 16, 2008, at 7:06 AM, Apache wrote:
>>> New Test Failures:
>>>
2010 Dec 01
8
[LLVMdev] Alternative exception handling proposal
...t [9 x i8] c"catchall\00", align 1
@llvm.eh.catch.all.value = linkonce constant i8* null, section "llvm.metadata"
@llvm.used = appending global [1 x i8*] [i8* bitcast (i8**
@llvm.eh.catch.all.value to i8*)], section "llvm.metadata"
define void @_Z3barv() {
entry:
%memtmp = alloca %struct.A, align 8
%memtmp1 = alloca %struct.A, align 8
%memtmp2 = alloca %struct.A, align 8
invoke void @_Z3foov()
to label %"3" unwind label %lpad personality @__gxx_personality_v0
catches %struct.__fundamental_type_info_pseudo* @_ZTIi,
%struct.__pointer_t...
2010 Dec 01
0
[LLVMdev] Alternative exception handling proposal
...r the last value is truly the catchall value or for a catch handler.
> "10": ; preds = %"5"
> %exc_ptr31 = call i8* @llvm.eh.exception()
> %filter32 = call i32 @llvm.eh.selector()
> invoke void @_ZN1CD1Ev(%struct.A* %memtmp)
> to label %"11" unwind label %fail personality @__gxx_personality_v0
> catches i32 1 ; <- this is an empty filter, i.e. one that catches everything
>
Filter? What do you mean by this?
> How is it codegened
> -------------------
>
> Code generation i...
2010 Dec 02
3
[LLVMdev] Alternative exception handling proposal
...then there is one on the
invoke, otherwise there is not. There is no special treatment of catch-all.
>> "10": ; preds = %"5"
>> %exc_ptr31 = call i8* @llvm.eh.exception()
>> %filter32 = call i32 @llvm.eh.selector()
>> invoke void @_ZN1CD1Ev(%struct.A* %memtmp)
>> to label %"11" unwind label %fail personality @__gxx_personality_v0
>> catches i32 1 ; <- this is an empty filter, i.e. one that catches everything
>>
> Filter? What do you mean by this?
http://llvm.org/docs/ExceptionHandling.html#throw_filters
>> Will...
2010 Dec 06
4
[LLVMdev] Inlining and exception handling in LLVM and GCC
...ons on the call stack so that there was only a cleanup
there; the code implementing "throw" looked up the call stack, saw that there
were only cleanups, and called terminate rather than unwinding the exception.
Here's the LLVM IR for foo:
define void @_Z3foov() noreturn {
entry:
%memtmp = alloca %struct.X, align 8 ; <= Stack object for variable "x"
%D.2669_1 = call i8* @__cxa_allocate_exception(i64 4) nounwind
%D.2687_2 = bitcast i8* %D.2669_1 to i32*
store i32 1, i32* %D.2687_2, align 4
invoke void @__cxa_throw(i8* %D.2669_1, i8* bitcast
(%struct.__funda...
2010 Dec 02
0
[LLVMdev] Alternative exception handling proposal
...le in Ada. In your code above, the i8* null is indistinguishable from the other types.
>>> "10": ; preds = %"5"
>>> %exc_ptr31 = call i8* @llvm.eh.exception()
>>> %filter32 = call i32 @llvm.eh.selector()
>>> invoke void @_ZN1CD1Ev(%struct.A* %memtmp)
>>> to label %"11" unwind label %fail personality @__gxx_personality_v0
>>> catches i32 1 ; <- this is an empty filter, i.e. one that catches everything
>>>
>> Filter? What do you mean by this?
>
> http://llvm.org/docs/ExceptionHandling.html#th...