search for: aph

Checking out LLVM from svn and building, I get: llvm[2]: Linking Release executable ModuleMaker (without symbols) /usr/bin/ld: error in /home/aph/llvm/Release/lib/LLVMX86.o(.eh_frame); no .eh_fr ame_hdr table will be created. /usr/bin/ld: error in /home/aph/llvm/Release/lib/LLVMInterpreter.o(.eh_frame); n o .eh_frame_hdr table will be created. /usr/bin/ld: error in /home/aph/llvm/Release/lib/LLVMExecutionEngine.o(.eh_frame ); no .eh_frame_hd...

Hi Andrew, > Checking out LLVM from svn and building, I get: > > llvm[2]: Linking Release executable ModuleMaker (without symbols) > /usr/bin/ld: error in /home/aph/llvm/Release/lib/LLVMX86.o(.eh_frame); no .eh_fr > ame_hdr table will be created. > /usr/bin/ld: error in /home/aph/llvm/Release/lib/LLVMInterpreter.o(.eh_frame); n > o .eh_frame_hdr table will be created. > /usr/bin/ld: error in /home/aph/llvm/Release/lib/LLVMExecutionEngine.o(.eh_fram...

Nick Lewycky wrote: > 2009/6/30 Andrew Haley <aph at redhat.com <mailto:aph at redhat.com>> > > Nick Lewycky wrote: > > I'm seeing this new build failure, starting some time yesterday on > ARM: > > Yes. It's just a matter of defining __sync_val_compare_and_swap_4: > > http://gcc.g...

2009/6/30 Andrew Haley <aph at redhat.com> > Nick Lewycky wrote: > > I'm seeing this new build failure, starting some time yesterday on ARM: > > > > make[3]: Entering directory `/home/nlewycky/llvm/tools/llvmc/driver' > > llvm[3]: Linking Debug executable llvmc > > g++ -DLLVMC_BUIL...

Andrew Haley <aph at redhat.com> writes: > Óscar Fuentes wrote: >> The following message is a courtesy copy of an article >> that has been posted to gmane.comp.compilers.llvm.devel as well. >> >> Andrew Haley <aph at redhat.com> writes: >> >>> This is x86_64. I...

Checking out LLVM from svn and building, I get: llvm[2]: Linking Release executable ModuleMaker (without symbols) /usr/bin/ld: error in /home/aph/llvm/Release/lib/LLVMX86.o(.eh_frame); no .eh_fr ame_hdr table will be created. /usr/bin/ld: error in /home/aph/llvm/Release/lib/LLVMInterpreter.o(.eh_frame); n o .eh_frame_hdr table will be created. /usr/bin/ld: error in /home/aph/llvm/Release/lib/LLVMExecutionEngine.o(.eh_frame ); no .eh_frame_hd...

Andrew Haley wrote: > Nick Lewycky wrote: >> 2009/6/30 Andrew Haley <aph at redhat.com <mailto:aph at redhat.com>> >> >> Nick Lewycky wrote: >> > I'm seeing this new build failure, starting some time yesterday on >> ARM: >> >> Yes. It's just a matter of defining __sync_val_compare_and_swap_4: >&...

This is x86_64. I have a problem where an absolute memory load define i32 @foo() { entry: %0 = load i32* inttoptr (i64 12704196 to i32*) ; <i32> [#uses=1] ret i32 %0 } generates incorrect code on LLVM 2.4: 0x7ffff6d54010: mov 0xc1d9c4(%rip),%eax # 0x7ffff79719da 0x7ffff6d54016: retq should be 0x7ffff6d54010: mov 0xc1d9c4, %eax 0x7ffff6d54016: retq

Óscar Fuentes wrote: > Andrew Haley <aph at redhat.com> writes: > >> Óscar Fuentes wrote: >>> The following message is a courtesy copy of an article >>> that has been posted to gmane.comp.compilers.llvm.devel as well. >>> >>> Andrew Haley <aph at redhat.com> writes: >>> >&...

Here's my problem, which I raised on IRC: JIT::getPointerToFunction gets the address of the start of a function. But how do I find out where the end of the function is? I need this to register the function for profiling. varth said: aph, you need to intercept the "endFunctionBody" call on the memory manager, it will tell you the start pointer and the end pointer But how can I do this? The obvious way would be for me to inherit from DefaultMemoryManager and pass an instance of my class to ExecutionEngine::createJIT. Bu...

...w_value); lib/System/Atomic.cpp: return __sync_add_and_fetch(ptr, 1); lib/System/Atomic.cpp: return __sync_sub_and_fetch(ptr, 1); lib/System/Atomic.cpp: return __sync_add_and_fetch(ptr, val); Cheers Xerxes Andrew Haley skrev: > Nick Lewycky wrote: > >> 2009/6/30 Andrew Haley <aph at redhat.com <mailto:aph at redhat.com>> >> >> Nick Lewycky wrote: >> > I'm seeing this new build failure, starting some time yesterday on >> ARM: >> >> Yes. It's just a matter of defining __sync_val_compare_and_swap_4: >&...

...priate type and alignment. The storage holds one object at a time, it's initialized (and for nontrivial types, destroyed) at the right times to ensure this. The cast is only to the type of object that's already there, there's no magic here. On Fri, Aug 10, 2018, 17:52 Andrew Haley <aph at redhat.com> wrote: > On 08/10/2018 05:30 AM, Liu Hao wrote: > > Only an lvalue of a pointer to (possibly CV-qualified) `void` or a > > pointer to a character type (in C) / any of `char`, `unsigned char` or > > `std::byte` (in C++) can alias objects. > > Yes. > &...

On 08/12/2018 02:19 PM, Kim Gräsman wrote: > I still feel a little uncomfortable, because I think Jonathan makes an > excellent point -- if GCC thinks there's a strict-aliasing violation > (whether the standard agrees or not) and classifies this as undefined > behavior, we might invoke the optimizers wrath. The warning is a nice > hint that this could happen. Indeed. And

...drew, Andrew Haley wrote: > Here's my problem, which I raised on IRC: > > JIT::getPointerToFunction gets the address of the start of a function. > But how do I find out where the end of the function is? I need this > to register the function for profiling. > > varth said: aph, you need to intercept the "endFunctionBody" call on > the memory manager, it will tell you the start pointer and the end > pointer > Yep, that's what I said :) > But how can I do this? The obvious way would be for me to inherit > from DefaultMemoryManager and pas...

Thanks Kevin! I¹m unclear how to read the ‹itemize-changes output. Can you provide some insight? This is a local transfer from an external drive to an internal drive all attached to one computer. rsync -aPh --itemize-changes -n /Volumes/shuttle_05/2012_79_1_14_1__1199_Workprint /Volumes/3TB_LTO/LT003A/ sending incremental file list >f..t....... >2012_79_1_14_1__1199_Workprint/2012_79_1_14_1__1199_Workprint__Derivatives >/2012_79_1_14_1_DER_01.mov >f..t....... >2012_79_1_14_1__1199_Wor...

Hi I was using rsync with the following options rsync -aPH --exclude-from=/var/tmp/ignorelist /home/me/ /run/media/me/ADATA\ #2/rsync-me/ and I was creating a copy of a home directory on my Linux machine. It went along for sometime (some 30,000 files) when it stopped with the following message. ---> Desktop/OSme/Web-Site-Backups/backup-5.4.2014_15-1...

...looking at the protocol and it is very very similar to www.networkupstols.org/ups-protocols/megatec.html at least protocol wise. but i have a few problems ==== problem 1 ==== using FOR is wrong as it then reports as a different device than it actually is. should i add a new device string, say APH? ==== problem 2 ==== i would like to use the usb protocol but i don't know where to start. lsusb Bus 003 Device 003: ID 0665:5161 Cypress Semiconductor USB to Serial dmesg [10684.669013] usb 3-2: new low speed USB device using uhci_hcd and address 3 [10684.833060] usb 3-2: New USB device fo...

...object at a time, it's initialized (and for nontrivial types, > > destroyed) at the right times to ensure this. The cast is only to the type > > of object that's already there, there's no magic here. > > > > > > On Fri, Aug 10, 2018, 17:52 Andrew Haley <aph at redhat.com> wrote: > >> > >> Not exactly. You can cast a pointer to a pointer to some character > >> type or the type of the object stored in memory. It does not matter > >> whether you use an intermediate type or not. Having not seen the test > >&...

On Tue, 14 Aug 2018 at 11:56, Kim Gräsman <kim.grasman at gmail.com> wrote: > > On Tue, Aug 14, 2018 at 11:51 AM Andrew Haley <aph at redhat.com> wrote: > > > > On 08/12/2018 02:19 PM, Kim Gräsman wrote: > > > I still feel a little uncomfortable, because I think Jonathan makes an > > > excellent point -- if GCC thinks there's a strict-aliasing violation > > > (whether the standard...

..._sync_add_and_fetch(ptr, 1); > lib/System/Atomic.cpp: return __sync_sub_and_fetch(ptr, 1); > lib/System/Atomic.cpp: return __sync_add_and_fetch(ptr, val); > > Cheers > Xerxes > > Andrew Haley skrev: >> Nick Lewycky wrote: >> >>> 2009/6/30 Andrew Haley <aph at redhat.com <mailto:aph at redhat.com>> >>> >>> Nick Lewycky wrote: >>>> I'm seeing this new build failure, starting some time yesterday on >>> ARM: >>> >>> Yes. It's just a matter of defining >>> __syn...