Displaying 20 results from an estimated 231 matches for "koks".
Did you mean:
kok
2016 Nov 27
3
llvm optimizer turning musttail into tail
r287955 seems like it might be related.
-- Sean Silva
On Sat, Nov 26, 2016 at 4:06 PM, Sean Silva <chisophugis at gmail.com> wrote:
> This sounds buggy to me. What pass is doing this?
>
> -- Sean Silva
>
> On Thu, Nov 24, 2016 at 5:39 AM, Carlo Kok via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
>>
>> I've got some calls like:
>>
2008 Sep 03
1
request.remote_ip returns kok + ip
What is this? When I use request.remote_ip in my rails app and print it
to a web page it says "kok" and then the ip. What is that word there
for?
--
Posted via http://www.ruby-forum.com/.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email
2018 Jul 30
3
lld/mach-o x86_64 asserts
Sorry, I was thinking to review the test but didn't.
Is this test complete? It does invoke lld, but it didn't verify its output.
On Mon, Jul 30, 2018 at 2:03 PM Andrew Kelley <superjoe30 at gmail.com> wrote:
> Ping Rui. Is there anything else that needs to be done on this patch?
>
> On Tue, Jul 17, 2018 at 6:58 AM, Carlo Kok via llvm-dev <
> llvm-dev at
2019 May 08
2
taskpool exhaustion in lld/wasm
It's a wasm testcase that ends up with a 1 mb executable; after 15 minutes I killed it, it doesn't do anything (note that it's waiting on a conditional variable in ALL threads)
On Wed, May 8, 2019, at 14:32, Brian Cain wrote:
> Are you sure it's not just taking "a long time"? If that build machine doesn't have enormous amounts of memory you could end up with a
2016 Nov 24
3
llvm optimizer turning musttail into tail
I've got some calls like:
musttail call void bitcast (i32 (i32, i8*, %Type*)* @MyMethod to void
(i32, i8*)*)(i32 %0, i8* %1)
ret void
Into something like:
%8 = tail call i32 @MyMethod(i32 %0, i8* %1, %Type* null)
ret void
I realize I'm losing a parameter there, but this is an interface jump
trick I use and relies on the end code being a 'jmp' (x86). I realize i
can probably
2017 May 30
2
Missing symbol __executable_start on Android when linking with LLD
When linking a project with lld, the android libc links to
__executable_start
which isn't defined when linking with lld (tried on x86), but is when
linking with gnu ld it seems.
I tried:
.globl __executable_start
__executable_start = __ehdr_start
as a workaround but seems to be ignored.
Anyone know a better workaround?
Thanks,
--
Carlo Kok
RemObjects Software
2017 May 30
2
Missing symbol __executable_start on Android when linking with LLD
Android libc casts its address to the elf header type. So I think start of text?
Rafael Avila de Espindola <rafael.espindola at gmail.com> schreef op 30 mei 2017 20:51:19 CEST:
>It is missing from lld.
>
>Do you know what it should point to? The first executable PT_LOAD?
>
>Thanks,
>Rafael
>
>Carlo Kok via llvm-dev <llvm-dev at lists.llvm.org> writes:
>
2009 Dec 28
9
mkdir this "." directory
Hi
I have this . folder under tmp
1/ How they can make it this folder?
2/ How can I remove it?
Thank you
Send instant messages to your online friends http://uk.messenger.yahoo.com
2018 Mar 30
0
[LLD] Mixing bitcode and native code
The problem is a bitcode implementation that has a stdcall function that's used from native code. 1 side has _elements_exception_handler, compiled that would be __elements_exception_handler at 20 due to stdcall. The native bit has the mangled name and the linker can't find it as the bitcode indexes have it without mangling.
I'll try to prepare a testcase when I get back in the office.
2018 Mar 30
2
[LLD] Mixing bitcode and native code
Mixing native and bitcode files should just work, and that happens all the
time, as most programs need at least crt.o (which is a precompiled native
object file containing startup code).
Could you elaborate the issue a bit? It might be a bug in lld.
On Fri, Mar 30, 2018 at 3:11 AM Carlo Kok via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> On Fri, Mar 30, 2018, at 11:23, Carlo Kok
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
2018 Jul 17
2
lld/mach-o x86_64 asserts
Got it.
Attached are both the testcase & the fix.
On Tue, Jul 17, 2018, at 12:06, Carlo Kok via llvm-dev wrote:
> On Wed, Jul 11, 2018, at 16:45, Davide Italiano wrote:
> > On Tue, Jul 10, 2018 at 10:12 PM Carlo Kok via llvm-dev
> > <llvm-dev at lists.llvm.org> wrote:
> > >
> > > That sounds quite reasaonable; how does one usually go about doing that?
2009 Jan 14
6
hardware info
Hi
How can I know the hardware info eg: type of memory
No need to turn off the machine
Thank you
2018 Mar 30
1
[LLD] Mixing bitcode and native code
Clang may be avoiding this problem because it will always emit
"\01__elements_exception_handler at 20" as the function name. It probably does
that for precisely this reason.
On Fri, Mar 30, 2018 at 11:55 AM Carlo Kok via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> The problem is a bitcode implementation that has a stdcall function that's
> used from native code. 1
2018 Jan 25
2
llvm::UpgradeDebugInfo does a full verification
Op 24-1-2018 om 18:26 schreef Adrian Prantl:
>
>
>> On Jan 23, 2018, at 11:01 PM, Carlo Kok via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>>
>> Hi,
>>
>> I noticed that since recently UpgradeDebugInfo (Which is called for loading any bitcode from disk/memory) does a full bitcode verification. Is this on purpose or is this a mistake? Seems to have a
2017 Sep 18
5
Interleaved debug info on arm
When compiling code with lld -O0 --lto-O0 --eh-frame-hdr I get strange interleaved line info all
over the place:
...
0x00000000000595ac 22 11 1 0 0 is_stmt
0x00000000000595bc 25 7 1 0 0 is_stmt <<<
0x00000000000595c0 22 11 1 0 0 is_stmt
0x00000000000595c4 25 7 1 0 0 is_stmt <<<
0x00000000000595c8 26 7 1 0 0 is_stmt
but the code only has 1 reference to line 25 and the
2016 Jun 01
2
linkonce_odr & coff
I have @_rtti_a_a = linkonce_odr constant in two files that end up as
coff object files. Shoudln't the linkonce_odr prevent duplicate symbol:
__rtti_a_a \consoleapplication149.o and __rtti_a_a island.lib(island.o)
from happening in LLD?
If not what alternative can I use? THis is used for template like
generics, so having duplicate functions and globals is going to happen a
lot)
(Side
2019 May 08
2
taskpool exhaustion in lld/wasm
On a 12" MacBook (2017) with 2 cores I get lld/wasm to be stuck in:
https://gist.githubusercontent.com/carlokok/1a14e7ed3dbbd54511e1f0b3a7d684ff/raw/19267560b584ca42cc66f44f508df5b34102d803/thread%2520for%2520waiting
It seems the outer for loop exhausts the thread pool, and the inner ones trigger a new parallel for which never finishes because the pool is full. Is this a bug or am I
2018 Jan 25
0
llvm::UpgradeDebugInfo does a full verification
> On Jan 24, 2018, at 10:47 PM, Carlo Kok <ck at remobjects.com> wrote:
>
>
>
> Op 24-1-2018 om 18:26 schreef Adrian Prantl:
>>> On Jan 23, 2018, at 11:01 PM, Carlo Kok via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>>>
>>> Hi,
>>>
>>> I noticed that since recently UpgradeDebugInfo (Which is called for loading any
2014 Sep 15
2
[LLVMdev] codeview debug info in Visual Studio
Hi,
Is there any way to debug the codeview output of llvm from within Visual
Studio?
I want to use the codeview line info debug output of clang/llvm. I tried
with the
x86_64-pc-windows-msvc and i686-pc-windows-msvc triples and linking it
into an
existing project with VC++ from within the IDE and outside with link
/debug.
Neither option lets me debug with Visual Studio as debugger host.