search for: notrap

...of information ? We need to think about what happens when we merge >>> or >>> hoist load/stores. Will we need to review and change every single >>> memory >>> optimization in the compiler ? >> >> The original idea was that if the function is marked notrap, it only >> loosens the previous restrictions for the optimizations. Thus, if the >> old code still assumes trapping semantics, it should be still safe >> (only >> worse optimizations might result). >> >> Anyways, this has at least one problem that I see: functi...

...order to support this new > piece > of information ? We need to think about what happens when we merge > or > hoist load/stores. Will we need to review and change every single > memory > optimization in the compiler ? > > The original idea was that if the function is marked notrap, it only > loosens the previous restrictions for the optimizations. Thus, if the > old code still assumes trapping semantics, it should be still safe > (only > worse optimizations might result). > > Anyways, this has at least one problem that I see: functions that > have >...

...gt; piece > > of information ? We need to think about what happens when we merge > > or > > hoist load/stores. Will we need to review and change every single > > memory > > optimization in the compiler ? > > The original idea was that if the function is marked notrap, it only > loosens the previous restrictions for the optimizations. Thus, if the > old code still assumes trapping semantics, it should be still safe > (only > worse optimizations might result). > > Anyways, this has at least one problem that I see: functions that > have >...

On Tue, 12 Sep 2017 14:41:42 -0300 Flávio Silveira via samba <samba at lists.samba.org> wrote: > > Ok, I understand now, one question though: if realm is > AD.TECNOPON.COM.BR, does domain need to be AD? No, you can use anything you like, provided it is one word, 15 characters or less, without punctuation. > If I understand > correctly, realm is "full domain with

...need to be changed in order to support this new piece > of information ? We need to think about what happens when we merge or > hoist load/stores. Will we need to review and change every single memory > optimization in the compiler ? The original idea was that if the function is marked notrap, it only loosens the previous restrictions for the optimizations. Thus, if the old code still assumes trapping semantics, it should be still safe (only worse optimizations might result). Anyways, this has at least one problem that I see: functions that have the notrap attribute cannot be safely in...

..." applies to both servers and clients, so a configuration # that might be intended to block requests from certain clients could also end # up blocking replies from your own upstream servers. # By default, exchange time with everybody, but don't allow configuration. restrict -4 default kod notrap nomodify nopeer noquery restrict -6 default kod notrap nomodify nopeer noquery # Local users may interrogate the ntp server more closely. restrict 127.0.0.1 restrict ::1 # Clients from this (example!) subnet have unlimited access, but only if # cryptographically authenticated. #restrict 192.168.1...

...?? iburst prefer server 2.pool.ntp.org???? iburst prefer driftfile?????? /var/lib/ntpsec/ntp.drift logfile???????? /var/log/ntp.log #logconfig =all ntpsigndsocket? /var/lib/samba/ntp_signd/ # Access control # Default restriction: Allow clients only to query the time #restrict default kod nomodify notrap nopeer limited mssntp restrict -4 default kod limited nomodify notrap nopeer noquery mssntp # No restrictions for "localhost" restrict 127.0.0.1 # Enable the time sources to only provide time to this host restrict 0.pool.ntp.org?? mask 255.255.255.255??? nomodify notrap nopeer noquery re...

...t; cat << EOF >> /etc/ntp.conf > # > ###### Needed for Samba 4 ####### in the restrict -4 or -6 added mssntp at the end > # Location of the samba ntp_signed directory > ntpsigndsocket /var/lib/samba/ntp_signd > # > EOF > > sed -i 's/restrict -4 default kod notrap nomodify nopeer noquery limited/restrict -4 default kod notrap nomodify nopeer noquery limited mssntp/g' /etc/ntp.conf > sed -i 's/restrict -6 default kod notrap nomodify nopeer noquery limited/restrict -6 default kod notrap nomodify nopeer noquery limited mssntp/g' /etc/ntp.conf &gt...

...e: >> >> >> >> NEW PROPOSAL >> >> The solution is to introduce meta-data that is explicit about how the >> safe-to-execute condition ought to be evaluated. Instead of an SSA >> use, we can have meta-data that says: >> >> %v = load %p !notrap !{ @f, <args> } >> >> where @f is a function in the current module and this function >> returns i1, and <args> is zero or more arguments to pass to @f. As >> with any meta-data, this doesn’t imply anything different if you >> wanted to just execute the cod...

...een discussing this in a > slightly-different context, and briefly, this means adding all of > the relevant conditional branch inputs to the metadata, and ensuring > dominance before the metadata is respected. For example: > > if (i1 %c = call z_is_never_zero()) { > %x = %y / %z !notrap !{ %c } > ... > } > > and so if we run across this situation: > > %x = %y / %z !notrap !{ %c } > if (i1 %c = call z_is_never_zero()) { > ... > } > > we can test that the %c does not dominate %x, and so the metadata > needs to be ignored. The complication here...

