similar to: [LLVMdev] Remaining big-endian host issues in RuntimeDyld

Displaying 20 results from an estimated 200 matches similar to: "[LLVMdev] Remaining big-endian host issues in RuntimeDyld"

2014 Nov 04
2
[LLVMdev] Remaining big-endian host issues in RuntimeDyld
Hi Daniel, Thanks very much - I really appreciate you tracking this down. David - once Daniel's patch goes in it would be interesting to see what impact his work has had on PPC. I expect this will fix some of the tests there too. Regarding the AArch64 stub-addr return: My read is that createStubFunction returns a pointer to the start of the stub for AArch64. Those switch cases are a bit
2013 Jan 05
0
[LLVMdev] RuntimeDyld bug in resolving addresses with offset?
Hi, I believe I came across a bug in RuntimeDyld. I have the following piece of C code (attached as rtdyldbug.c): double numbers[5] = {33, 34, 35, 36, 37}; void foo(double val, double other[]) { other[2] += val * numbers[4]; } I adapted llvm-rtdyld.cpp to load the .o file of the code above, get a pointer to foo, and invoke it (whole thing is attached as myrtdyld.cpp): typedef
2015 Aug 24
2
enumerate symbols in RuntimeDyld
Hi All Is there any technical reason why we can’t or shouldn’t have RuntimeDyld be able to enumerate all symbols in the dyld? I know elf, mach-o apis have this capability, and I’m reasonably sure coff has support for it as well.
2017 Apr 13
2
Using a function from lib/Target/(any arch)/ in lib/ExecutionEngine/RuntimeDyld/
Hello LLVMDevs, I have written a .cpp file in lib/Target/(some arch)/ and i want to use one of its function in a file in lib/ExecutionEngine/RuntimeDyld/. So is there any specific way to do that. This may be a general question for any one who writes a .cpp file in Target/(any arch)/ and tries to use it somewhere in ExecitionEngine/RuntimeDyld/. Please guide. Thanks, Siddharth -------------- next
2014 Aug 19
2
[LLVMdev] [RFC] Adding functions for unaligned load/store to Support for JIT/RuntimeDyld
Hi, I've noticed that certain parts of LLVM (RuntimeDyld, JIT) use unaligned memory accesses to load/store pointers or just 32- or 64-bit integers. Technically, this is undefined behavior, and UBSan reports errors when this happens. Even if we believe we're running some x86-specific code (e.g. RuntimeDyldELF::resolveX86_64Relocation) what matters for unaligned acceses in source code is
2020 Oct 02
2
Memory mapping assumptions in RuntimeDyld
Hi! Implementing the Memory::allocateMappedMemory() function on z/OS, I see a failure in the AArch64 COFF test case. The test case has 3 sections. For each section, Memory::allocateMappedMemory() is called to reserve memory. If the distance between the pointers gets too large, then the test case fails. It can be reliable produced with a distance of 1MB between the pointers. An easy way to
2015 Jan 26
2
[LLVMdev] [llvm] r188726 - Adding PIC support for ELF on x86_64 platforms
Hi Lang, Yeah, I remember this case. Basically what’s happening is that there are relocations for ELF on x86 that use a value that is present in the object image as part of the calculation for the final value that goes in the same location. If you ever find yourself applying relocations for a second time (for instance, because the loaded object location is remapped for out-of-proc execution)
2014 Jun 23
3
[LLVMdev] Proposal: Improved regression test support for RuntimeDyld/MCJIT.
Hi Everyone, For your consideration: A proposal to improve regression test support for RuntimeDyld. Short version: We can make RuntimeDyld far more testable by adding a trivial pointer-expression language that allows us to describe how memory should look post-relocation. Jump down to "The Proposal" for details. Long version: Background: For those unfamiliar with it, RuntimeDyld a
2014 Jun 24
4
[LLVMdev] Proposal: Improved regression test support for RuntimeDyld/MCJIT.
Hi Dave, Jim Grosbach asked the same question, so you're in good company. With hindsight I think it was a mistake to say "FileCheck workflow". What I really meant was that this system plays well with lit. Not that your question about using FileCheck would have been any less valid. I did consider using FileCheck for this, but decided it was the wrong approach. The fundamental reason
2006 Mar 20
0
Only 8 tickets remaining for Next Final Drive (Rails 1.1)
A huge thanks to all the rails developers that worked so hard to improve rails after the 1.0 release! Only 8 tickets remain in the FD report. Next Final Drive (what will be fixed before Rails 1.1) http://dev.rubyonrails.org/report/14 #4234 AR serialization broken with PostgreSQL/Ruby 1.8.2 ActiveRecord David 03/14/06 #4155 type_name_with_module fails, throws Uninitialized Constant
2005 Aug 01
2
scriptaculous: Drag/Drop Sluggish Animation (release animation time should be proportional to remaining distance)
Thomas suggested posting these here so they don''t get lost. Making Scriptaculous Snappy: *) Drag/Drop - make release cost proportional to remaining distance For drag/drop - change the ''release'' animation time to be proportional to the remaining distance the dropped item has to travel. If a user drags the item almost all the way to the final location, the release time
2007 Dec 13
0
xenoprof: flush remaining smples when sampling is stopped.
xenoprof: flush remaining smples when sampling is stopped. Xenoprof notifies guest kernel via VIRQ_XENOPROF when sampled. But it does coarsly based on heuristic so that sometimes VIRQ_XENOPROF isn''t delivered resulting in that oprofile daemon collects no sample. To avoid that situation, always send VIRQ_XENOPROF when sampling is stopped. -- yamahata
2008 Jun 04
3
Util to remove (s)log from remaining vdevs?
After having to reset my i-ram card, I can no longer import my raidz pool on 2008.05. Also trying to import the pool using the zpool.cache causes a kernel panic on 2008.05 and B89 (I''m waiting to try B90 when released). So I have 2 options: * Wait for a release that can import after log failure... (no time frame ATM) * Use a util that removes the log vdev info from the remaining vdevs.
2008 Jul 17
1
Shutdown by battery.remaining or battery.runtime?
On a test shutdown of an APC Back-UPS RS1500 upsc was run periodically to follow the UPS discharge, it showed these values: battery.low 120 battery.charge.low 10 As it turned out, the battery.charge.low was encountered first and the system shut down there. However, considering the rate at which the charge was falling at the end I would much rather have had it shutdown sooner than it did. Is
2002 Feb 19
1
Notepad not remaining language selection
When I use wine's notepad, I select a language in the menu. Languages are displaying. But after closing notepad, the language selection is canceled. Is this not implement or is there a problem ? ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran?ais ! Yahoo! Mail : http://fr.mail.yahoo.com
2016 Jun 02
0
[PATCH 01/20] drm/atomic: Fix remaining places where !funcs->best_encoder is valid
Adapt drm_pick_crtcs() and update_connector_routing() to fallback to drm_atomic_helper_best_encoder() if funcs->best_encoder() is NULL so that DRM drivers can leave this hook unassigned if they know they want to use drm_atomic_helper_best_encoder(). Signed-off-by: Boris Brezillon <boris.brezillon at free-electrons.com> --- drivers/gpu/drm/drm_atomic_helper.c | 4 +++-
2014 May 25
2
[LLVMdev] [AArch64] Remaining broken tests
Hi Tim, There are three remaining broken tests on AArch64 on Gabor's buildbot: http://lab.llvm.org:8011/builders/llvm-aarch64-linux CodeGen/Generic/2011-07-07-ScheduleDAGCrash.ll ** LLVM ERROR: Can't handle live physical register dependency! CodeGen/Generic/asm-large-immediate.ll ** error: invalid operand in inline asm: '/* result: ${0:c} */'
2014 Oct 10
2
[LLVMdev] Remaining Compiler-RT failures in ARM
On 10 October 2014 12:48, Renato Golin <renato.golin at linaro.org> wrote: > 0x0014b494 <+192>: andeq r1, r0, r4, asr #23 > 0x0014b498 <+196>: andseq r8, r2, r12, lsl #24 > 0x0014b49c <+200>: andeq r1, r0, r12, ror r7 > 0x0014b4a0 <+204>: ; <UNDEFINED> instruction: 0x00128bd0 > => 0x0014b4a4 <+208>: ;
2014 Oct 10
2
[LLVMdev] Remaining Compiler-RT failures in ARM
On 10 October 2014 15:30, Evgeniy Stepanov <eugenis at google.com> wrote: > Could this be some kind of linker-generated compatibility magic? I'm not sure. Searching for "____asan_handle_no_return_veneer" on Google gets me this thread. :) I'm tempted to disable that test on ARM+Linux, since we use EHABI instead of SjLj... At least for now... --renato
2016 Aug 30
2
Remaining spam in Bugzilla
Hi! There were several new spam entries in Bugizlla, created from previously created accounts. I think will be good idea to delete them as well as block spammers accounts : Report IDs: 30192, 30191, 30187, 30186, 30185, 30182, 28766, 28717, 28715, 28714. Eugene.