Displaying 20 results from an estimated 200 matches similar to: "clang interpreter failed to materialize symbols"
2020 Jan 14
4
clang interpreter failed to materialize symbols
Hi Igor, not sure if that will work, but have you tried lli
-jit-kind=orc-lazy ? The default is still MCJIT:
https://github.com/llvm/llvm-project/blob/master/llvm/tools/lli/lli.cpp#L88
On 13/01/2020 19:07, David Blaikie via llvm-dev wrote:
> (+Lang for JIT/interpreter questions)
>
> On Sun, Jan 5, 2020 at 5:00 PM Igor Gomon via llvm-dev
> <llvm-dev at lists.llvm.org
2020 Jan 16
2
clang interpreter failed to materialize symbols
Hi Stefan,
I just tried the -jit-kind=orc-lazy with lli executable and it solves the problem on Ubuntu 18.04 (still does not work on Windows 10). But this solution is good enough for me now. Thanks again for your help!
--
Best Regards,
Igor
________________________________
From: Igor Gomon <giv_ua at hotmail.com>
Sent: Tuesday, January 14, 2020 7:38 PM
To: Stefan Gränitz
2020 Jan 22
4
Longstanding failing tests - clang-tidy, MachO, Polly
Hi,
A few tests seem broken for a long time, some for more than a month. Would it possible for respective owners to take a look please?
I'm at checkout 133a7e631cee97965e310f0d110739217427fd3d, compiling on Windows 10.
These tests fail with Visual Studio 2019:
Failing Tests (7):
Clang Tools :: clang-tidy/checkers/cert-mem57-cpp-cpp17.cpp
Clang Tools ::
2016 Oct 17
2
Assertion fail/crash in X86FrameLowering::GetFrameIndexReference SEH
Hi,
I'm gettign an assertion fail/crash in
X86FrameLowering::GetFrameIndexReference when compiling the following
bitcode:
https://gist.github.com/carlokok/868cddebeb9acc8ccbac6253de0480b0
I tried removing the llvm.frameaddres calls but that's not it, where can
I start looking for what my mistake here is? Code seems to verify just fine.
; #0 0x00e1afe8
2016 Oct 19
2
Assertion fail/crash in X86FrameLowering::GetFrameIndexReference SEH
I think r262546 introduced the assumption that allocas are used exactly
once with catchpad. It seems easy to fix, though.
On Mon, Oct 17, 2016 at 11:51 PM, Carlo Kok via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> This turned out to be related to reusing the local used in the catchpad,
> for example given the following c++ code:
>
> extern void rthrow();
>
> int
2017 Nov 01
2
llvm.gcroot trouble with non-i8* allocas
I'm allocating { i8*, i32 } on the stack, and would like to add this as a
GC root, but I'm having trouble figuring this out.
This works as expected:
declare void @llvm.gcroot(i8** %ptrloc, i8* %metadata)
define i8* @bar(i8* %x) gc "shadow-stack" {
entry:
%objptr = alloca i8*
call void @llvm.gcroot(i8** %objptr, i8* null)
store i8* %x, i8** %objptr
%v = load i8*, i8**
2017 Nov 01
0
llvm.gcroot trouble with non-i8* allocas
Solved by using alloca i8*, i32 2 which the system seems happy enough with,
and bitcasting to the actual type for rest of the code after llvm.gcroot.
Not entirely sure if this is a terrible workaround or exactly the way
gcroot is supposed to be used...
On Wed, Nov 1, 2017 at 11:59 AM, Nikodemus Siivola <
nikodemus at random-state.net> wrote:
> I'm allocating { i8*, i32 } on the
2015 Oct 05
2
[cfe-dev] Orc Windows C++
It’s pretty intermittent at the moment…sometimes I get the relocation overflow issue, sometimes I get another issue about BSS sections having no contents.
The source code to reproduce either is simple:
#include <iostream>
int main (int argc, char* argv[])
{
}
I’ve managed to reproduce the BSS section issue in clang consistently, and since that comes before terms of where it happens in
2015 Oct 05
2
[cfe-dev] Orc Windows C++
Oops, sorry for the spam.
That last comment was incorrect. It’s IMAGE_REL_AMD64_REL32 not _5
> On 5 Oct 2015, at 17:26, Joshua Gerrard <joshua.gerrard at roli.com> wrote:
>
> Additional info: when the relocation issue does occur the relocation type is IMAGE_REL_AMD64_REL32_5
>
>> On 5 Oct 2015, at 17:16, Joshua Gerrard <joshua.gerrard at roli.com> wrote:
>>
2015 Oct 14
4
[cfe-dev] Orc Windows C++
That's great news, thanks! If I can be of any help, let me know. :)
I'll see if I can reduce the example for the relocation issue whilst you're
at it.
Regards,
Joshua
--
Joshua Gerrard
JUCE Software Developer
*ROLI’s **award-winning*
<http://www.telegraph.co.uk/luxury/design/31520/the-seaboard-grand-piano-wins-designs-of-the-year-2014-award.html>*
Seaboard
GRAND, celebrated
2015 Oct 19
2
[cfe-dev] Orc Windows C++
First of all, thanks very much to Lang for fixing the BSS section bug; works like a charm!
I’ve been unable to reproduce the 32 bit relocation on 64 bit code (I’ll let you know if I do). However, I’m still having issues with resolving the 64 bit symbol relocations. In case it’s relevant, the specific symbol my program is tripping up on is IID_IOleObject, where TargetAddress is dereferenced
2020 Jan 23
2
Longstanding failing tests - clang-tidy, MachO, Polly
So, for this test case:
extern "C" void shouldBeUnconditional();
extern "C" void shouldBeConditional();
extern "C" void otherCall();
void testFn(bool Bool1, bool Bool2) {
Bool1 |= Bool2;
shouldBeUnconditional();
if (Bool1)
shouldBeConditional();
if (Bool2) {
otherCall();
if (Bool1)
otherCall();
}
}
MSVC generates this buggy asm:
$ cl -c
2015 Oct 02
2
[cfe-dev] Orc Windows C++
Thanks for the link!
There’s some code there that looks extremely relevant to say the least.
> On 1 Oct 2015, at 19:00, Hayden Livingston <halivingston at gmail.com> wrote:
>
> Maybe looking at their code might help:
>
> https://github.com/dotnet/llilc/blob/dd12743f9cdb5418f1c39b2cd756da1e8396a922/lib/Jit/LLILCJit.cpp#L299
>
> On Thu, Oct 1, 2015 at 10:45 AM, David
2013 Apr 29
1
[LLVMdev] Many tests fail on Win64
I fell over this issue yesterday myself with lots of asserts being thrown.
I think the issue is in lib/IR/AsmWriter.cpp:1618 in the function
AssemblyWriter::printFunction(const Function *F)
Looking at the code I think the 2nd for loop should be preceded by the test
...
if (Idx < AS.getNumSlots())
Not sure why it doesn't fail on other platforms as it looks like it should
be a genuine
2006 Apr 30
4
renamed partial won''t render?
hi all
this works
<%= render :partial => "admin/works/work", :collection =>
@artist.works %>
but this doesn''t
<%= render :partial => "admin/works/worklist", :collection =>
@artist.works %>
even though the partial _work.rhtml and _worklist.rhtml are identical.
worklist.rhtml throws
undefined local variable or method
2006 Mar 11
5
mboot.c32, weird e820 map on HP blade machine, possible memory corruption
I'm seeing this on a HP Blade and i'm not sure why this is happning since
the nature of the issue is so wierd.
I compiled mboot.c with a DEBUG defined in the mboot.c file. In the funciton
init_mmap(), it prints the e820 map and on the HP blade this map values come
out to be totally random. Some weird numbers which dont make any sense at
all.
However, if i add a while(1); or a exit(1); at
2009 Jan 10
1
Help needed for Loading "tm" package
Howdy Gurus again
Thanks to Tony.Breyal, I was able to writing the following script for
analyzing a text document.
But I got an error with "tm' package. I don't why I got the error from the R
script below. I think I followed proccess of R tm manual.
I use R v2.8.1. and tm_0.3-3.zip under Win XP.
Thanks in advance,
Kum Hwang
> # setting directory
> my.path
2020 Jul 17
5
[PATCH] drm/nouveau: Accept 'legacy' format modifiers
Accept the DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK()
family of modifiers to handle broken userspace
Xorg modesetting and Mesa drivers.
Tested with Xorg 1.20 modesetting driver,
weston at c46c70dac84a4b3030cd05b380f9f410536690fc,
gnome & KDE wayland desktops from Ubuntu 18.04,
and sway 1.5
Signed-off-by: James Jones <jajones at nvidia.com>
---
drivers/gpu/drm/nouveau/nouveau_display.c | 26
2011 Sep 29
1
[LLVMdev] Beginner Question on Linking
I am following along in http://llvm.org/docs/GettingStartedVS.html with a
Hello World bitcode file. I can run the file using the command `lli
HelloWorld.bc`, but now I want to link it into an executable file (on
windows). The next thing the document says to run is `llc -filetype=obj
HelloWorld.bc` which runs fine and now I have a `HelloWorld.obj` file. It's
the last step that is giving me some
2020 Jul 17
1
[PATCH] drm/nouveau: Accept 'legacy' format modifiers
On Fri, Jul 17, 2020 at 11:57:57AM -0700, James Jones wrote:
> Accept the DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK()
> family of modifiers to handle broken userspace
> Xorg modesetting and Mesa drivers.
>
> Tested with Xorg 1.20 modesetting driver,
> weston at c46c70dac84a4b3030cd05b380f9f410536690fc,
> gnome & KDE wayland desktops from Ubuntu 18.04,
> and sway 1.5
>
>