Displaying 20 results from an estimated 25 matches for "20190507".
Did you mean:
20170507
2019 May 07
2
[Bug 110631] New: EDID confusion with LG 4K TV as monitor running X rather than wayland
...ifferent systems with more conventional resolution
monitors, nouveau works fine.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20190507/9f735c1b/attachment.html>
2019 May 06
2
RegAlloc Q: spill when implicit-def physreg is also the output reg of instruction
Hi LLVM,
I ran into a case where RegAlloc would insert a spill across instruction
that had same register for output operand and implicit-def. The effect
this had was that spill code would immediately overwrite the output
result. Is this the expected result of setting up MyInst this way? In
other words, does RegAlloc know to not insert spill in case it sees that
output reg is same as one of
2019 May 07
2
Reuse llvm::ExecutionEngine
..., USt.ID-Nr. DE 114 165 789 Geschäftsführer: Dr. Hiroshi Nakamura, Dr. Robert Plank, Markus Bode, Heiko Lampert, Takashi Nagano, Takeshi Fukushima. Junichi Tajika
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190507/fd7f9978/attachment.html>
2019 May 03
4
[LLD] Should --compress_debug_sections be enabled (=zlib) by default ?
Hi,
In the file lld/ELF/Driver.cpp in function getCompressDebugSections we can see that the current default for lld is no debug section compression. It looks like tools like gdb, valgrind, elfutils, gcc's backtrace lib currently support compressed symbols. Since perf can use libdw from elfutils, I guess it supports it too.
Do you think it's time to enable compressed debug section by
2019 May 06
4
config help & pid file not existing issue
Tinc team:
I'm creating a vpn for my work laptop and vps and got trapped, here are my
config files:
on laptop:
*tinc.conf
Name = envy13
Device = /dev/net/tun
ConnectTo = main
*hosts/main
Address = <my vps ext ip address>
Port = 655
Subnet = 10.0.0.1/32
*hosts/envy13
Port = 655
Subnet = 10.0.0.2/32
*tinc-up
#!/bin/sh
ip link set myvpn up
ip addr add 10.0.0.2/32 dev myvpn
ip route add
2019 May 07
2
RegAlloc Q: spill when implicit-def physreg is also the output reg of instruction
...mailing list
>> llvm-dev at lists.llvm.org <mailto: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/20190507/06eec7bc/attachment.html>
2019 May 07
0
Project :Adding new compiler optimization Passes to Codegen
...lo
I am looking to contribute to the about Nouveau based project.
Could you please tell me how I can participate in XORG EVOC for this
project?
Thank you
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20190507/689d4c57/attachment.html>
2019 May 07
1
config help & pid file not existing issue
...t; _______________________________________________
> tinc mailing list
> tinc at tinc-vpn.org
> https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20190507/b4873e19/attachment.html>
2019 May 08
0
error:060A7094:digital envelope routines:EVP_EncryptUpdate:invalid operation
...rom the Debian source, and still hit the
same issue. 1.0 works fine, but I'd like to upgrade to 1.1
Any ideas on how to fix it?
I'm using OpenSSL 1.1.1b-2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20190507/a6d1b0b7/attachment.html>
2019 May 07
1
Getting listed on the directory
...p://64.71.79.181:4272/
*Thanks in advance! *
[image: --]
Nicholas Kyriakides
[image: https://]about.me/shillos
<https://about.me/shillos?promo=email_sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190507/8daa42c8/attachment.html>
2019 May 07
0
dlopen failed: cannot locate symbol "opus_projection_encoder_ctl" referenced by "libopusenc.so"
...format=0
LOCAL_LDFLAGS := -llog
LOCAL_SHARED_LIBRARIES := libopus libopusenc
LOCAL_ASSET_DIR := $(LOCAL_PATH)/assets
include $(BUILD_SHARED_LIBRARY)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/opus/attachments/20190507/364d3f49/attachment-0001.html>
2019 May 07
2
RHEL 8 released
...ttps://www.centos.org
gpg key: 56BEC54E | twitter: @arrfab
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://lists.centos.org/pipermail/centos/attachments/20190507/61126446/attachment-0002.sig>
2019 May 04
2
Source client with HTTP PUT
Good afternoon,
On Sat, 2019-05-04 at 10:19 -0400, Fred Gleason wrote:
> On Fri, 2019-05-03 at 12:24 -0400, Fred Gleason wrote:
>
> > Don't use PUT at all. Instead, open a TCP socket connection to the
> port
> > that the server is running on, write all of your headers to that
> > (terminating each one with a CR/LF), send a naked CR/LF to tell
> Icecast
>
2019 May 03
2
Total response file count limited to 21
IMO, a limit of at most 20 nested response files would make a lot more
sense than 20 total response files. I don't think the total should really
have a limit at all.
Since we expand the files in place while iterating over the arglist, we'd
need to keep a separate array listing the end-offset of each file we're
currently nested within, and update the offsets with every expansion of
2019 May 07
2
[NEW] LLVM / Clang Social in Chicago
...vf4mddxy2b2hybn4
[1] https://www.meetup.com/LLVM-clang-Chicago-socials/
-------------- 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/20190507/75e32621/attachment.sig>
2019 Apr 30
3
[RFC][clang/llvm] Allow efficient implementation of libc's memory functions in C/C++
Thx for the feedback David.
So we're heading toward a broader
> __attribute__((disable_call_synthesis))
David what do you think about the additional version that restrict the
effect to a few named functions?
> e.g. __attribute__((disable_call_synthesis("memset", "memcpy", "sqrt")))
A warning should be issued if the arguments are not part of
2019 May 06
4
very high traffic without any load
Lars, interesting - do you have an example of what that might look like in
the config file?
Thanks!
On Sun, May 5, 2019 at 6:00 PM Lars Kruse <lists at sumpfralle.de> wrote:
> Hello Christoph,
>
> I am glad, that you discovered the source of the problem!
>
>
> Am Sat, 4 May 2019 08:30:28 +0200
> schrieb "Christopher Klinge" <Christ.Klinge at web.de>:
2019 May 07
11
RHEL 8 released
This morning Red Hat announced the general availability of Red Hat
Enterprise Linux 8.
More details at
https://www.redhat.com/en/about/press-releases/red-hat-enterprise-linux-8-every-enterprise-every-cloud-every-workload?sc_cid=701f2000001OIIOAA4
--
Rich Bowen: CentOS Community Manager
rbowen at redhat.com
@rbowen // @CentOSProject
1 859 351 9166
2019 Jan 21
7
[Bug 109407] New: GTX 1050 fails to initialise acceleration
https://bugs.freedesktop.org/show_bug.cgi?id=109407
Bug ID: 109407
Summary: GTX 1050 fails to initialise acceleration
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau at
2019 May 06
3
Data Stale issue
On Mon, 6 May 2019, Gareth Davies wrote:
> Just to say, I stopped the driver and started it again and the errors went
> away! However, I turned off power to the UPS but I wasn’t receiving any
> e-mails :( also when I rebooted the RPi the driver/service didn’t start back
> up automatically...
>
> I wonder if you have any thoughts on the above?
Those are issues with