similar to: [PATCH] guestfish: Enable grouping in string lists

This patch lacks updated documentation and tests. This change adds the ability to group entries in a string list with single quotes. So the string: "'foo bar'" becomes 1 token rather than 2. Consequently single quotes must now be escaped: "\'" resolves to a literal single quote. Incidentally, this change also alters another, probably unintentional behaviour of

There's a new syntax check rule from gnulib. It requires that you write e.g., exit (EXIT_SUCCESS), not exit (0). And the same for 1/EXIT_FAILURE and any other constants. There were a lot of violations, including a few false positives, so I started with the exemptions (see the .x-sc file below). Then I converted the vast majority automatically, with this: maint: use EXIT_SUCCESS and

Hi, I have a data set with variables that are _not_ missing at random. Now I use a package for learning a Bayesian Network which won't accept NA as a value. From a database I query data.frames with k,k+n,k+2n, ... variables (there are always at least k variables as leftmost columns). Using rbind.fill from the reshape package on two data frames I would get a data frame like trg_type

Greetings, As previously reported by me to the Debian bug tracking system: ---------------------------------------------------------------------- An access list in rsyncd.conf may contain hostnames as well as addresses. It may contain several patterns to match against. address_match (in access.c) does this by trying to match hostname and address against each of the patterns until a match is

innetgr.. much easier.. Had a look for the user section but didn't find it in my 15 seconds of looking.. --- access.c 2003-07-30 16:12:27.000000000 +1000 +++ ../rsync-2.6.0-Linux/access.c 2004-02-01 23:21:12.000000000 +1100 @@ -22,10 +22,21 @@ */ #include "rsync.h" +#include <netdb.h> static int match_hostname(char *host, char *tok) { + char

Hi MyDeveloperDay, We are using the released version of clang-format / clang-tidy (not necessarily the latest release). I think it makes sense to use most recent versions of the tools: https://github.com/google/llvm-premerge-checks/issues/196 Kind regards, Mikhail On Wed, Jun 3, 2020 at 3:40 PM MyDeveloper Day <mydeveloperday at gmail.com> wrote: > Mikhail > > Firstly let me

Hi, I'm trying to get rsync 2.5.6 to authenticate users via openldap-2.0.23. I was looking through the mailing list archives and found a patch for rsync-2.4.6 that does this for me. I was just wondering if this is still valid, or if there has been a new patch or new implementation that has superceded this patch. Any help would be great. The message I am referring to is as follows:

I'm trying to use linphone-android with asterisk but there is an aspect of the way asterisk and linphone-android interact with MESSAGE transactions that is causing problems. The linphone-android folks consider both the To: and From: address in MESSAGE transactions when deciding which "chat" to put a received MESSAGE into. Every combination of To: and From: address are a separate

> On Jan 20, 2017, at 11:17 AM, Tian, Xinmin <xinmin.tian at intel.com> wrote: > >>>>> This means that the optimizer has to be aware of it, I’m missing the magic here? > > This is one option. > > The another option is that, as I mentioned in our LLVM-HPC paper in our implementation. We have a "prepare phase for pre-privatization" can be invoked

>>>>Ok, but this looks like a “workaround" for your specific use-case, I don’t see how it can scale as a model-agnostic and general-purpose region semantic. I would say it is a design trade-off. Regardless it is a new instruction or an intrinsics with token/tag, it will consist of model-agnostic part and model-non-agnostic part. The package comes with a framework for parsing

> On Jan 31, 2017, at 5:38 PM, Tian, Xinmin <xinmin.tian at intel.com> wrote: > >>>>> Ok, but this looks like a “workaround" for your specific use-case, I don’t see how it can scale as a model-agnostic and general-purpose region semantic. > > I would say it is a design trade-off. I’m not sure if we’re talking about the same thing here: my understanding at

Let me try this. You can simply consider the prepare-phase (e.g. pre-privatization) were done in FE (actually a library can be used by multiple FEs at LLVM IR level), the region is run with 1 thread, region annotation (scope, single-entry-single-exit) as memory barrier conservatively for now (instead of checking individual memory dependency, aliasing via tags which is the actual

The first c-set cleans up the list of excluded syntax-checks. The second enables the sc_avoid_ctype_macros test and changes each use of a ctype macro like isspace to c_isspace. This makes it so such tests (often parsing-related) is locale-independent. Otherwise, in some odd corner cases (combination of non-C locale and perverted inputs), I suspect that libguestfs tools would mistakenly accept

> On Jan 31, 2017, at 6:48 PM, Tian, Xinmin <xinmin.tian at intel.com> wrote: > > Let me try this. > > You can simply consider the prepare-phase (e.g. pre-privatization) were done in FE (actually a library can be used by multiple FEs at LLVM IR level), the region is run with 1 thread, region annotation (scope, single-entry-single-exit) as memory barrier conservatively

Tok tok!!! Still waiting "_"

Commit b91b39e06ab7eb9b9b06c8b4dfef2ef9f381ab19 changed the separator to ':', although this creates parsing issues when there are fields with colons (for example lv_tags=imgbased:pool). Change once more the separator, but this time using a non-printable character such as '\r': while it will produce uglier debug logs, this should greatly reduce the possibilities of conflicts with

Hi, I'm going to club together some responses. I agree that outlining function sub-bodies and passing in the function pointers to said outlined bodies to OpenMP helpers lets us correctly implement the semantics we need. However, unless I severely misunderstood the thread, I thought the key idea was to move *away* from that representation and towards a representation that _allows_

In this case, inliner is educated to add all local variables to the tag of enclosing parallel region, if there is enclosing parallel region. In our icc implementation, it is even simple, as we have routine level symbol table, the inliner adds ”private” attribute to those local variables w/o checking enclosing scope, the parallelizer does check and use it. Xinmin From: mehdi.amini at apple.com

> On Jan 20, 2017, at 10:44 AM, Tian, Xinmin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Sanjoy, the IR would be like something below. It is ok to hoist alloca instruction outside the region. There are some small changes in optimizer to understand region-annotation intrinsic. > > { void main() { > i32* val = alloca i32 > tok =

> On Jan 31, 2017, at 7:53 PM, Tian, Xinmin <xinmin.tian at intel.com> wrote: > > In this case, inliner is educated to add all local variables to the tag of enclosing parallel region, if there is enclosing parallel region. So isn’t it a good example that shows that your intrinsic *cannot* be opaque and that IR passes need to be modified to handle not only the IR-region