search for: macp

Hi Rafael, comment explanation added now. Thanks. On Tue, Jan 14, 2014 at 8:31 PM, Rafael Espíndola < rafael.espindola at gmail.com> wrote: > LGTM with a comment explaining the issue. > > On 20 December 2013 03:50, Andrew MacPherson <andrew.macp at gmail.com> > wrote: > > Thanks Joerg. > > > > I've made the change you suggested and verified that it still works. I > think > > the noinline is still required though as this function can be called > from a > > couple of places...

...ouple of places and gdb will want to set its breakpoint on the single function address. Let me know if you think otherwise though. Cheers, Andrew On Fri, Dec 20, 2013 at 11:52 AM, Joerg Sonnenberger < joerg at britannica.bec.de> wrote: > On Fri, Dec 20, 2013 at 11:18:46AM +0100, Andrew MacPherson wrote: > > This patch forces it to leave the call using the method described here in > > the 'noinline' section: > > Use asm volatile("":::"memory") to make sure that it doesn't leave > trackes. The noinline can likely go in that case... &g...

Wouldn't LLVM_ATTRIBUTE_USED be the correct thing here to prevent dead stripping, if that's the problem? On Wed, Jan 15, 2014 at 8:46 AM, Rafael Espíndola < rafael.espindola at gmail.com> wrote: > LGTM. Do you have commit access? > > On 15 January 2014 00:27, Andrew MacPherson <andrew.macp at gmail.com> wrote: > > Hi Rafael, comment explanation added now. Thanks. > > > > > > On Tue, Jan 14, 2014 at 8:31 PM, Rafael Espíndola > > <rafael.espindola at gmail.com> wrote: > >> > >> LGTM with a comment explaining...

Has anyone been able to sucessfully use 2-4 X101P clones with Asterisk on a single system ? I'm using one Encore MD 3200 modem sucessfully, alongside a TDM400P (3 FXS, 1 FXO) and would like to be able to use up to 4 X101P on a single system. In most cases I'll have 2 or 3 instead. I understand all the issues with interrupt sharing and PC motherboard quality. Just need to know if any

If it's a Windows-only thing the correct tests would be: if (NumBytes >= 4096 && STI.isOSWindows()) { and if (Subtarget->isTargetWindows()) where bool isOSWindows() const { return TargetTriple.isOSWindows(); } Yaron 2013/10/23 Andrew MacPherson <andrew.macp at gmail.com> > Glad that helped! As I understand it __chkstk is always required on > Windows regardless of output type, I had meant to file a bug about this but > had apparently forgotten to do so. I think the check needs to be that the > target is Windows and...

...m.sin.f32 intrinsic, as the X86 processor family does have an instruction for that, but I still get the same problem. While you may still be right, there is at least something else going on as well. Thanks for your input, though. Taco. ---------------------------------------- From: "Andrew MacPherson" <andrew.macp at gmail.com> Sent: Thursday, September 19, 2013 10:36 AM To: taco at heddesit.nl Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] JIT compiled intrinsics calls is call to null pointer Hi Taco, We had a similar issue where a math intrinsic was being converted to a...

...rrect tests would be: > > if (NumBytes >= 4096 && STI.isOSWindows()) { > > and > > if (Subtarget->isTargetWindows()) > > where > > bool isOSWindows() const { return TargetTriple.isOSWindows(); } > > Yaron > > > > 2013/10/23 Andrew MacPherson <andrew.macp at gmail.com> > >> Glad that helped! As I understand it __chkstk is always required on >> Windows regardless of output type, I had meant to file a bug about this but >> had apparently forgotten to do so. I think the check needs to be that the >> t...

Yeah, take a look at the IntelJITEventListener code (in lib/ExecutionEngine/IntelJITEvents). It uses the debug info to find function names. -Andy From: Andrew MacPherson [mailto:andrew.macp at gmail.com] Sent: Wednesday, November 13, 2013 1:12 PM To: Kaylor, Andrew Cc: Reid Kleckner; llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] Stack traces from JIT code Hi Andy, In the NotifyObjectEmitted method of our derived JITEventListener class we use the begin_symbo...

.... > > So, should I patch both tests? > Is the correct patch removing the test isTargetCOFF() completely? > Or enabling it for both COFF or ELF tarrgets? > I mean - is there any X86 target that does NOT require this stack checking? > > Yaron > > > > 2013/10/23 Andrew MacPherson <andrew.macp at gmail.com> > >> Hi Yaron, >> >> If you're outputting ELF on Windows this sounds like an issue we ran into >> where __chkstk calls weren't being output in the assembly due to an >> explicit check for COFF output. Once stack allocat...

