search for: ptty

http://bugzilla.mindrot.org/show_bug.cgi?id=317 Summary: add header so ptty functions are found Product: Portable OpenSSH Version: -current Platform: Other OS/Version: FreeBSD Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: openssh-unix-dev at mindrot.org...

http://bugzilla.mindrot.org/show_bug.cgi?id=317 ------- Additional Comments From djm at mindrot.org 2002-09-10 22:28 ------- What is the failure if this header isn't added. I'd prefer to detect it in configure rather than use a platform-specific define ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=317 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From djm at mindrot.org 2002-10-21 10:50

Hrmm.... PromoteVectorOp doesn't seem to follow this at all. http://llvm.org/svn/llvm-project/llvm/trunk/lib/CodeGen/SelectionDAG/LegalizeVectorOps.cpp SDValue VectorLegalizer::PromoteVectorOp(SDValue Op) { // Vector "promotion" is basically just bitcasting and doing the operation // in a different type. For example, x86 promotes ISD::AND on v2i32 to // v1i64. EVT VT =

...the two ends > points on public networks and visible to one another? If not the reinvite > may be passing an internal (nat'ed) address to the other and the connection > will fail...just a though t38modem -tt -o /var/log/t38modem.log --no-h323 -u 91 --sip-listen udp\$127.0.0.1:6060 --ptty +/dev/ttyT380,+/dev/ttyT381 --route 'modem:.*=sip:<dn>@127.0.0.1:5061' --route 'sip:.*=modem:<dn>' --sip-register 91 at 127.0.0.1:5061,password I tried it with a global IP (instead of 127.0.0.1) - same behavior. The point is, that the receiving part, which initiates th...

Notice that PromoteVectorOp is called after the type legalization legalized all of the types in the program. It legalizes the *operations*, not the types. So, you should only see legal types (Legal types are types that fit into your registers). So, if your target has v2i32, I suspect that v4i8 is an illegal because it has a different size. -----Original Message----- From: Villmow, Micah

...ks and visible to one another? If not the reinvite >>> may be passing an internal (nat'ed) address to the other and the connection >>> will fail...just a though >> >> t38modem -tt -o /var/log/t38modem.log --no-h323 -u 91 --sip-listen >> udp\$127.0.0.1:6060 --ptty +/dev/ttyT380,+/dev/ttyT381 --route >> 'modem:.*=sip:<dn>@127.0.0.1:5061' --route 'sip:.*=modem:<dn>' >> --sip-register 91 at 127.0.0.1:5061,password >> >> I tried it with a global IP (instead of 127.0.0.1) - same behavior. >> >> The p...

v4i8 itself is a legal type, just not on the 'AND' operation. So there seems to be multiple problems here. 1) PromoteVectorOp doesn't handle the case where the types are not the same size, this occurs because #2 2) getTypeToPromoteTo doesn't actual check to see if the type it should promote to makes any sense. 3) PromoteVectorOp also doesn't handle the case where

If v4i8 is a legal type then getTypeToPromoteTo should return the pair v4i8 and 'legal'. This looks like the root of the problem. -----Original Message----- From: Villmow, Micah [mailto:Micah.Villmow at amd.com] Sent: Monday, July 30, 2012 22:10 To: Rotem, Nadav; Developers Mailing List Subject: RE: Vector promotion broken for <2 x [i8|i16]> v4i8 itself is a legal type, just not

...e > > >>> may be passing an internal (nat'ed) address to the other and the connection > > >>> will fail...just a though > > >> > > >> t38modem -tt -o /var/log/t38modem.log --no-h323 -u 91 --sip-listen > > >> udp\$127.0.0.1:6060 --ptty +/dev/ttyT380,+/dev/ttyT381 --route > > >> 'modem:.*=sip:<dn>@127.0.0.1:5061' --route 'sip:.*=modem:<dn>' > > >> --sip-register 91 at 127.0.0.1:5061,password > > >> > > >> I tried it with a global IP (instead of 127.0.0.1)...

I don't know how your target architecture looks like, but I suspect that <4 x i8> should not be legalized to <1 x i32>. I think that what you are seeing is that <4 x i8> is first split into <2 x i8>, and later promoted to <2 x i32>. At the moment different targets can only affect type-legalization by declaring different legal types. A number of us discussed the

Sorry, <4 x i8> should convert to a <1 x i32>. What currently is happening is that it is returning a <2 x i32> because <1 x i32> does not exist. Micah > -----Original Message----- > From: Rotem, Nadav [mailto:nadav.rotem at intel.com] > Sent: Monday, July 30, 2012 10:51 AM > To: Villmow, Micah; Developers Mailing List > Subject: RE: Vector promotion broken

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I've been enjoying the -t argument to ssh lately to force ptty allocation and I noticed there's no option in the config file that controls it. The O'Reilly ssh book specifies a ForcePTTYAllocation parameter so I've created a patch to openssh-5.2p1 which adds this functionality. Is this of interest to anyone? - -- Peter Wright Software Engineer Bel...

Does anyone know if it is possible to get Wine to map PTTYn devices to its serial ports? If so how? I'm running Wine on Mandriva 2007. I have a program which I want to run which will get its data from a serial port but this port is actually a pseudo serial port which is connected to a TCP/IP application! Stuart

...added a few large new things: 1. Key bindings with modifiers. This lets you from any of your scheme files/interactive prompt bind an arbitrary key + modifier to an arbitrary scheme function. So you can define new Compiz behaviors and shortcuts on the fly. 2. An interactive prompt. This sets up a PTTY and connects xterm to one end, and compiz-scheme to the other. You can then enter scheme expressions and have them evaluated by compiz-scheme on the fly. You can hit super+o to hide/show this. 3. An example startup file (compcomm/plugins/compiz-scheme/startup-example.scm on opencompositing.org GIT...

For various reasons, it suits our workplace to have a cygwin version of R. I am pretty sure that cygwin is still not a supported environment for R, but we have managed to compile R-2.5.1 under cygwin without too many dramas. Our procedure is described below. We still have a few problems compiling libraries without manually changing files from .so to .dll, but it seems ok. I was wondering

Hello! I'm still trying to get a working t.38 configuration w/ pjsip. I'm now able to send t.38 faxes to my own extension: hylafax -> t38modem -> extension -> extension -> t38modem -> hylafax. The fax is sent by t38modem. The receiving part of t38modem accepts the call, sends ReInvite for t.38 and things are working as expected. Now, let's do the nearly same

Hi Folks , As per https://libvirt.org/formatdomain.html#elementsConsole Regardless of the type, character devices can have an optional log file associated with them. Whether the lgging functionality is same as mapping device to file ? Whether libvirt xml syntax below both 1 and 2 are same ? 1) <serial type='pty'> <log

I'd like someone familiar with the R options initialization to comment on a difference of behavior within/without mpiexec I have a (.NET) application with embedded R that is proven to run in a single process: ./Sample1.exe on a Debian Linux with R 3.0.2 Running the same code with mpiexec, it fails at the R engine initialization: mpiexec -n 1 ./Sample1.exe Fatal error: you must

https://bugzilla.mindrot.org/show_bug.cgi?id=2548 Bug ID: 2548 Summary: Make pam_set_data/pam_get_data work with OpenSSH Product: Portable OpenSSH Version: 7.2p1 Hardware: Sparc OS: Solaris Status: NEW Severity: major Priority: P5 Component: PAM support Assignee: