search for: locical

Hi everyone, (Also CC'ed cfe-dev since this seems relevant to Clang, particularly the questions at the end.) I've been working on a library to generate LLVM IR that complies with platform ABIs (the current focus is on C but I'm also interested in ABIs for other languages). You can find it here: https://github.com/scross99/llvm-abi To explain further (for those who are unfamiliar),

Hi Reid, Thanks for your response. The issue is that every LLVM frontend needing ABI compliance has to re-implement the same target-dependent logic, which is a significant burden; the ABI compliance code inside Clang isn't really usable for other frontends as-is. We haven't got many good options here :-). I think a lot of people would've hoped that LLVM would provide the means for

On Tue, 30 Jun 2015 at 06:02 Hal Finkel <hfinkel at anl.gov> wrote: > ----- Original Message ----- > > From: "Stephen Cross" <scross at scross.co.uk> > > To: "Reid Kleckner" <rnk at google.com> > > Cc: "Clang Developers List" <cfe-dev at cs.uiuc.edu>, "LLVM Developers > Mailing List" <llvmdev at

...########################################### Then I did # xen-create-image --hostname xen-test01 that also caused no problems: # less /var/log/xen-tools/xen-test01.log ########################################## .... Setting up root password All done ######################################### The locical volumes are also well done.... But then # xm create xen-test01.cfg -c gave me ######################### Using config file "/etc/xen/xen-test01.cfg". Error: (22, 'Invalid argument') ######################### # less /etc/xen/xen-test01.cfg #####################################...

On Wed, 1 Jul 2015 at 08:19 Stephen Cross <scross at scross.co.uk> wrote: > Hi everyone, > > I was wondering if anyone could answer the questions in my first > email. These were: > > * Why does Clang generate 8 byte alignment for 16+ byte arrays on > x86-64, even though the AMD64 ABI seems to require 16 byte alignment? > * Clang has some logic in

...s a look at the list and, if no entry is found, looks at the disk directory. If a list entry was found, Samba should verify that that directory still exists. In idle times the list can be written to a spool directory. I know that this is no "clean" solution, because it introduces another locical layer between Samba and the filesystem (e.g. system attributes are lost, if the folder is renamed, garbage has to be cleaned then) - but it would be nice to have it for windows special folders working on network shares. Mit freundlichen Gr|_en, Matthias Stolte Return-Path: <keith.warno@valara...