search for: sensitively

Displaying 20 results from an estimated 5595 matches for "sensitively".

Did you mean: sensitive
2017 Sep 07
3
login case sensitivity
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
2016 Mar 28
4
Existing studies on the benefits of pointer analysis
On 03/28/2016 12:37 AM, Chris Lattner wrote: > It changes all the time. Here’s a trivial example, assume no inlining > and no AA other than the one in question: > > std::vector<int> V1 = { 1, 2, 3 }; > std::vector<int> V2 = { 4, 5, 6 }; > > V1.pop_back(); // Mutates *this > > auto length = V1.size(); > > V2.pop_back(); //
2017 Sep 07
2
login case sensitivity
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
2019 Sep 04
2
[Bug] Sieve vacation :addresses match only case-sensitive?
> > 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 definition
2019 Sep 09
1
[Bug] Sieve vacation :addresses match only case-sensitive?
> 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
2011 Nov 02
1
[LLVMdev] flow sensitive context sensitive pointer analysis
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>
2017 Sep 07
0
login case sensitivity
On 7 September 2017 at 16:07, Alexander Dalloz <ad+lists at uni-x.org> wrote: > 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
2016 Mar 28
0
Existing studies on the benefits of pointer analysis
> > > 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
2016 Mar 21
6
Existing studies on the benefits of pointer analysis
Hi Daniel, On 03/21/2016 11:05 AM, Daniel Berlin wrote: > > > On Tue, Mar 15, 2016 at 1:37 PM, Jia Chen via llvm-dev > <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > > Dear llvm devs, > > tl;dr: What prevents llvm from switching to a fancier pointer > analysis? > > > Nothing. > > > Currently,
2016 Mar 26
2
Existing studies on the benefits of pointer analysis
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 your claim,
2017 Mar 12
2
flow-sensitive alias analysis
On Sun, Mar 12, 2017 at 2:55 PM, Oliver Braunsdorf via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > Perhaps by "value" you mean points-to set? > > Thats 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
2017 Sep 08
0
login case sensitivity
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
2019 Sep 04
2
[Bug] Sieve vacation :addresses match only case-sensitive?
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. >
2016 Mar 26
0
Existing studies on the benefits of pointer analysis
On Mar 21, 2016, at 10:00 AM, Jia Chen via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> So my question here is: what kind(s) of precision really justify the cost and what kinds do not? >> >> Depends entirely on your applications. >> >> Has anybody done any study in the past to evaluate what kinds of features in pointer analyses will benefit what
2016 Mar 28
0
Existing studies on the benefits of pointer analysis
> 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
2017 Mar 11
3
flow-sensitive alias analysis
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 the > value of
2017 Mar 10
2
flow-sensitive alias analysis
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.
2012 Jan 19
0
Global sensitivity indices using sensitivity package: sobol, sobol2002
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 type), the error messages just keep
2011 Jan 05
2
case (non-)sensitivity for folder names
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
2008 Mar 08
0
[LLVMdev] Google Summer of Code Idea
...op-level variables can have their address taken and be passed between functions, which requires the analysis to maintain 2 contexts for each points-to relation: one for the pointer and one for the pointee. The other problem with their method is that only the top-level variables are treated context-sensitively; everything in the heap (e.g. for Java, all object fields) is context-insensitive. I spoke with John Whaley about this and he said they've tried to use a context-sensitive heap model, but they couldn't get it to scale at all. My personal feeling (backed up by results from some other resear...