search for: 20200219

..._____________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200219/5e3da1c0/attachment.html>

..., so use a -1 for checking a true // 1-bit value. Which seems to reflect the same observation. Is this a bug or a feature? Thanks in advance for any explanation -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200219/3c2aeca5/attachment.html>

On Wed, Feb 19, 2020 at 3:51 AM Juneyoung Lee via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I think not_poison (Johannes's used keyword) makes sense. We can simulate the original UB semantics by simply attaching it, as explained. > For the attributes other than nonnull, we may need more discussion; align attribute seems to be okay with defining it as poison, dereferenceable

...; LLVM Developers mailing list >>> llvm-dev at lists.llvm.org >>> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200219/e944b84d/attachment.html>

...in > the list of users from doveadm. > > What can I do to tell doveadm to forget about "nobody"? > > Thanks. > > Philip > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20200219/7e37f8b0/attachment.html>

On Tue, Feb 18, 2020 at 2:55 AM David Chisnall via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi Tanya, > > On 18/02/2020 00:56, Tanya Lattner wrote: > > I understand not everyone wants to use Google docs which was why I gave > an option to reply via email as well. My intention on using Google docs is > really just based on my experience using it for docs that span

...lipboard. It is unaccounted for because it is doing the accounting for the rest of it. Nine-tenths of the universe, in fact, is the paperwork. --The Thief of Time -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20200219/d9458361/attachment-0001.html>

...Argonne National Laboratory Lemont, IL 60439, USA jdoerfert at anl.gov -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200219/bed194ee/attachment.sig>

Hi LLVM community, I am trying to differentiate access to different array elements, for example: for (int i = 1; i < 10; i++) { a[i] = a[i] + 10; b[i] = a[i - 1] * 2; } If it is possible to tell it loads/stores 3 different array elements: a[i], b[i] and a[i - 1] at IR level? Thanks for your time in advance! Best, Michael -------------- next part -------------- An HTML

We're using dovecot on a help desk ticketing system. The system doesn't perform any cleanup of IMAP mailboxes so we have a regular cronjob doing this: /usr/bin/doveadm flags add -A '\Deleted' SEEN SENTBEFORE 12w && /usr/bin/doveadm expunge -A DELETED MAILBOX '*' Recently, doveadm has been reporting this: doveadm(nobody): Error: User initialization failed:

My Junk mailbox is still filling up with hard linked emails. There are some junk mails with over 3000 hard linked files and over half a million files in the .Junk/cur folder. I had a handy script to remove them all by doing a find for inodes and sorting the list by age and keeping the olds hard link and removing all the others, but I now can?t find it :/ so I have just taken to periodically

...and registration can be found here: https://www.eventbrite.com/e/eurollvm-2020-diversity-inclusion-workshop-tickets-94343837959 Hope to see you there ! -- Arnaud -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200219/6394d3e2/attachment.html>

We recently found an issue when using the full restrict implementation developed by Jeroen; it surfaces when compiling an obscure combination of std::valarray and std::indirect_array but I don't want to bore you with all the details. What it boils down to is this basic question about restrict: Given one restrict pointer based on another, should they never alias? As far as I understand the

Hello everyone, Release Candidate 2 was tagged earlier today as llvmorg-10.0.0-rc2. It includes 98 commits since the previous release candidate. Source code and docs are available at https://prereleases.llvm.org/10.0.0/#rc2 and https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0-rc2 Pre-built binaries will be added as they become available. Please file bug reports for any issues

Hi Philip, While it's true we don't I think Valentin is reasonable in saying "hey, when people do this let's try to combine them if it makes sense". It's just being polite to everyone, especially if it doesn't risk the patches or upstream stability. I don't think there's a policy change being proposed, just a "hey, let's see what we can do in the

Two patches are handling new edge cases introduced by doing DMA mappings (which can fail) in virtio core. I stumbled upon this while stress testing I/O for Protected Virtual Machines. I deliberately chose a tiny swiotlb size and have generated load with fio. With more than one virtio-blk disk in use I experienced hangs. The goal of this series is to fix those hangs. Halil Pasic (2):

Two patches are handling new edge cases introduced by doing DMA mappings (which can fail) in virtio core. I stumbled upon this while stress testing I/O for Protected Virtual Machines. I deliberately chose a tiny swiotlb size and have generated load with fio. With more than one virtio-blk disk in use I experienced hangs. The goal of this series is to fix those hangs. Halil Pasic (2):

...;r=ELyOnT0WepII6UnFk-OSzxlGOXXSfAvOLT6E8iPwwJk&m=xMDqkSAlj-YCOS4JMDXAENpBS-eaCcLYSkIm1qK68fs&s=B3LRzqpd9bD1724nvhG0FtpFh3QPsQ4FTBGQ4qJn1cA&e=> > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200219/14510c24/attachment.html>

...--Enjoy The Samba Team -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: not available URL: <http://lists.samba.org/pipermail/samba-announce/attachments/20200219/e04a9c76/signature.sig>

...--Enjoy The Samba Team -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: not available URL: <http://lists.samba.org/pipermail/samba-announce/attachments/20200219/e04a9c76/signature.sig>