search for: telecon

Displaying 9 results from an estimated 9 matches for "telecon".

Did you mean: telecom
2016 May 26
0
Adapting and open-sourcing PGI's Fortran frontend for LLVM
...formal review team made up of some key LLVM stakeholders to help smooth the way for a broader public rollout of the Flang code base and eventual integration. We’ll probably rely on Hal and others here to help us figure out who that group might be. My expectation is that it would involve a few WebEx/telecons on an as-needed basis (perhaps quarterly?) starting later this summer when code starts to move out of PGI’s internal systems and into a private github space. Stay tuned - we (both DOE and PGI) are keenly interested in doing what we can to make this successful. —Rob Neely, LLNL On 5/26/16, 11:57...
2016 May 26
2
Adapting and open-sourcing PGI's Fortran frontend for LLVM
...ade up of some key LLVM > stakeholders to help smooth the way for a broader public rollout of the > Flang code base and eventual integration. We’ll probably rely on Hal and > others here to help us figure out who that group might be. My expectation > is that it would involve a few WebEx/telecons on an as-needed basis > (perhaps quarterly?) starting later this summer when code starts to move > out of PGI’s internal systems and into a private github space. Stay tuned > - we (both DOE and PGI) are keenly interested in doing what we can to make > this successful. It seems to me t...
2016 May 26
0
Adapting and open-sourcing PGI's Fortran frontend for LLVM
...>> stakeholders to help smooth the way for a broader public rollout of the >> Flang code base and eventual integration. We’ll probably rely on Hal and >> others here to help us figure out who that group might be. My >>expectation >> is that it would involve a few WebEx/telecons on an as-needed basis >> (perhaps quarterly?) starting later this summer when code starts to move >> out of PGI’s internal systems and into a private github space. Stay >>tuned >> - we (both DOE and PGI) are keenly interested in doing what we can to >>make >> th...
2008 Jun 03
3
Stereo AEC, transition to Git
Hi, Two related news here. First, I've merged in support for stereo (or more channels) acoustic echo cancellation in mainline. The standard AEC remains the same, but I added a speex_echo_state_init_mc() call that takes the number of speakers and microphones. Now, one of the consequence of this new work is that by merging this work into the main tree, I had to do things in git that svn just
2016 May 27
1
Adapting and open-sourcing PGI's Fortran frontend for LLVM
...lders to help smooth the way for a broader public rollout of the >>> Flang code base and eventual integration. We’ll probably rely on Hal and >>> others here to help us figure out who that group might be. My >>>expectation >>> is that it would involve a few WebEx/telecons on an as-needed basis >>> (perhaps quarterly?) starting later this summer when code starts to move >>> out of PGI’s internal systems and into a private github space. Stay >>>tuned >>> - we (both DOE and PGI) are keenly interested in doing what we can to >>...
2016 May 26
3
Adapting and open-sourcing PGI's Fortran frontend for LLVM
Hi Chad - We have a functional Fortran compiler, with the PGI front-end bridged directly to LLVM, all of our Fortran runtime libraries integrated, and the Clang driver adapted for use with the Fortran compiler. We're working with a few users at DOE who are trying to compile big applications with a binary version of the compiler. Work is ongoing to migrate the source code into an LLVM-style
2015 Apr 08
4
[LLVMdev] [RFC] OpenMP offload infrastructure (iteration 2)
Hello everybody! To continue the original (http://article.gmane.org/gmane.comp.compilers.llvm.devel/75674) discussion of offload infrastructure I have an updated document with more details for your attention. The document is a consensus of the contributors representing a number of institutions: ANL, AMD, IBM, Intel and Texas Instruments. Our intent is to have a discussion and an approval from
2008 Jan 24
6
Your "favorite" Asterisk application.
Hi, all. I've done some Asterisk recelling, but recently got roped into a Sr. SysAdmin position. Our PBX is c. 1823, and -- well, as pretty much all circuit-based systems do, it sucks. It sucks to administer, moves suck... you know the drill. So, I'd love change to an Asterisk system. My boss, who loves to spend money for no particular reason, wants to go proprietary, though. So
2004 Jul 19
2
Affordable SIP Phone - Stiil a Myth?
...d $65/-(tentative) See the communication from D'Link below. Seshu Kanuri ----- Original Message ----- From: Mandar Pise (Netweb India Ltd) To: Abhijit M ( Voip Dept.) Sent: Monday, July 19, 2004 1:51 PM Subject: Re: D-link ( DPH-80 ),Sip Firmware Upgrade . Dear Mr. Abhijit, As per our teleconversation with you, I am forwarding you the sip server logs attached along with this email. Thank you, Regards, Mandar Pise "Abhijit M ( Voip Dept.)" <amalankar@dlink.co.in> wrote: Dear Raghvendra / Mandar , Forwarding to you the Dph-80 , upgrade of firmware which now works with...