search for: sensitivity

...cal-part of a mailbox MUST BE treated as case sensitive. Therefore, SMTP implementations MUST take care to preserve the case of mailbox local-parts. In particular, for some hosts, the user "smith" is different from the user "Smith". However, exploiting the case sensitivity of mailbox local-parts impedes interoperability and is discouraged. Mailbox domains follow normal DNS rules and are hence not case sensitive. Alexander

...s 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 static dispatch (like C++, Swift, and others). > > > That said, I have no idea what you’re referring to by > "context-insensitive...

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

...; maximum interoperability, a host that expects to receive mail SHOULD avoid > defining mailboxes where the Local-part requires (or uses) the > Quoted-string form or where the Local-part is case-sensitive." > > And therefore ?receive liberally? policy that wants to assume case-insensitivity should single-case the address IN THE COMPARISON. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20190904/3d002a84/attachment.html>

...interoperability, a host that expects to receive mail >> SHOULD avoid defining mailboxes where the Local-part requires (or >> uses) the Quoted-string form or where the Local-part is case-sensitive." >> And therefore ?receive liberally? policy that wants to assume case-insensitivity should single-case the address IN THE COMPARISON. > The local-part MAY be case-sensitive, but in general I don't know any mail addresses where the case matters. > Thus it is hard for me to understand, why this comparison of the vacation address is case-sensitive. Whether the final recipie...

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>

...ilbox MUST BE treated as case sensitive. > Therefore, SMTP implementations MUST take care to preserve the case > of mailbox local-parts. In particular, for some hosts, the user > "smith" is different from the user "Smith". However, exploiting the > case sensitivity of mailbox local-parts impedes interoperability and > is discouraged. Mailbox domains follow normal DNS rules and are > hence not case sensitive. > Thanks for the clarification to my original email. I misremembered RFC821 and thought it was for the entire part.. Commands and re...

...> > 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 in this thread, the analysis analysis > framework in LLVM doesn't provide any APIs for flow-sensitive queries as > well as context-sensitive queries. This design choice almost eliminate any > possibilities for a...

...data first. > > > 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), and field...

...tive, > 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 your claim, context sensitivity *is* useful for mod-ref > analysis, e.g. “can I hoist a load across this call”? Context > sensitivity improves the precision of the mod/ref set of the call. > I'm not sure about that. How often does mod-ref information change across callsites? Isn't a good context-insensitive f...

...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 undecidable f...

...ocal-part of a mailbox MUST BE treated as case sensitive.__ Therefore, SMTP implementations MUST take care to preserve the case of mailbox local-parts. In particular, for some hosts, the user "smith" is different from the user "Smith". However, exploiting the case sensitivity of mailbox local-parts impedes interoperability and is discouraged. Mailbox domains follow normal DNS rules and are hence not case sensitive. . . . Case munging of the local part is handled by the local delivery agent in my experience. The Cyrus LMTP service can be, and often is, configure...

On Wed, Sep 4, 2019 at 8:25 AM Philipp Faeustlin via dovecot < dovecot at dovecot.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. >

...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), and fie...

...ion 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 your claim, context sensitivity *is* useful for mod-ref analysis, e.g. “can I hoist a load across this call”? Context sensitivity improves the precision of the mod/ref set of the call. >> > I'm not sure about that. How often does mod-ref information change across callsites? Isn't a good context-insensitive func...

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 does t...

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.com/unsw-corg/SVF by Yulei Sui (for LLVM 3.8) 2.

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 (SIR...

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 directory on the server and they were different. The messages

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