search for: dialectal

Reply to Kiran Chandramohan: > You are welcome to participate, provide feedback and criticism to change the design as well as to contribute to the implementation. Thank you Kiran. > But the latest is what is there in the RFC in discourse. I have used this as reference for the response. > We did a study of a few constructs and clauses which was shared as mails to flang-dev and the

Please find the reply inline below On Sun, Feb 16, 2020 at 12:59 AM Mehdi AMINI <joker.eph at gmail.com> wrote: > > > On Sat, Feb 15, 2020 at 10:42 AM Vinay Madhusudan via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Reply to Kiran Chandramohan: >> >> > You are welcome to participate, provide feedback and criticism to >> change the

Hi, I have few questions / concerns regarding the design of OpenMP dialect in MLIR that is currently being implemented, mainly for the f18 compiler. Below, I summarize the current state of various efforts in clang / f18 / MLIR / LLVM regarding this. Feel free to add to the list in case I have missed something. 1. [May 2019] An OpenMPIRBuilder in LLVM was proposed for flang and clang frontends.

Please find the reply inline below: On Tue, Feb 18, 2020 at 8:02 AM Mehdi AMINI <joker.eph at gmail.com> wrote: > > > On Mon, Feb 17, 2020 at 10:29 AM Vinay Madhusudan <vinay at compilertree.com> > wrote: > >> Please find the reply inline below >> >> On Sun, Feb 16, 2020 at 12:59 AM Mehdi AMINI <joker.eph at gmail.com> wrote: >>

I have a kyocera TA-205C printer that is can scan to pdf and place the file on a smb share. I have a user on my domain (PCEDOM\printers) that can login and access the share. I tested it out with smbclient and was able to create a file where the printer is supposed to be able to put the file. The printer gave a very unhelpful error message, so I did a packet capture to find the error. (see

Thanks for the reply! It sounds like LLVM IR is being considered for optimizations in OpenMP constructs. There seems to be plans regarding improvement of LLVM IR Framework for providing things required for OpenMP / flang(?) Are there any design considerations which contain pros and cons about using the MLIR vs LLVM IR for various OpenMP related optimizations/ transformations? The latest RFC [

On Wed, Sep 11, 2019 at 1:54 PM David Greene <greened at obbligato.org> wrote: > Mehdi AMINI <joker.eph at gmail.com> writes: > > > Of course by its nature, MLIR doesn't lend itself to concrete semantic > >> descriptions, though I would expect the affine dialect (and others) to > >> have documentation on par with the LLVM IR. > > > > >

On Tue, Sep 10, 2019 at 1:40 PM David Greene via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Renato Golin via llvm-dev <llvm-dev at lists.llvm.org> writes: > > > But perhaps more importantly, as Hal states clearly, is the need for > > an official specification, similar to the one for LLVM IR, as well as > > a formal document with the expected semantics into

Hello, I was reading about secure Dialect negotiation to prevent man-in-middle to downgrade dialects & capabilities. _https://blogs.msdn.microsoft.com/openspecification/2012/06/28/smb3-secure-dialect-negotiation/_ I wanted to ask, is there any option to disable SMB2 to do dialect renegotiation as present in Windows8 clients, as they can control using RequireSecureNegotiate. -- Thanks Amit

On Wed, Oct 3, 2012 at 1:19 AM, Jim Grosbach <grosbach at apple.com> wrote: > What's the use case? the use case is that we can print out the assembly using alternative dialect. currently, on Intel machine, the default dialect is AT&T, and we cannot change that to Intel syntax without using cl:opt. the new public method lets us change the dialect without having cl:opt involved.

currently, there is no (easy) way to set the AssemblerDialect. the only method i am aware of is to set that via cl:opt. this patch fixes that by adding a public function setAssemblerDialect() to class MCAsmInfo. Signed-off-by: Jun Koi <junkoi2004 at gmail.com> diff --git a/include/llvm/MC/MCAsmInfo.h b/include/llvm/MC/MCAsmInfo.h index 97aad71..cd08a7e 100644 ---

Please help me interpret the following results. The full model (Schwa~Dialect*Prediction*Reduction) was reduced via both update() and step(). The minimal adequate model is: ancova<-lm(Schwa~Dialect+Prediction+Reduction+Dialect:Prediction) Schwa is response variable Dialect is factor, two levels ("QF","SF") Prediction is factor, two levels ("High","Low")

Hi all How can I list of all opened connections to a share and see protocol negotiated? Ubuntu 12.04, Samba 3 & 4 Regards Daniel -- View this message in context: http://samba.2283325.n4.nabble.com/List-open-connections-with-negotiated-dialect-tp4670389.html Sent from the Samba - General mailing list archive at Nabble.com.

(Hi, I tried sending this to ess-bugs, but got it bounced back: "user unknown". Hope this isn't too off-topic for ess-help. Scot) I'm using Xemacs 21.4, ess 5.1.24, on Windows 98 SE, with John Fox's configuration files: (http://socserv.mcmaster.ca/jfox/Books/Companion/ESS/index.html) and am getting the end-of-loop-timeout warning message I've seen reported to

Hello Jeremy, thanks a million for your help and interest in tracking this down! :-) Am 13.06.2017 um 18:36 schrieb Jeremy Allison: > Can you get comparitive wireshark traces for the two cases ? > > That would help discover what the bottleneck is. I am not at all a network guy, but I hope that - maybe with a little more help from your part once I have tried to do so in practice - I

Dear all, During a recent package submission, we were highlighted that some lines in our configure script didn't follow the correct syntax. The lines looked like this: x=$(($y/10)) We were indicated at the time that this is because the statement does not use Bourne shell syntax, which is absolutely true, and also that the manual warns about this, which is true again. So far everything

I increased the logging to 10 on the problem member server. Didn't see anything of interest. I did a packet capture on the PDC while typing " net rpc testjoin" from both the problem member server (4.4.14) and a working member server (4.4.13) e.g SMB: ----- SMB Header ----- SMB: SMB: CLIENT REQUEST SMB: Command code = 0x72 SMB:

What's the use case? On Oct 1, 2012, at 8:33 PM, Jun Koi <junkoi2004 at gmail.com> wrote: > currently, there is no (easy) way to set the AssemblerDialect. the > only method i am aware of is to set that via cl:opt. > > this patch fixes that by adding a public function > setAssemblerDialect() to class MCAsmInfo. > > Signed-off-by: Jun Koi <junkoi2004 at

For what it's worth, Autoconf does not assume that arithmetic expansion will be available. Instead, it emits the following shell code: if ( eval 'test $(( 1 + 1 )) = 2' ) 2>/dev/null; then eval 'func_arith () { func_arith_result=$(( $* )) }' else func_arith () { func_arith_result=`expr "$@"` } fi 2017-12-17 23:55 GMT+01:00 Rodrigo Tobar

Hi, I am enhancing the Samba Server on our product (VxWorks on the box) to support Long Name. So I started implementing the dialect "LM1.2X002" (first dialects that support Long Name, the current dialect that we support is PC Network Program). I have implemented the Negotiation, Tree Connect AndX and Open AndX command. When I try access the shared drive of our product, after the