search for: 20191004

Displaying 15 results from an estimated 15 matches for "20191004".

Did you mean: 20191003
2019 Oct 04
0
CentOS 8 Release Notes - Czech translation
...________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > https://lists.centos.org/mailman/listinfo/centos-docs > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-docs/attachments/20191004/404e0688/attachment-0006.html>
2019 Oct 04
2
Home Directory Creation
> On 4 Oct 2019, at 0.47, Asai via dovecot <dovecot at dovecot.org> wrote: > > One thing Timo mentioned in this post (https://dovecot.org/list/dovecot/2013-May/090397.html) is: "You could also change your new user creation to trigger mkdiring the user's home." > > Does anyone know where I can find any documentation on this, or has anyone done this? > It
2019 Oct 04
0
Home Directory Creation
...anks for your reply. We're just using a SQL backend to store user info.? How does this get done with LDAP? Perhaps we can do the same with a SQL backend. Asai -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20191004/a63d3466/attachment.html>
2019 Oct 04
3
Full 'restrict' support in LLVM.
Hi all, I am happy to announce that Synopsys wants to contribute its implementation of 'C99 restrict' to the LLVM project. [1] This implementation is based on Hal Finkel's local restrict patches and on the 'RFC: Full 'restrict' support in LLVM' [2] Any help with extra testing and code review is welcome. To be generally useful, there are also some small gaps [1] that
2019 Sep 27
3
What about multiple MachineMemOperands in one MI (BranchFolding/MachineInstr::mayAlias)?
On 9/27/19 7:33 AM, Matt Arsenault via llvm-dev wrote: > > >> On Sep 27, 2019, at 09:07, Björn Pettersson A via llvm-dev >> <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> >> Obviously we do not store into two locations (it is still a single >> two byte store). >> So is it (always) correct to interpret the list of
2019 Oct 04
2
CentOS 8 Release Notes - Czech translation
Hello, I see the page, but there is no button to edit it. If I try to add ?action=edit to URL, wiki shows message "Nem?te dovoleno editovat tuto str?nku." (You are not allowed to edit this page). Jan ?t 3. 10. 2019 v 21:08 odes?latel David Hrb?? <david-lists at hrbac.cz> napsal: > > Jan, > > I have created the page. Are you able to edit it? > > Regards. > DH
2019 Oct 04
4
vectorize.enable
..._______________________________________________ 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/20191004/43fb82c6/attachment-0001.html>
2019 Sep 27
2
Opportunity to split store of shuffled vector.
> I may be missing something obvious, but what is `vector` defined as here? Can you provide a buildable example? Sorry, I should provide a cross-platform version using vector extension of frontend :) `vector int` is a vector extension on PowerPC, which is enabled if you set target to PowerPC platforms. Example below should be successfully compiled in any platform: typedef float v4sf
2019 Oct 04
4
Exposing the New Pass Manager in the LLVM C API
Hi all, At some time in the near future we would like to allow for Rust to use the new PM. As I understand it, Rust uses LLVM through the stable LLVM C API, which currently only provides an interface to the legacy PM. We wanted to ask what people think about how we should go about exposing the new PM through this API. We can think of 3 possibilities for now: 1) Just replace the API to expose the
2019 Oct 02
2
vectorize.enable
Am Mi., 2. Okt. 2019 um 15:56 Uhr schrieb Finkel, Hal J. <hfinkel at anl.gov>: > > It's done by the WarnMissedTransformation and just looks for > > transformation metadata that is still in the IR after all passes that > > should have transformed them have ran. That is, it does not know why > > it is still there -- it could be because the LoopVectorize pass is not
2019 Oct 04
2
[cfe-dev] CFG simplification question, and preservation of branching in the original code
...rg/cgi-bin/mailman/listinfo/llvm-dev -- Hal Finkel Lead, Compiler Technology and Programming Languages Leadership Computing Facility Argonne National Laboratory -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191004/28d09ebb/attachment.html>
2019 Oct 04
2
Opportunity to split store of shuffled vector.
..._____________________________ > 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/20191004/1ac25391/attachment.html>
2019 Oct 03
2
[cfe-dev] CFG simplification question, and preservation of branching in the original code
Hi all, > On 2 Oct 2019, at 14:34, Sanjay Patel <spatel at rotateright.com> wrote > Providing target options/overrides to code that is supposed to be target-independent sounds self-defeating to me. I doubt that proposal would gain much support. > Of course, if you're customizing LLVM for your own out-of-trunk backend, you can do anything you'd like if you're willing to
2019 Oct 01
5
PR43374 - when should comparing NaN values raise a floating point exception?
Hi, I’ve been investigating https://bugs.llvm.org/show_bug.cgi?id=43374, which is about clang/llvm producing code that triggers a floating point exception when x is NaN, when targeting ARM, in the below code example. int bar(float x) { return x!=x ? 0 : 1; } The C99 standard states in section 7.12.14: """ The relational and equality operators support the usual mathematical
2014 Mar 10
122
[Bug 75985] New: HDMI audio device only visible after rescan
https://bugs.freedesktop.org/show_bug.cgi?id=75985 Priority: medium Bug ID: 75985 Assignee: nouveau at lists.freedesktop.org Summary: HDMI audio device only visible after rescan QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: jean-louis at