Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] [PATCH] with no response: Bug 13163 - BlockAddress instruction with use from the global context is damaged during module link"
2012 Oct 02
0
[LLVMdev] [PATCH] with no response: Bug 13163 - BlockAddress instruction with use from the global context is damaged during module link
On 07/05/2012 15:52, Yuri wrote:
> I think my patch fell through the cracks:
> http://llvm.org/bugs/show_bug.cgi?id=13163
>
> Could anybody please check it in?
>
Could anybody please review and check this patch in?
Yuri
2012 Oct 02
0
[LLVMdev] [PATCH] with no response: Bug 13163 - BlockAddress instruction with use from the global context is damaged during module link
Hi Yuri,
On 06/07/12 00:52, Yuri wrote:
> I think my patch fell through the cracks:
> http://llvm.org/bugs/show_bug.cgi?id=13163
>
> Could anybody please check it in?
I think Chris is the right person to look at this, hopefully he will.
Ciao, Duncan.
2013 Apr 18
3
[LLVMdev] [PATCH] with no response: Bug 13163 - BlockAddress instruction with use from the global context is damaged during module link
On 10/02/2012 13:01, Duncan Sands wrote:
>
> I think Chris is the right person to look at this, hopefully he will.
Now 5 months passed. I updated the patch for this current revision.
Can anybody review this and check in please?
http://llvm.org/bugs/show_bug.cgi?id=13163
Yuri
2013 Apr 24
0
[LLVMdev] [PATCH] with no response: Bug 13163 - BlockAddress instruction with use from the global context is damaged during module link
On Apr 17, 2013, at 7:26 PM, Yuri <yuri at rawbw.com> wrote:
> On 10/02/2012 13:01, Duncan Sands wrote:
>>
>> I think Chris is the right person to look at this, hopefully he will.
>
> Now 5 months passed. I updated the patch for this current revision.
> Can anybody review this and check in please?
>
> http://llvm.org/bugs/show_bug.cgi?id=13163
>
2012 Oct 02
1
[LLVMdev] [PATCH] with no response: Bug 13163 - BlockAddress instruction with use from the global context is damaged during module link
Have you sent the patch, with a descriptive header, to the llvm-commits list?
On Oct 2, 2012, at 12:33 AM, Yuri <yuri at rawbw.com> wrote:
> On 07/05/2012 15:52, Yuri wrote:
>> I think my patch fell through the cracks:
>> http://llvm.org/bugs/show_bug.cgi?id=13163
>>
>> Could anybody please check it in?
>>
>
> Could anybody please review and check
2012 Oct 06
1
[LLVMdev] [PATCH] with no response: Bug 13163 - BlockAddress instruction with use from the global context is damaged during module link
On 10/02/2012 13:01, Duncan Sands wrote:
>
> I think Chris is the right person to look at this, hopefully he will.
>
Duncan,
You said the same in the PR comment July 7, 2012, now 3 months have
passed and nothing changed. This patch is still outstanding.
Over time patches may get in conflict with the newer changes so after
the long time patches generally need more attention.
Is there
2012 Jun 17
3
[LLVMdev] BlockAddress instruction is copied instead of cloned during module link?
I have a module having the blockaddress instruction.
When I link it into another module and delete the original, blockaddress
disappears and is replaced by inttoptr (i32 1 to i8*).
Please compile and run the attached program to see the demo of this
problem.
Right after linking modules, blockaddress still exists:
@switch.bbs = internal global [3 x i8*] [i8* blockaddress(@my_func,
2017 Jul 29
2
Storing "blockaddress(@function, %block)" in a global variable?
Hi,
The LangRef warns that "blockaddress(@function, %block)" has a limited and
target-dependent applicability:
https://llvm.org/docs/LangRef.html#addresses-of-basic-blocks
But I wanted very much to save addresses of blocks in a global variable and
so I did:
% cat cond.c
void foo(long *a) { if (a) *a = 0; }
% clang -O1 -c cond.c -fsanitize-coverage=inline-8bit-counters,pc-table
-S
2010 Jun 03
2
[LLVMdev] Is there 'Nop' instruction?
How can I copy the value from another BB?
PHI instruction with one argument would fit, but it requires that all
arguments are in immediately preceding BBs.
Yuri
2010 Jun 01
2
[LLVMdev] How to create global string array? (user question)
I am trying to create such module with API (it's equivalent to c++:
const char* ss[] = {"s1","s2"};):
@ss = global [2 x i8*] [i8* getelementptr inbounds ([3 x i8]* @.str1,
i32 0, i32 0), i8* getelementptr inbounds ([3 x i8]* @.str2, i32 0, i32
0)] ; <[2 x i8*]*> [#uses=0]
@.str1 = private constant [3 x i8] c"s1\00", align 1 ; <[3 x i8]*> [#uses=1]
2015 May 30
2
[LLVMdev] Linking modules across contexts crashes
I get a crash when I try to link multiple modules registered in their
individual contexts.
Documentation for Linker::LinkModules doesn't mention anything about
contexts, and the first link succeeds. But the second link crashes.
Is this not the right way to merge such modules? If not, then what is
the right way?
In any case, documentation for Linker::LinkModules should say if
contexts are
2015 Jun 04
2
[LLVMdev] Linking modules across contexts crashes
> 1. How to find all constants in Module? Does this code find all of them, or
> they are somewhere else too?
> for (GlobalVariable &GV : globals()) {
> if (auto C = static_cast<Constant*>(GV.Op<0>().get())) {
> ... C is Constant*
> }
> }
Constants are unfortunately part of the Context, not the module :-(
Cheers,
Rafael
2011 Aug 16
2
[LLVMdev] --enable-shared doesn't build shared library any more
In r134967 it still worked, and in r137742 it now doesn't.
I used such flags: --enable-assertions --enable-shared --enable-libffi
--enable-debug-runtime --enable-debug-symbols --disable-optimized
Before build would create directory tools/llvm-shlib under the build
tree. Now it is missing.
Yuri
2019 May 06
2
samba-tool max-pwd-age error
On Mon, 6 May 2019 08:21:15 +0000 (UTC)
Billy Bob via samba <samba at lists.samba.org> wrote:
> See:
>
>
>
>
> https://bugzilla.samba.org/show_bug.cgi?id=13873
>
>
> and
>
>
> https://lists.samba.org/archive/samba/2019-March/222141.html
>
>
> These seem related, if not the same.
They are, a bit more investigation, reveals why this has
2014 Mar 31
3
[LLVMdev] Can WriteBitcodeToFile be parallelized?
This function (understandably) takes quite a long time, because it has
to go through each function in module and write its binary.
But it probably can be parallelized if different threads would write
binaries separately, and then merge them together.
Is this implemented or planned?
Yuri
2014 Feb 02
2
[LLVMdev] Why variables get "optimized away" after the last use in unoptimized code?
On 02/02/2014 01:48, David Chisnall wrote:
> In most calling conventions, this is a callee-save register. After its last use, the register allocator may reuse that register. On x86 and ARM, the register that contains this is also (usually) the register used for
But the rule "after the last use, the register allocator may reuse it"
is also introduced by llvm, since register
2010 Jun 19
1
[LLVMdev] Is alloca instruction allowed within the cycle?
I am running this code in JIT on x86 (32 bit).
It crashes when 'alloca %object' instruction is within the body of the
cycle, and it finishes successfully when this instruction is in the
beginning of main (outside the cycle). Crash occurs in the middle of the
cycle after few hundreds of thousands iterations.
What is wrong? Does alloca inside the cycle forces it to allocate it on
stack
2010 Jun 03
0
[LLVMdev] Is there 'Nop' instruction?
Yuri <yuri at rawbw.com> writes:
> How can I copy the value from another BB?
> PHI instruction with one argument would fit, but it requires that all
> arguments are in immediately preceding BBs.
Using a value is not restricted to the BB where you created it.
2010 Jun 10
3
[LLVMdev] clang build fails if done in the separate object directory
I did these steps:
* checked out llvm trunk, and clang trunk
* created symbolic link llvm/tools/clang
* created separate folder: llvm-objects
* run configure and gmake in llvm-objects
It builds ok until it hits clang, at which point I get an this error:
gmake[2]: Entering directory `/tmp/llvm-svn/llvm-objects/tools/clang'
Makefile:44: Makefile.config: No such file or directory
Makefile:127:
2010 Jun 16
1
[LLVMdev] Should file opening error during raw_fd_stream::raw_fd_stream exit instead of passing the error up to the caller?
In several places, for example in JITDebugRegisterer::MakeELF, stream is
opened and the error is ignored. When the error is actually returned by open
There are two solutions (assuming there are no exceptions).
1. check error string after every raw_fd_stream::raw_fd_stream, fix all
the places where the check is missing
2. make raw_fd_stream::raw_fd_stream exit
I suggest the second should be