search for: scrutiny

...lly "playful" EuroLLVM presentation (*) I think it would be time to get serious about merging to ToT. But we should probably find out whether an optimized algorithm is desired at all. So I'd solicit comments from the code owners (Use.{h,cpp}) and anybody who is interested. For closer scrutiny, the code is here: <http://llvm.org/viewvc/llvm-project/llvm/branches/ggreif/waymark-64-new/> I do not have the equipment to perform a compile-time measurement. How do folks benchmark for this nowadays? Is it a viable alternative to bring the changes to ToT and compare speedups/slowdowns in...

...nt to customize main().) - I updated the LICENSE.txt and mkpatch, but I haven't done the HTML docs yet because I am still thinking about what to write. - I probably made some mistakes in setting up the makefile rules - that is what took the most time - so it will merit heightened scrutiny. -- -- Talin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20081230/7dd86e49/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: unittest.patch Type: appl...

Oh yes, also I added a shortcut for code blocks. Instead of <pre><code>, you can surround it with three backticks (```). - Lucas http://rufy.com/

...as been reported in this Syslinux Mailing List several times already, and there is also a bug report for it http://bugzilla.syslinux.org/show_bug.cgi?id=10 . FWIW, version 5.xx has many other problems, part of them resolved in 6.03 (but the lss16 issue is not yet resolved). I hope your initial scrutiny of the source code can bring up an actual solution / patches for both, Syslinux CLI and menu parsers (and if possible for both, BIOS and UEFI). Any developers willing to look at this issue and actually solve it? TIA, Ady.

...before the OOM notifier is invoked, and it seems like the shrinker API might allow more fine grained control of when we deflate. On the other hand, I'm not totally convinced that Wei's patch is an expected use of the shrinker/page-cache APIs, and maybe it is fragile. Needs more testing and scrutiny. It seems to me like the shrinker API is the right API in the long run, perhaps with some fixes and modifications. But maybe reverting to OOM notifier is the best patch to back port? On Fri, Feb 14, 2020 at 6:19 AM David Hildenbrand <david at redhat.com> wrote: > >> There was a re...

...de? Is there a reason? Is it because there are problems with the HPH-SSH code? Since the code has been out for a time and still has not been incorporated to the OpenSSH code. It creates doubt of there must be a reason why the OpenSSH group has not incorporated the patch. There are concerns of code scrutiny and review if it is not incorporated. OpenSSH has now become not just an application but a medium for data transfer and that means network performance is very critical. If network performance can be increased without decrease in security then it would make OpenSSH even more attractive. So the ques...

...g us all. It will help individuals create new projects more easily and efficiently. Are the diff files readily available, can I download them from anywhere? If the diff files were made available with each update, the community would understand more, less questions and confusion would occur. More scrutiny would result in a better product for us all. RHEL takes open source software and closes it. CentOS takes this closed software and reopens it. By making the changes open to public inspection, CentOS would become 100% open source. I have no wish to waste months of effort duplicating your work, even...

Hi, the display of LSS16 files from a DISPLAY file (as documented in http://www.syslinux.org/wiki/index.php/SYSLINUX#Display_graphic_from_filename:) seems heavily broken since syslinux has been converted from assembler to C. I already discovered one bug in core/include/graphics.h (and core/graphics.c): the pointer VGAFilePtr is of type uint16_t*, but should be plain char*. This bug causes the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm wondering if/where I can get the server side component for freebsd-update. Presumably such a component would build and sign the binary patches and prepare them to be served via HTTP to the freebsd-update client. I need a system for distributing binary updates to a collection of customized FreeBSD machines, jails, and embedded systems.

...trengthReduce. A former colleague created this pass back in LLVM 2.9 and we've been using it ever since. I've done some light refactoring and modernization. This pass broke 4 existing tests that were sensitive to generated code. I've corrected all these, but please give them special scrutiny. The patch is available here: http://reviews.llvm.org/D12494 Please advise. Regards, -steve

...o test my CATENATE implementation a few years ago and it runs fine against dovecot in OS X Server. When run against dovecot-2.2.4 though it always fails or hangs, which in some cases means we interpreted RFCs differently and in other cases means it's finding bugs; both conditions are worthy of scrutiny. (It's random-number driven so every run is different.) A couple months ago I reported a few simple bugs which this script found and you fixed them; thanks. Then it started finding problems for which it's harder to isolate simple reproducible test cases. Vacations and other work interce...

...n restart it quickly by giving the same session ID as before, as long as the daemon maintains a session cache. 4. The code might end up being simpler (just calling the OpenSSL library). Or it might not. I haven't looked into it yet :-) 5. TLS and OpenSSL have both been subjected to widespread scrutiny. Even though the initial setup of a TLS connection might have a higher overhead than tinc's TCP protocol, once it's established I don't expect it's much higher, and in any case isn't the volume of metadata exchanged relatively low? Just a thought anyway... Regards, Brian. [...

...ain().) > - I updated the LICENSE.txt and mkpatch, but I haven't done the HTML > docs yet because I am still thinking about what to write. > - I probably made some mistakes in setting up the makefile rules - that > is what took the most time - so it will merit heightened scrutiny. > > +++ unittests/Makefile.unittest (revision 0) [...] +VPATH=$(PROJ_SRC_DIR) $(PROJ_SRC_ROOT)/unittests That doesn't look like a valid path to me. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments...

...0, Daniel Vetter wrote: > On Fri, Feb 24, 2017 at 08:19:45PM +0100, Lukas Wunner wrote: > > Fix Thunderbolt-related issues in apple-gmux and vga_switcheroo: > > > > Patch [1/5] ("Recognize Thunderbolt devices") has already been subjected > > to a fair amount of scrutiny over at linux-pci@, I've submitted it 5 times > > total since May 2016. With luck it may be in ack-able shape now. > > > > Patch [2/5] amends apple-gmux to handle combined DP/Thunderbolt ports > > properly on newer MacBook Pros. > > > > Patches [3/5] to [5...

...cot -c /etc/dovecot/dovecot.conf dovecot 16245 16243 0 13:42 ? 00:00:00 dovecot/anvil root 16246 16243 0 13:42 ? 00:00:00 dovecot/log root 16248 16243 0 13:42 ? 00:00:00 dovecot/config Still no listener :( $ sudo netstat -tlnp | grep -c 993 0 Other infos for your scrutiny. $ sudo dovecot --version 2.0.18 $ doveconf -n # 2.0.18: /etc/dovecot/dovecot.conf # OS: Linux 3.2.5-grsec x86_64 Debian wheezy/sid ext4 auth_debug = yes auth_mechanisms = plain login auth_verbose = yes first_valid_uid = 1000 log_timestamp = "%Y-%m-%d %H:%M:%S " mail_debug = yes mail_lo...

...epending on the context: For all GlobalObjects: 1. Pass GlobalObject to target-independent TargetLoweringObjectFile::isGlobalInSmallSection. If it's a declaration, make a virtual call to a new method named TargetLoweringObjectFile::isGlobalInSmallSectionKind (doing target-specific scrutiny) and return the result early. 2. Pass to TargetLoweringObjectFile::getKindForGlobal. If the Kind is Data, BSS or Common, make a virtual call to TargetLoweringObjectFile::isGlobalInSmallSectionKind just before returning the SectionKind. If true is returned, set the 'isSmallKind'...

...015 at 6:32 PM, Warren Young <wyml at etr-usa.com> wrote: > On Jul 28, 2015, at 4:37 PM, Nathan Duehr <denverpilot at me.com> wrote: >> Equating this to ?vaccination? is a huge stretch. > > Why? It's not just an imperfect analogy it really doesn't work on closer scrutiny. Malware itself is not a good analog to antigens. Vaccinations provide immunity to only certain kinds of antigens, and only specific ones at that. Challenge-Response, which is what a login password is, is about user authentication it is not at all meant or designed to provide immunity from malware...

...n R releases only happening yearly in spring, now is good time to consider *and* discuss new features for what we often call "R-devel" and more officially is R Under development (unstable) (.....) -- "Unsuffered Consequences" Here is one such example I hereby expose to public scrutiny: A few minutes ago, I've committed the following to R-devel (the 'trunk' in the svn repository for R): ------------------------------------------------------------------------ r62834 | maechler | 2013-05-30 10:01:33 +0200 (Thu, 30 May 2013) | 1 line Changed paths: M doc/NEWS.Rd...

I just saw a mention here of LoginEngine, which I hadn''t heard of before. Last week when I was digging for user-account sample code for my web-app, I instead found the LoginGenerator and started using that: http://wiki.rubyonrails.com/rails/pages/LoginGenerator Is one of these preferred over the other? From skimming the API docs, it does seem that LoginEngine has more features,

...n top of post-quantum crypto lately, but isn't that still years away? X448, on the other hand, is fully defined and was recently put into TLS 1.3. It wouldn't be hard to convince me that X448 is still a little too new; perhaps we could wait a year and see how well it does with the new scrutiny it gets from being in the TLS spec. If it survives its field-testing, then we could move forward. And/or we make X448 a last-priority KEX for a year or two and patiently see what happens. Again, if this gets the green light, I'll be happy to write the initial implementation. Thanks,...