search for: douma

I am out of the office until 05/03/2010. I will respond to your message when I return. If you need immediate assistance please call the CSC or contact the Citrix Administrators group via email. Note: This is an automated response to your message "Xen-users Digest, Vol 62, Issue 125" sent on 4/24/2010 12:47:44 PM. This is the only notification you will receive while this person is

Hi Andy, Andrew Trick wrote: >> On Sep 23, 2016, at 7:50 AM, Christof Douma <Christof.Douma at arm.com <mailto:Christof.Douma at arm.com>> wrote: >> >> I can’t help to ask. Why not define a wrapping nsw instruction as UB, instead of “delayed UB” aka poison? I believe we >> have the notion of poison solely to ease the movement of instruction...

On 23 Sep 2016, at 11:08, Andrew Trick via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> On Sep 23, 2016, at 2:09 AM, Sanjoy Das <sanjoy at playingwithpointers.com> wrote: >> >> Hi all, >> >> This is about a project I've been prototyping on-and-off for a while >> that has finally reached a point where I can claim it to be >>

Hi Phil. You more or less answered your own question, but let me give you some more info. Maybe it is of use. >From what I understand the SchedMachineModel is the future, although it is not as powerful as itineraries at present. The mi-scheduler is mostly developed around out-of-orders cores, I believe (I love to hear arguments on the contrary). Some of the constraints that can be found in

...by the code generation is based on GRIN (http://www.cs.chalmers.se/~boquist/phd/index.html) which promotes a calling convention based on passing arguments in registers as much as possible. Is it possible to return multiple values in registers? I could not find anyting on this. Regards, Christof Douma

Hi, I'm planning to implement "execute only" support in the ARM code generator. This basically means that the compiler will not generate data access to the generated code sections (e.g. data and code are strictly separated into different sections). Outline: - Add the subtarget feature/attribute "execute-only" to the ARM code generator to enable the feature.

On Wed, 1 May 2019 at 15:03, Finkel, Hal J. <hfinkel at anl.gov> wrote: > > On 5/1/19 7:22 AM, Christof Douma via llvm-dev wrote: > > Hi Snider. > > > > As you and Peter mentioned there are indeed toolchains that allow location placement from within the C/C++ source code, using attributes or similar. I always wonder if such extension is worth the effort. There are downsides like the non-s...

...n tricks and shell one-liners:If you have another position (like in the How-To articles, under 16.Storage devices, Logical Volume Management, and RAID)?then we can put it there. The article will have a name like: "Renaming the root volume-group after a fresh Centos7 installation" Georgios Doumas? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-docs/attachments/20171220/2270c834/attachment-0002.html>

Hi to all! I?m writing a python module (python+sqlalchemy) to manage user and domain configuration on my system (I hope to get a CLI tool, a Web app and even a native Mac app, via PyObjc, from my lib). I?m implementing password crypto, but I have some problem in generating CRAM-MD5 password, dovecot style. I?ve found an old discussion on this mailing list and a piece of Perl that works, but I need

...placement of an object without having to manage the placement themselves in the linker command file. ~ Todd -----Original Message----- From: Peter Smith [mailto:peter.smith at linaro.org<mailto:peter.smith at linaro.org>] Sent: Wednesday, May 1, 2019 10:27 AM To: Finkel, Hal J. Cc: Christof Douma; Snider, Todd; llvm-dev Subject: [EXTERNAL] Re: [llvm-dev] RFC - a proposal to support additional symbol metadata in ELF object files in the ARM compiler On Wed, 1 May 2019 at 15:03, Finkel, Hal J. <hfinkel at anl.gov<mailto:hfinkel at anl.gov>> wrote: > > On 5/1/19 7:22 AM, Chri...

Hello, I have confirmed that the recently-reported vulnerability in Elm is also present in Elm-ME+ and thus also in Debian GNU/Linux version 1.2, prerelease version 1.3, and development tree "unstable". Below is a short diff to correct the problem. Debian GNU/Linux 1.2.x uses stock Elm 2.4pl25. Users of that version of Elm should upgrade to Elm-ME+ as detailed below. Debian 1.3

...o manage >> the placement themselves in the linker command file. >> >> ~ Todd >> >> -----Original Message----- >> From: Peter Smith [mailto:peter.smith at linaro.org] >> Sent: Wednesday, May 1, 2019 10:27 AM >> To: Finkel, Hal J. >> Cc: Christof Douma; Snider, Todd; llvm-dev >> Subject: [EXTERNAL] Re: [llvm-dev] RFC - a proposal to support additional >> symbol metadata in ELF object files in the ARM compiler >> >> On Wed, 1 May 2019 at 15:03, Finkel, Hal J. <hfinkel at anl.gov> wrote: >> > >> > On...

...cement of an object without having to manage the > placement themselves in the linker command file. > > ~ Todd > > -----Original Message----- > From: Peter Smith [mailto:peter.smith at linaro.org] > Sent: Wednesday, May 1, 2019 10:27 AM > To: Finkel, Hal J. > Cc: Christof Douma; Snider, Todd; llvm-dev > Subject: [EXTERNAL] Re: [llvm-dev] RFC - a proposal to support additional > symbol metadata in ELF object files in the ARM compiler > > On Wed, 1 May 2019 at 15:03, Finkel, Hal J. <hfinkel at anl.gov> wrote: > > > > On 5/1/19 7:22 AM, Christof...

Hi Snider. As you and Peter mentioned there are indeed toolchains that allow location placement from within the C/C++ source code, using attributes or similar. I always wonder if such extension is worth the effort. There are downsides like the non-standard ways of communicating this information to the linker, different places that control location of things (linker and compiler sources). I would

David, I'm glad you mentioned Discord's T&Cs. I'm not generally concerned about these kinds of things, but Discord's seems particularly aggressive. Particularly the phrase "perpetual, nonexclusive, transferable, royalty-free, sublicensable, and worldwide license" is... a lot. Since LLVM is a permissively licensed project I assume many of our contributors care about