search for: sensit

Am 07.09.2017 um 20:07 schrieb hw: > Gordon Messmer wrote: >> On 09/07/2017 08:11 AM, Stephen John Smoogen wrote: >>> This was always >>> problematic because DNS hostnames and email addresses in the RFC >>> standards were case insensitive >> >> >> Not quite.? SMTP is required to treat the "local-part" of the RCPT >> argument as case-sensitive, and to preserve case when relaying mail. >> The destination is allowed to treat addresses according to local >> policy, but in general SMTP...

...to length = V1.size(); > > V2.pop_back(); // Mutates *this > > auto zero = length - V1.size() > > > In this case, the compiler should “obviously” be able to CSE length, > allowing further simplification to substitute zero with 0. > > However, with a context sensitive AA, both &V1 and &V2 end up aliasing > the “this” pointer in std::vector::pop_back. As such, without context > sensitivity, you would falsely assume that “V2.pop_back();” could > modify “V1”. This is unfortunate, particularly for OO languages that > frequently use stati...

On 09/07/2017 08:11 AM, Stephen John Smoogen wrote: > This was always > problematic because DNS hostnames and email addresses in the RFC > standards were case insensitive Not quite.? SMTP is required to treat the "local-part" of the RCPT argument as case-sensitive, and to preserve case when relaying mail.? The destination is allowed to treat addresses according to local policy, but in general SMTP is case sensitive with regard to the user identifie...

> > It is not recommended to rely on local-part case, but it is indeed > case-sensitive. > > And this is to avoid such issues that postfix supports address > cleanup/canonicalisation before forwarding mails to dovecot. > > ---------- > RFC 5321: > > "Local-part = Dot-string / Quoted-string ; MAY be case-sensitive > [?] > While the above defini...

> On 9 Sep 2019, at 16.17, Philipp Faeustlin via dovecot <dovecot at dovecot.org> wrote: > >> It is not recommended to rely on local-part case, but it is indeed >> case-sensitive. >> And this is to avoid such issues that postfix supports address >> cleanup/canonicalisation before forwarding mails to dovecot. >> ---------- >> RFC 5321: >> "Local-part = Dot-string / Quoted-string ; MAY be case-sensitive >> [?]...

Hi, I was wondering, is there any code available on LLVM for flow sensitive context sensitive (fscs) pointer analysis? Thanks, Ray -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111102/01246f86/attachment.html>

...chrieb hw: >> >> Gordon Messmer wrote: >>> >>> On 09/07/2017 08:11 AM, Stephen John Smoogen wrote: >>>> >>>> This was always >>>> problematic because DNS hostnames and email addresses in the RFC >>>> standards were case insensitive >>> >>> >>> >>> Not quite. SMTP is required to treat the "local-part" of the RCPT >>> argument as case-sensitive, and to preserve case when relaying mail. The >>> destination is allowed to treat addresses according to local policy...

> > > For the example to work here the CSE pass itself needs to be > flow-sensitive and context-sensitive. I don't think that's how most > optimizations in LLVM work. If it is, then I agree with all you said. But > if it isn't, there's no point in bumping up the context sensitivity just > for the pointer analysis. > > As Daniel mentioned earlier i...

...t; > > This is correct. > Eventually, i hope george will have time to get back to CFL-AA and > turn it on by default. > > > If one looks at existing research literatures, there are even more > algorithm to consider for doing pointer analysis. Some are > field-sensitive, some are field-based, some are flow-sensitive, > some are context-sensitive. Even for flow-insensitive ones, they > could also be inclusion-style (-andersen-aa) and equality-style > (-steens-aa and -ds-aa). Those algorithms are often backed up by > rich theoretical f...

On 03/25/2016 08:08 PM, Chris Lattner wrote: > I’m still a big fan of context sensitive, flow insensitive, > unification based models. Interestingly I find the unification approach quite unsatisfactory sometime. What happens there is pointers with the same "depth" are too often clobbered together unless they are really unrelated to each other. > Contrary to you...

