search for: ldebug

...rc/lcode.c | 404 +- com32/lua/src/lcode.h | 21 +- com32/lua/src/lcorolib.c | 155 + com32/lua/src/lctype.c | 52 + com32/lua/src/lctype.h | 95 + com32/lua/src/ldblib.c | 214 +- com32/lua/src/ldebug.c | 620 ++- com32/lua/src/ldebug.h | 27 +- com32/lua/src/ldo.c | 661 +-- com32/lua/src/ldo.h | 33 +- com32/lua/src/ldump.c | 43 +- com32/lua/src/lfs.c | 294 ++ com32/lua/src/lfun...

I'm trying to figure out if there is a way to figure out what processor resource is used by which instruction during scheduling. This is purely for debugging purposes. Since I'm somewhat new to LLVM it is a bit difficult for me to figure this out. Initial idea was to insert comments in the generated assembly which would tell me what what resource is used. MachineInstr has a uint8_t

...404 +- > com32/lua/src/lcode.h | 21 +- > com32/lua/src/lcorolib.c | 155 + > com32/lua/src/lctype.c | 52 + > com32/lua/src/lctype.h | 95 + > com32/lua/src/ldblib.c | 214 +- > com32/lua/src/ldebug.c | 620 ++- > com32/lua/src/ldebug.h | 27 +- > com32/lua/src/ldo.c | 661 +-- > com32/lua/src/ldo.h | 33 +- > com32/lua/src/ldump.c | 43 +- > com32/lua/src/lfs.c | 2...

.../lcode.c | 404 +-- com32/lua/src/lcode.h | 21 +- com32/lua/src/lcorolib.c | 155 ++ com32/lua/src/lctype.c | 52 + com32/lua/src/lctype.h | 95 + com32/lua/src/ldblib.c | 214 +- com32/lua/src/ldebug.c | 625 +++-- com32/lua/src/ldebug.h | 27 +- com32/lua/src/ldo.c | 669 +++-- com32/lua/src/ldo.h | 33 +- com32/lua/src/ldump.c | 43 +- com32/lua/src/lfs.c | 296 +++ com32/lua/src...

...emote-host 10.3.1.201 option remote-subvolume brick end-volume volume mirror0 type cluster/afr subvolumes sirius00 sirius01 end-volume ??############################################################################# When I run the next command: $ glusterfs -l /var/log/glusterfs/gfscli.log -LDEBUG \ -f /etc/glusterfs/glusterfs-cli /mnt/glusterfs the log say me: --------- 2008-10-31 12:30:17 D [glusterfs.c:167:get_spec_fp] glusterfs: loading spec from /etc/glusterfs/glusterfs-client.vol 2008-10-31 12:30:17 D [spec.y:107:new_section] parser: New node for 'sirius00' 2008-10-31 12:30:1...

Hi, Unable to do peer probe... and unable to figure out whats the reason from the gluster log. can someone help ? 1) This is what i was trying... gluster> peer probe llm19.in.ibm.com Probe unsuccessful Probe returned with unknown errno 107 gluster> peer probe 9.124.111.25 Probe unsuccessful Probe returned with unknown errno 107 gluster> peer status Number of Peers: 1 Hostname:

Hi Stepan, Sorry for the delay. It's great that you are working on MergeFunctions as well and I agree, we should definitely try to combine our efforts to improve MergeFunctions. Just to give you some context, the pass (with the similar function merging patch) is already being used in a production setting. From my point of view, it would be better if we focus on improving its capability

...30838 0 0.01 30838 lauxlib.ll 43 110129 0 0.02 110114 0 0.02 110114 layer3.ll 13 435128 0 0.04 435097 0 0.04 435097 lbaselib.ll 43 99233 0 0.02 99218 0 0.02 99218 L_canny.ll 5 57717 0 0.02 57695 0 0.02 57695 lcode.ll 56 172913 0 0.02 172898 0 0.03 172898 ldblib.ll 24 83768 0 0.02 83753 0 0.02 83753 ldebug.ll 32 162976 0 0.02 162961 0 0.02 162961 ldecod.ll 14 149907 0 0.02 149886 0 0.02 149886 ldo.ll 24 152277 0 0.02 152262 0 0.02 152262 ldump.ll 11 32964 0 0.01 32949 0 0.01 32949 leaky_bucket.ll 5 54568 0 0.01 54547 0 0.01 54547 lemon.ll 112 1102968 0 0.10 1102951 0 0.11 1103447 lencod.ll 37 651236...

From: Matt Fleming <matt.fleming at linux.intel.com> This series fixes some bugs and switches the elflink branch to be entirely ELF modules. It applies on top of, http://syslinux.zytor.com/archives/2011-April/016369.html The deletions in the diff stat below are mainly from deleting com32/elflink/modules (finally!). Now there should be no duplicate code because we don't need COM32 and