...nge the fp > computation mode to the non-trapping one before calling such > a function (this is actually stated in the OpenCL specs). If such > handling is not supported by the target, then the attribute should not > be added the first place. > > The attribute could be called 'notrap' which would include the > semantics of any trap caused by any instruction. Or that could be > split, just in case the hardware is known not to support one of the > features. Three could suffice: 'nofptrap' (no IEEE FP exceptions), > 'nodivtrap' (no divide by zero e...

| My DC is a samba4.3 over Ubuntu 16.04. | I've configured ntp in the same server. | However > when I join a windows 10 client to my domain, this one doesn't | update its datetime. | Once I logging in, I am able to set any datetime. | And more > No matter the windows 10 client' s datetime, I can logging in with | any user of the Active Directory. | I need a proper time sync in

...i # add the folder location to ntp.conf cat << EOF >> /etc/ntp.conf # ###### Needed for Samba 4 ####### in the restrict -4 or -6 added mssntp at the end # Location of the samba ntp_signed directory ntpsigndsocket /var/lib/samba/ntp_signd # EOF sed -i 's/restrict -4 default kod notrap nomodify nopeer noquery limited/restrict -4 default kod notrap nomodify nopeer noquery limited mssntp/g' /etc/ntp.conf sed -i 's/restrict -6 default kod notrap nomodify nopeer noquery limited/restrict -6 default kod notrap nomodify nopeer noquery limited mssntp/g' /etc/ntp.conf systemct...

...nd I have been discussing this in a slightly-different context, and briefly, this means adding all of the relevant conditional branch inputs to the metadata, and ensuring dominance before the metadata is respected. For example: > > if (i1 %c = call z_is_never_zero()) { > %x = %y / %z !notrap !{ %c } > ... > } > > and so if we run across this situation: > > %x = %y / %z !notrap !{ %c } > if (i1 %c = call z_is_never_zero()) { > ... > } > > we can test that the %c does not dominate %x, and so the metadata needs to be ignored. The complicatio...

...urst prefer > > driftfile?????? /var/lib/ntpsec/ntp.drift > logfile???????? /var/log/ntp.log > #logconfig =all > ntpsigndsocket? /var/lib/samba/ntp_signd/ > > # Access control > # Default restriction: Allow clients only to query the time > #restrict default kod nomodify notrap nopeer limited mssntp > restrict -4 default kod limited nomodify notrap nopeer noquery mssntp > # No restrictions for "localhost" > restrict 127.0.0.1 > # Enable the time sources to only provide time to this host > restrict 0.pool.ntp.org?? mask 255.255.255.255??? nomodify...

...urst prefer > > driftfile?????? /var/lib/ntpsec/ntp.drift > logfile???????? /var/log/ntp.log > #logconfig =all > ntpsigndsocket? /var/lib/samba/ntp_signd/ > > # Access control > # Default restriction: Allow clients only to query the time > #restrict default kod nomodify notrap nopeer limited mssntp > restrict -4 default kod limited nomodify notrap nopeer noquery mssntp > # No restrictions for "localhost" > restrict 127.0.0.1 > # Enable the time sources to only provide time to this host > restrict 0.pool.ntp.org?? mask 255.255.255.255??? nomodify...

...??? /var/lib/ntpsec/ntp.drift > > logfile???????? /var/log/ntp.log > > #logconfig =all > > ntpsigndsocket? /var/lib/samba/ntp_signd/ > > > > # Access control > > # Default restriction: Allow clients only to query the time > > #restrict default kod nomodify notrap nopeer limited mssntp > > restrict -4 default kod limited nomodify notrap nopeer noquery mssntp > > # No restrictions for "localhost" > > restrict 127.0.0.1 > > # Enable the time sources to only provide time to this host > > restrict 0.pool.ntp.org?? mask 255...

...ey do. The runtime should change the fp computation mode to the non-trapping one before calling such a function (this is actually stated in the OpenCL specs). If such handling is not supported by the target, then the attribute should not be added the first place. The attribute could be called 'notrap' which would include the semantics of any trap caused by any instruction. Or that could be split, just in case the hardware is known not to support one of the features. Three could suffice: 'nofptrap' (no IEEE FP exceptions), 'nodivtrap' (no divide by zero exceptions, undef val...

On 11/01/2013 01:48 PM, Hal Finkel wrote: > The large complication that you end up with a scheme like this is > maintaining control dependencies. [...] Good point. > 2. Assert that !notrap cannot be used where its validity might be affected > by control dependencies. Thus, I propose that if this ends up being per-instruction property, its semantics would include this restriction. > 3. Represent the control dependencies explicitly in the metadata. [...] This could work but mi...

Hi! Previously in the "Add a 'notrap' function attribute?” thread we had discussed a way to use meta-data to specify that a load does not trap under certain conditions. Andy and Hal and I talked about this more in private and I just wanted to summarize what I think we arrived at. First I’ll summarize the original !notrap meta-da...