...hats right! I meant the points-to set. Sorry I didn't mention that. > I want to track back the value of the parameter to its definition -- an > "assignment" which could be indirect through a pointer to the value used > as the function argument. > > > Either way, flow-sensitivity can only give you more precise -- but still > > not necessarily exact -- answers. > > I am aware of the inexactness of (flow-sensitive) alias analysis. Is > there an exact way to accomplish this? > No, even the non-flow-sensitive version of the problem is statically undecida...

On Thu, September 7, 2017 14:07, hw wrote: > Gordon Messmer wrote: >> On 09/07/2017 08:11 AM, Stephen John Smoogen wrote: >>> This was always problematic because DNS hostnames and >>> email addresses in the RFC standards were case insensitive >> >> >> Not quite. SMTP is required to treat the "local-part" of the RCPT >> argument as case-sensitive, and to preserve case when relaying mail. >> The destination is allowed to treat addresses according to local >> policy, but in general SMTP is...

...org> > Further investigation showed me that it has to be a bug. > > I tested with Dovecot 2.2.36.3 (a7d78f5a2), Pigeonhole version 0.4.24 > (5a7e9e62): > > In this version the additional addresses in vacation :addresses > ["test at example.com"] are handled case-insensitive. > > In the new version: Dovecot 2.3.7.2 (3c910f64b), Pigeonhole version > 0.5.7.2 (7372921a) installed via https://repo.dovecot.org/, (same sieve, > same configuration) these addresses are handled case-sensitive. > > The case-sensitive matching of mail addresses, doesn't m...

...hanged since then :-) >> PS2: If no such evaluation exists in the past, I'd happy to do that myself and report back my findings if anyone here is interested. >> I don't think any of the world is set up to make that valuable. >> >> Nothing takes advantage of context sensitivity, flow sensitivity, etc. > I agree that nothing takes advantage of context sensitivity. But I would argue against flow sensitivity, field sensitivity, heap model and external function models. Flow sensitivity is helpful when the optimization pass itself is flow-sensitive (e.g. adce, gvn), an...

> On Mar 25, 2016, at 9:04 PM, Jia Chen <jchen at cs.utexas.edu> wrote: > > On 03/25/2016 08:08 PM, Chris Lattner wrote: >> I’m still a big fan of context sensitive, flow insensitive, unification based models. > > Interestingly I find the unification approach quite unsatisfactory sometime. What happens there is pointers with the same "depth" are too often clobbered together unless they are really unrelated to each other. > >> C...

Perhaps by "value" you mean points-to set? Either way, flow-sensitivity can only give you more precise -- but still not necessarily exact -- answers. Yours, Andrey === Compiler Architect NXP On Fri, Mar 10, 2017 at 6:39 PM, Flamedoge via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > For a given argument of a call instruction in the cfg: Where d...

Hi, I am looking for some flow-sensitive (context-insensitive) alias analysis algorithm implemented in LLVM. (I use LLVM 3.9, hope to switch to 4.0 soon.) As far as I know, none of the built-in analysis (basicAA, globals-modref, andersAA, etc.) is intended to be flow-sensitive. So I searched and came across these two 1. https://github...

Dear R users, I have been trying to estimate global sensitivity indices such as the sobol 1st and 2nd order indices. I managed to obtain the PRCC. The example presented in the sensitivity package on sobol2002 seems to work well for linear models: for example: calculate y for given x values. However, when trying to apply this technique to dynamic models...

Is IMAP supposed to be case sensitive or case in-sensitive? It seemed it would be case sensitive because I've had different cases of folders. But today I found I had two folders "Spam" and "spam", with directories ".INBOX.Spam" and ".INBOX.spam" on the server. Messages existed in each d...

FWIW, Ben Hardekopf asked me to post this for him on the subject Regarding Whaley and Lam's BDD-based approach to context-sensitive analysis, there is a paper by the same research group (Avots et al in ICSE'05) that adapts their technique for C. The results are not very encouraging -- their system doesn't scale nearly as well for C as it did for Java. The primary difference is that unlike Java, in C top-level variabl...