similar to: NamedRegionTimer - printing structured data, full nanosecond resolution values

On Monday 22 September 2014 13:48:38 Richard W.M. Jones wrote: > The existing APIs guestfs_stat, guestfs_lstat and guestfs_lstatlist > return a stat structure that contains atime, mtime and ctime fields > that store only the timestamp in seconds. > > Modern filesystems can store timestamps down to nanosecond > granularity, and the ordinary glibc stat(2) wrapper will return these

https://bugzilla.samba.org/show_bug.cgi?id=12742 Bug ID: 12742 Summary: a proposal: fix bogus nanosecond mtimes on transfer (patch included) Product: rsync Version: 3.1.1 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 Component: core

The existing APIs guestfs_stat, guestfs_lstat and guestfs_lstatlist return a stat structure that contains atime, mtime and ctime fields that store only the timestamp in seconds. Modern filesystems can store timestamps down to nanosecond granularity, and the ordinary glibc stat(2) wrapper will return these in "hidden" stat fields: struct timespec st_atim; /* Time of last

I'm pondering a new timing feature for TableGen and am wondering whether anyone uses the existing -time-regions option. Some instrumentation for it appears in CodeGenTarget.cpp and GICombinerEmitter.cpp but nowhere else. If no one is using it, I'll be tempted to remove it.

I slightly modified the Kaleidoscope example to print the timing data using the NamedRegionTimer as below: // Run the main "interpreter loop" now. { const char *GroupName = "MainLoop"; NamedRegionTimer T("Kaleidoscope", GroupName, true); MainLoop(); } My assumption was that when T goes out of scope, it will emit the data on the command line. But I see

Signed-off-by: Alex Nelson <ajnelson at cs.ucsc.edu> --- xml/hivexml.c | 20 +++++++++++++++++--- 1 files changed, 17 insertions(+), 3 deletions(-) diff --git a/xml/hivexml.c b/xml/hivexml.c index 5030c24..98b90c5 100644 --- a/xml/hivexml.c +++ b/xml/hivexml.c @@ -185,6 +185,8 @@ filetime_to_8601 (int64_t windows_ticks) char *ret; time_t t; struct tm *tm; + int64_t sub_seconds;

Apple File System Guide is released. https://developer.apple.com/library/prerelease/content/documentation/FileManagement/Conceptual/APFS_Guide/GeneralCharacteristics/GeneralCharacteristics.html >Nanosecond Timestamp Granularity > >APFS supports 1 nanosecond timestamp granularity, which improves >upon the 1 second timestamp granularity of HFS+. >Compatibility > >You can share

On Thu, Dec 25, 2014 at 2:48 AM, Ingo Brückl <ib at wupperonline.de> wrote: > On systems using nanoseconds differences should be taken into > consideration. > The problem is that if you transfer from a filesystem that has nanoseconds to one that does not support it, rsync would consider most of the files to be constantly different, since the nanosecond values would only match if

On systems using nanoseconds differences should be taken into consideration. --- a/generator.c 2014-06-14 01:05:08.000000000 +0200 +++ b/generator.c 2014-12-25 11:19:54.000000000 +0100 @@ -588,7 +588,13 @@ if (ignore_times) return 0; - return cmp_time(st->st_mtime, file->modtime) == 0; + return cmp_time(st->st_mtime, file->modtime) == 0 +#ifdef ST_MTIME_NSEC + ?

ping. On Mon, May 9, 2011 at 10:20 PM, Sanjiv <llvmdev at gmail.com> wrote: > I slightly modified the Kaleidoscope example to print the timing data using > the NamedRegionTimer as below: > > // Run the main "interpreter loop" now. > { > const char *GroupName = "MainLoop"; > NamedRegionTimer T("Kaleidoscope", GroupName, true); >

Windows-32 has a time structure called FILETIME, a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC). That is not a typo, the year is 1601. Does anyone have a clue(or algorhithm)for how this is converted to something a little more POSIX-like ? Thank you, Derek -- Derek N. Eder Gothenburg University VINKLA - Vigilance and Neurocognition

Hello llvm-dev, I'm working on some out-of-process reflection support for Swift and I'd like to switch over some of my memory management to context-based with a bump-pointer allocator. I hit a linker error that `grow_pod` was missing. Eventually, some of this code will get linked into the Swift runtime and we are trying to avoid directly linking LLVM into the runtime to keep the size

Can anyone comment on the easiest way to get the PPS Kit kernel patch to work on a CentOS-5 system? I'd rather not use a plain vanilla kernel. http://www.kernel.org/pub/linux/daemons/ntp/PPS/

On Aug 10, 2018, at 1:28 PM, Marshall Clow via cfe-dev <cfe-dev at lists.llvm.org> wrote: > > * The clock stuff being added in C++20 has already been discussed here. I’ve missed the discussions on file_time_type, however I thought I should throw in my opinion here before it is too late to do anything about it. I believe it is a mistake to model file_time_type with 128 bits. It

> On Jun 29, 2013, at 9:53 PM, Eli Friedman <eli.friedman at gmail.com> wrote: > >> On Sat, Jun 29, 2013 at 7:51 PM, David Farler <accumulator at icloud.com> wrote: >> Hi all, >> >> In getting to know the LLVM infrastructure, I'm having a hard time finding implementation details for closures and continuations. >> >> For closures,

figured out how to use ldapsearch also to get what I want. Also found how to convert AD time to unix time Another thing I wanted calculated was when an account expires. ldapsearch -h ad.mydomain.tld -b dc=ad,dc=mydomain,dc=tld "(sAMAccountName=$user)" gives all the good information about a user. here is how I used it to tell me all accounts expiring this next month. h=ad.mydomain.tld

On Aug 10, 2018, at 9:35 PM, Eric Fiselier <eric at efcs.ca> wrote: > > Part of me is still concerned with the future, and the filesystems which are yet to exist. > Me too. But it is best to target modern systems when targeting future systems adds an unnecessary cost. When future systems come into being, it is likely because future hardware is making those future systems

http://libvirt.org/html/libvirt-libvirt.html#virDomainInfo http://libvirt.org/html/libvirt-libvirt.html#virVcpuInfo Both virDomainInfo and virVcpuInfo have a nanosecond cpuTime field. How do the two related to one another? With some experiementing, it appears the virDomainInfo::cpuTime is equal to the host CPU time used by the qemu-kvm process for the domain. It also appears that the

Hi. I'm trying to get digits form the user via agi something like this: this only should print result=asciicode but none of the functions even wait until timeout .. they just pass .. (after a nanosecond) the las print is always timeout. Any clue ..? my $callerid = $AGI{'callerid'} ; if($callerid !~ /[0-9]{7,20}/){ #way numbre one print "EXEC PLAYBACK

https://bugzilla.samba.org/show_bug.cgi?id=6672 Summary: mtim.tv_nsec not used when reading time of a file Product: rsync Version: 3.0.6 Platform: Other OS/Version: All Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: antonio at