...lem thus it is probably required for other reasons. So, should I patch both tests? Is the correct patch removing the test isTargetCOFF() completely? Or enabling it for both COFF or ELF tarrgets? I mean - is there any X86 target that does NOT require this stack checking? Yaron 2013/10/23 Andrew MacPherson <andrew.macp at gmail.com> > Hi Yaron, > > If you're outputting ELF on Windows this sounds like an issue we ran into > where __chkstk calls weren't being output in the assembly due to an > explicit check for COFF output. Once stack allocations in a given function...

Hi, I'm wondering about the status of Windows x64 unwind info in LLVM. We're trying to print a simple stack trace on Windows exceptions, including function names of JITted code (which we can roughly derive using addresses from a JITEventListener). While this works fine in 32-bit mode, we're unable to properly walk the stack in 64-bit since the unwind info doesn't seem to be

...> that’s visible via either the ELF headers or the DWARF information. Do you > have functions that don’t show up in either of those places? > > > > -Andy > > > > *From:* llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] *On > Behalf Of *Andrew MacPherson > *Sent:* Wednesday, November 13, 2013 9:23 AM > *To:* Reid Kleckner > *Cc:* llvmdev at cs.uiuc.edu > *Subject:* Re: [LLVMdev] Stack traces from JIT code > > > > We implemented a similar solution for handling crashes in production but > one issue we came across with...

We implemented a similar solution for handling crashes in production but one issue we came across with MCJIT was that the NotifyFunctionEmitted call from the old JIT was replaced with NotifyObjectEmitted. The ObjectImage used by NotifyObjectEmitted does have a way of iterating symbols but non-external functions used in the module didn't seem to appear in this list so we were left with some

Hi Yaron, If you're outputting ELF on Windows this sounds like an issue we ran into where __chkstk calls weren't being output in the assembly due to an explicit check for COFF output. Once stack allocations in a given function exceeded some amount we'd get exactly this kind of crash in the function initialization. If you take a look for isTargetCOFF() in

Yes, this is correct code address accessing bad data address. However, there is no other relocation before .text or near it. I'll send you the full debug printout, maybe you'll note something. The problem could be result of something else entirely else than the linker such as some library initialization code that by chance worked with smaller code but fails now. I need to debug and see

...ahW{=nH zgJXwQKSq2?KWWWrcQm?t_E1&VvVA!7Das5NPtS;3v3)n>UFnAOM}o`!Toz&`L>Hj3 ztWV-+KF|;i(6 at l(^F_p8=Lo!xnjMOowZz!xoqbwdb-sSohf!-}kVY;Ot;bBWzJ(@H zk|8U8j58;#fSGQDW$N_dJOa+HNjbzL;QAC_IQgJXU2&(L+j$&c=U7^T`pAd*Py-V* zJ$A2s39UwoKe8J6VPpjy802_3;&|DfQ)eLtkmDL;HGHAf at Lz{Geh6~>MacP~3AAWJ zj^B+8TVfycE}Y{bbBbl3MW#n1a&Ch3hjaWohm)X<T<0WcUoU`y#&&ze1SeZwx5e_R zU~W9k2aCUf$_epB%oP7%-)pyzd4Oah8`{XLU>sju);aF+B%+(1xY`b--bKZ4j`?~a z#q_g~=~H31?_O7MG_EfOeBL!5Oftleu7KTso(;QwGQ){ImmkTW-h1mh6kF&B%!A#A zj^>ZHfzKZ}T0W7Fm=^JgJV_<t6S=t;pUBA3>bZGT;*4!a@<-N}3~An...

Hi, We switched from compiling LLVM with gcc to clang (3.3) and it appears that clang (correctly I think) optimizes away the GDBRegistrar's __jit_debug_register_code() function that's used to trigger reading debug info from JIT-ted code, breaking GDB support. This patch forces it to leave the call using the method described here in the 'noinline' section:

I need help to get extlinux to work. I am tiring to boot /dev/hda1 with a ext2 file system. I am using extlinux 3.08 and installed it in the /boot directory with "/sbin/extlinux /boot" and set up the mbr with "cat mbr.bin > /dev/hda". The installer reported "/boot device is /dev/hda1". On booting extlinux.sys runs and displays "EXTLINUX 3.08 2005-05-19"

I need help to get extlinux to work. I am tiring to boot /dev/hda1 with a ext2 file system. I am using extlinux 3.08 and installed it in the /boot directory with "/sbin/extlinux /boot" and set up the mbr with "cat mbr.bin > /dev/hda". The installer reported "/boot device is /dev/hda1". On booting extlinux.sys runs and displays "EXTLINUX 3.08 2005-05-19"

Since the largest regional ILEC in Brazil completely stopped taking new BRI ISDN customers and started heavily incentiving their existing customers to migrate over to ADSL (regardless if what they need is voice or data), we have thousands of ISDN phones collecting dust. Is there any network side U cards that will work with Asterisk, so we can turn those phones into useful things ? I'm