search for: crowl

...er hand, a language with undefined behavior makes it possible for compilers (and their run-time support) to identify a program as wrong. The problem with the latest spate of compiler optimizations was not the optimization, but the lack of warnings about exploiting undefined behavior. -- Lawrence Crowl

On Sun, Feb 28, 2016 at 12:27 AM, Markus Trippelsdorf <markus at trippelsdorf.de> wrote: >> > >> > -fno-strict-overflow >> >> -fno-strict-aliasing. > > Do not forget -fno-delete-null-pointer-checks. > > So the kernel obviously is already using its own C dialect, that is > pretty far from standard C. > All these options also have a negative

Hi, I want to run rsync as a daemon program so that it can run at particular time in nights given by us any help greatly appreciated Thks in advance --Venkat

I have 2 drives in a Linux 7.1 server , 1 primary and 1 secondary. I am trying to clone to the secondary slave drive and be take the primary out and change the slave to primary and boot from it. The problem I am having is that it the copied drive will not boot, It is not getting the lilo boot and config properly. When I try to boot the copied drive , it boots to a Blank screen with an

[Moved to openssh port from openssh at openbsd.org for broader comments] On Wed, 18 Apr 2001, Mike Crowl wrote: > > To whom it may concern, > > I've been building openssh for various versions of solaris and noticed > that I'm having to jump through hoops to get it done because the build > process for openssh is pretty sloppy. Specifically there are several > option flags...

If carries_dependency affects semantics, then it should not be an attribute. The original design, or at least my understanding of it, was that it not have semantics; it was only a suggestion to the compiler that it should preserve dependencies instead of inserting a fence at the call site. Dependency-based ordering would be preserved in either case. But I think we're moving away from that

On Fri, Feb 19, 2016 at 09:15:16PM -0500, Tony V E wrote: > There's at least one easy answer in there: > > > ‎If implementations must support annotation, what form should that > annotation take?  P0190R0 recommends the [[carries_dependency]] > attribute, but I am not picky as long as it can be (1) applied > to all relevant pointer-like objects and (2) used in C as well