Displaying 16 results from an estimated 16 matches for "20200424".
2020 Apr 24
4
Make llvm-commits default cc on Phabricator
...Would it make sense to set 'LLVM Github Monorepo' as a default? Or subscribe 'llvm-commits' automatically when creating a patch?
Thanks!
Alex.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200424/1252adef/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 3097 bytes
Desc: image001.png
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200424/1252adef/attachment.png>
2020 Apr 24
4
VM migration problems
I have migrated KVM VMs from a CentOS 6 to a CentOS 7 host. All work fine post-migration, CentOS 3 (don't ask ...), CentOS 6, CentOS 7, Windows. But the CentOS 5 VMs failed. At some point during the boot process, they became unpingable and also inaccessible.
I have correlated this to the start of the irqbalance service and was wondering if it is generally considered best practice to turn it
2020 Apr 24
2
Pointer comparison folding
...ed. Is it a safe transformation to use that range and constant fold the icmps? Is so, is it still safe if the gep offset 'x' is unknown?
Regards,
Sam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200424/1aeacb6f/attachment-0001.html>
2020 Apr 24
0
VM migration problems
..._____________________________________
> CentOS-virt mailing list
> CentOS-virt at centos.org
> https://lists.centos.org/mailman/listinfo/centos-virt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20200424/5e7072f3/attachment-0005.html>
2020 Apr 24
0
VM migration problems
...as wondering if it is generally considered best practice to turn it off. The VMs in question all have at least 2 vcpus, and the C5 VMs are the odd ones out.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20200424/0dbc0e45/attachment-0005.html>
2020 Apr 24
0
Hierarchy separator recommendation?
...can i always change this namespace hierarchy separator later on?
>> This would cause similar caching problems on end user devices.
>>
>> Sami
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dovecot.org/pipermail/dovecot/attachments/20200424/2b69e81b/attachment-0001.html>
2020 Apr 24
2
Hierarchy separator recommendation?
The dot '.' will work, but I suggest to follow documentation here:
https://wiki1.dovecot.org/Namespaces,
And it says:
A commonly used separator is '/'. It probably causes the least amount of
trouble with different IMAP clients
And I already had problems using '.' as a namespace separator.
On 2020-04-24 15:56, Sami Ketola wrote:
>
>> On 24. Apr 2020, at
2015 Feb 18
6
[Bug 11101] New: support writing to devices
https://bugzilla.samba.org/show_bug.cgi?id=11101
Bug ID: 11101
Summary: support writing to devices
Product: rsync
Version: 3.0.6
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: core
Assignee: wayned at samba.org
Reporter: jpyeron at
2020 Apr 23
2
pad length mismatch error message
Hi Andrew,
> Thanks for reporting this. Firstly, don't worry about 'attr' packages
> or how Bind9 or DNS is configured etc, this is an error in our core RPC
> server, and not something that is able to be configured (neither at
> build nor runtime).
>
> A client, and we don't include enough information in the message as to
> which, so you will need to turn up
2020 Apr 23
4
[PATCH] virtio-blk: handle block_device_operations callbacks after hot unplug
A virtio_blk block device can still be referenced after hot unplug by
userspace processes that hold the file descriptor. In this case
virtblk_getgeo() can be invoked after virtblk_remove() was called. For
example, a program that has /dev/vdb open can call ioctl(HDIO_GETGEO)
after hot unplug.
Fix this by clearing vblk->disk->private_data and checking that the
virtio_blk driver instance is
2020 Apr 23
4
[PATCH] virtio-blk: handle block_device_operations callbacks after hot unplug
A virtio_blk block device can still be referenced after hot unplug by
userspace processes that hold the file descriptor. In this case
virtblk_getgeo() can be invoked after virtblk_remove() was called. For
example, a program that has /dev/vdb open can call ioctl(HDIO_GETGEO)
after hot unplug.
Fix this by clearing vblk->disk->private_data and checking that the
virtio_blk driver instance is
2020 Apr 24
5
RFC: Switching from Bugzilla to Github Issues [UPDATED]
On 04/24/2020 03:24 AM, Sam McCall wrote:
> clangd's experience using github issues to track bugs (in a separate repo) has been very positive, and I'm glad you're pushing on this!
>
> Part of this has been that our issue tracker has been scoped to our subproject only, which is a scope that the tool works well for (on the user and developer side).
> As such I don't
2020 Apr 23
3
[cfe-dev] More verbose -mspeculative-load-hardening
Another thing to consider about your feature idea is that the output may be
noisy depending on what you were hoping for.
SLH tries to mitigate anything that could potentially be a problem and thus
it instruments almost every branch, load, and function entry, for example.
There isn't a lot of signal about what is really a gadget among the code
instrumented by SLH. It really tries to be
2020 Apr 22
3
[cfe-dev] More verbose -mspeculative-load-hardening
Hi
I think llvm-dev list (CC'ed) have more visibility in this.
On Wed, 22 Apr 2020 at 22:18, milsegv via cfe-dev <cfe-dev at lists.llvm.org>
wrote:
> Hello everyone,
>
> It may not be the best place to ask this but I found nothing on the
> internet about it.
> I'm working on Spectre V1 detection and stumbled upon the mitigation
> provided by clang, the
2020 Apr 20
12
RFC: Switching from Bugzilla to Github Issues [UPDATED]
Hi,
I wanted to continue discussing the plan to migrate from Bugzilla to Github.
It was suggested that I start a new thread and give a summary of the proposal
and what has changed since it was originally proposed in October.
== Here is the original proposal:
http://lists.llvm.org/pipermail/llvm-dev/2019-October/136162.html
== What has changed:
* You will be able to subscribe to notifications
2020 Apr 23
7
Cannot build master
Hi,
Using master at b0a1c0b72c9c61f8b0a223e08f43498abb64f5e8, I cannot build
LLVM. I configured with:
CC=clang CXX=clang++ cmake -DCMAKE_INSTALL_PREFIX=$HOME/opt/llvm11-git \
-DCMAKE_BUILD_TYPE=Release \
-DLLVM_BUILD_LLVM_DYLIB=ON \
-DLLVM_LINK_LLVM_DYLIB=ON \
-DBUILD_SHARED_LIBS=OFF \
-DLLVM_ENABLE_EH=ON \
-DLLVM_ENABLE_RTTI=ON \