Displaying 9 results from an estimated 9 matches for "01lc".
Did you mean:
015c
2009 Jan 10
2
[LLVMdev] How to represent zero-sized string?
...uot;\0"
The difference seems innocent enough. However, in objc if the zero-
sized string is part of a cfstring, it causes a problem. The linker
expects it in the readonly __cstring section, but llvm puts it in the
read / write bss section.
The problem is llvm represents this as
@"\01LC" = internal constant [1 x i8] zeroinitializer
CodeGen can tell it should go into a read only section, but it cannot
know it's a cstring. Any ideas how I can fix this? If I write the zero-
sized string as c"A\00", bitcode reader still turns it back to
zeroinitializer.
Thank...
2009 Jan 27
4
[LLVMdev] RFC: -fwritable-strings Change
...;
I should have put this in darwin.h and called it from there. I think
that there is a far more fundamental problem that affects more than
Objective-C. Even with C code, we place a null string in a writable
section, which isn't correct. I've attached the .bc file. The culprit
is the @"\01LC" global. (This is generated with my hack, so it has an
explicit "section".) Any suggestions for a back-end fix would be
welcome, as I'm not a huge fan of hacking the front-end to get the
sections for symbols correct. :-)
-bw
-------------- next part --------------
A non-text att...
2009 Jan 10
0
[LLVMdev] How to represent zero-sized string?
...That seems extremely weird... what sort of magic is objc using that
could possibly care where a string is stored? Can you give a more
complete testcase? It sounds like LLVM isn't modelling something
which it really should be...
> The problem is llvm represents this as
>
> @"\01LC" = internal constant [1 x i8] zeroinitializer
>
> CodeGen can tell it should go into a read only section, but it cannot
> know it's a cstring. Any ideas how I can fix this? If I write the zero-
> sized string as c"A\00", bitcode reader still turns it back to
> zero...
2009 Jan 27
0
[LLVMdev] RFC: -fwritable-strings Change
...this in darwin.h and called it from there. I think
> that there is a far more fundamental problem that affects more than
> Objective-C. Even with C code, we place a null string in a writable
> section, which isn't correct. I've attached the .bc file. The culprit
> is the @"\01LC" global. (This is generated with my hack, so it has an
> explicit "section".) Any suggestions for a back-end fix would be
> welcome
Fix commited :) Actually it was my fault. We have ConstantArray stuff
for everything string-like but non-zero and ConstantAggregateZero for
st...
2008 Oct 22
9
[LLVMdev] Helping the optimizer along (__assume)
Hi,
I'm interested in whether or not there is a way of providing
source-level annotations to help LLVM with optimizations, similar to
VisualC++'s __assume facility
(http://msdn.microsoft.com/en-us/library/1b3fsfxw.aspx).
As part of our PHP compiler (phpcompiler.org), it would be great to be
able to annotate our generated C code with, for example, (var !=
NULL), or (var->type ==
2009 Jan 27
0
[LLVMdev] RFC: -fwritable-strings Change
Hello, Bill
>>
>> I don't see anything obvious wrong, but this is an easy area to
>> break.
>> I'd recommend running the gcc testsuite and checking for regressions.
>>
> Okay, that's a good plan.
I'm strongly agains any target-specific and language-specific hacks in
the generic tree-conversion code. What if we decide to support objc on
2009 Jan 28
3
[LLVMdev] uses of unwind lead to crashes
...re i32 12, i32* %reg_36
%reg_37 = getelementptr {i32, [2 x i32]}* %reg_34, i32 0, i32 1, i32 1
store i32 16, i32* %reg_37
%reg_38 = bitcast {i32, [2 x i32]}* %reg_34 to %packed_args*
%reg_39 = call i32 @dispatch(%eframe* %reg_23,i32
%reg_30,%packed_args* %reg_38)
ret i32 %reg_39
}
@"\01LC" = internal constant [3 x i8] c"%d\00" ; <[3 x i8]*> [#uses=1]
@"\01LC1" = internal constant [6 x i8] c"false\00" ; <[6 x i8]*>
[#uses=1]
@"\01LC2" = internal constant [5 x i8] c"true\00" ; <[5 x i8]*>
[#uses=1]
@"...
2009 Jan 27
2
[LLVMdev] RFC: -fwritable-strings Change
On Mon, Jan 26, 2009 at 4:45 PM, Dale Johannesen <dalej at apple.com> wrote:
>
> On Jan 26, 2009, at 4:07 PMPST, Bill Wendling wrote:
>
>> There is a problem with Objective-C code where a null string is placed
>> in the wrong section. If we have this code:
>>
>> #include <Foundation/Foundation.h>
>> void foo() {
>> NSLog(@"");
2014 Mar 07
3
[LLVMdev] [RFC] Add second "failure" AtomicOrdering to cmpxchg instruction
...er-remat.ll
+++ b/test/CodeGen/X86/coalescer-remat.ll
@@ -5,7 +5,7 @@
define i32 @main() nounwind {
entry:
- %0 = cmpxchg i64* @val, i64 0, i64 1 monotonic
+ %0 = cmpxchg i64* @val, i64 0, i64 1 monotonic monotonic
%1 = tail call i32 (i8*, ...)* @printf(i8* getelementptr ([7 x i8]* @"\01LC", i32 0, i64 0), i64 %0) nounwind
ret i32 0
}
diff --git a/test/CodeGen/X86/nocx16.ll b/test/CodeGen/X86/nocx16.ll
index cceaac4..8b995da 100644
--- a/test/CodeGen/X86/nocx16.ll
+++ b/test/CodeGen/X86/nocx16.ll
@@ -2,7 +2,7 @@
define void @test(i128* %a) nounwind {
entry:
; CHECK: __syn...