search for: nameptr

Just spoke to Jerry, we'll be doing a 3.0.27a on Monday to fix a regression that broke smbfs mounts from Linux. Sorry for the problem. Jeremy.

...gt; > Why? AFAIK the "function name" is just an arbitrary string. Using s or > MD5(s) shouldn't matter. Of course, the user will need to pass consistent > flags to clang. The raw format for 64bit target can be made 'unchanged', but not for the 32bit raw format -- the nameptr field is only 32bit. The indexed format can not be made the same -- The ondisk profile record layout totally changes. The key field changes from a blob of chars into an 64bit integer. > > >> >> It will be >> very messy to support multiple formats in instr-codegen and >&...

My systems: rh61, 2.2.14 + smbfs-nls.patch. I refer to 2.0.7pre3 as 2.0.7 === 1) "ls" of an empty dir 1a) 1.9.18 doing "ls" to an empty samba dir: smb: \> ls 49550 blocks of size 16384. 33754 blocks available 1b) 2.0.7 doing "ls" to an empty samba dir: smb: \> ls ERRDOS - ERRbadfile (File not found.) listing \* <=======

...an arbitrary string. Using s or >> > MD5(s) shouldn't matter. Of course, the user will need to pass >> > consistent >> > flags to clang. >> >> The raw format for 64bit target can be made 'unchanged', but not for >> the 32bit raw format -- the nameptr field is only 32bit. >> >> The indexed format can not be made the same -- The ondisk profile >> record layout totally changes. The key field changes from a blob of >> chars into an 64bit integer. > > > An MD5 sum cannot be represented as a blob of chars? yes -- it...

> > I think it is reasonable to simply replace the key we currently use with > MD5(key) for getting a size reduction. In practice for my use cases, I have > not observed any of the issues you mentioned under "Large size of overhead > can limit the usability of PGO greatly", but I can understand that some of > these issues could become problems in Google's use case.

...MD5(s) shouldn't matter. Of course, the user will need to pass >> >> > consistent >> >> > flags to clang. >> >> >> >> The raw format for 64bit target can be made 'unchanged', but not for >> >> the 32bit raw format -- the nameptr field is only 32bit. >> >> >> >> The indexed format can not be made the same -- The ondisk profile >> >> record layout totally changes. The key field changes from a blob of >> >> chars into an 64bit integer. >> > >> > >> >...

...ntificationDesc->Path); XenBusInterface.Read = XenBus_Read; XenBusInterface.Write = XenBus_Write; XenBusInterface.Printf = XenBus_Printf; @@ -765,7 +756,6 @@ XenPCI_XenBusWatchHandler(char *Path, PV XENPCI_IDENTIFICATION_DESCRIPTION description; NTSTATUS status; int i; - char *NamePtr; char **Bits; int Count; WDFCHILDLIST ChildList; @@ -773,8 +763,9 @@ XenPCI_XenBusWatchHandler(char *Path, PV WDFDEVICE ChildDevice; PXENPCI_XEN_DEVICE_DATA ChildDeviceData; - ANSI_STRING AnsiBuf; + + UNREFERENCED_PARAMETER(Data); KdPrint((__DRIVER_NAME " --> HotPlug...