search for: adacore

Displaying 15 results from an estimated 15 matches for "adacore".

Did you mean: acore
2012 Oct 02
2
Questions on converting to ConfBridge
I'm looking at what would be involved in converting from MeetMe to ConfBridge and there seems to be a lot of missing administrative things, but I hope I'm just missing it. We all know about the missing realtime linkage. That's a major nuisance, but can be worked around. More serious is that the CLI command to display users in a ConfBridge don't show the caller ID information, so
2015 Feb 14
2
[LLVMdev] Y.A.Project based on LLVM: ParaSail LLVM-Based compiler
...e ParaSail run-time support library. All ParaSail software is open source, and can be downloaded from http://parasail-lang.org. There is also a "blog" that documents the design and implementation of ParaSail: http://parasail-programming-language.blogspot.com Sincerely, -Tucker Taft AdaCore Lexington, MA
2009 Dec 14
1
meetme with review of the entered conference number
Hi there, I'm using asterisk meetme function like: exten => 9070,n,MeetMe(|dcM) and everything works pretty well. But I would like to add a review of the entered conference number before the user jumps into the conference. Somthing like: *:"Please enter the conference number followed by the hash key" (works) U: 123456# (works) *: "You are entering conference number
2009 Dec 17
2
[LLVMdev] updated code size comparison
Hi Paolo, > I would also avoid testcases using volatile. Smaller code on these testcases > is often a sign of miscompilation rather than optimization. For example, > http://embed.cs.utah.edu/embarrassing/src_harvested_dec_09/076389.c is > miscompiled on GCC 3.4 and SunCC 5.10. Yeah, there are definitely several examples where small code is generated by miscompilation, especially
2009 Dec 17
0
[LLVMdev] updated code size comparison
> However I would prefer to leave these testcases in, unless there is a > strong feeling that they are too distracting. They serve as poignant > little reminders about how easy it is to get volatile wrong... They skew the results in favor of the less careful compilers so they are more than simply distracting, they are unfair. -- Eric Botcazou
2009 Dec 17
1
[LLVMdev] updated code size comparison
On Thu, Dec 17, 2009 at 19:54, Eric Botcazou <ebotcazou at adacore.com> wrote: >> However I would prefer to leave these testcases in, unless there is a >> strong feeling that they are too distracting.  They serve as poignant >> little reminders about how easy it is to get volatile wrong... > > They skew the results in favor of the less c...
2013 Nov 15
0
[qemu-upstream-unstable test] 21952: regressions - FAIL
...redhat.com> Eric Johnson <ericj@mips.com> Erlon Cruz <erlon.cruz@br.flextronics.com> Evgeny Budilovsky <evgeny.budilovsky@ravellosystems.com> Evgeny Voevodin <e.voevodin@samsung.com> Evgeny Voevodin <evgenyvoevodin@gmail.com> Fabien Chouteau <chouteau@adacore.com> Fam Zheng <famz@redhat.com> Federico Simoncelli <fsimonce@redhat.com> Felipe Franciosi <felipe@paradoxo.org> Gabriel de Perthuis <g2p.code@gmail.com> Gabriel Kerneis <gabriel@kerneis.info> Gal Hammer <ghammer@redhat.com> Gerd Hoffmann <kr...
2013 Nov 14
0
[qemu-upstream-unstable test] 21930: regressions - FAIL
...redhat.com> Eric Johnson <ericj@mips.com> Erlon Cruz <erlon.cruz@br.flextronics.com> Evgeny Budilovsky <evgeny.budilovsky@ravellosystems.com> Evgeny Voevodin <e.voevodin@samsung.com> Evgeny Voevodin <evgenyvoevodin@gmail.com> Fabien Chouteau <chouteau@adacore.com> Fam Zheng <famz@redhat.com> Federico Simoncelli <fsimonce@redhat.com> Felipe Franciosi <felipe@paradoxo.org> Gabriel de Perthuis <g2p.code@gmail.com> Gabriel Kerneis <gabriel@kerneis.info> Gal Hammer <ghammer@redhat.com> Gerd Hoffmann <kr...
2013 Nov 18
0
[qemu-upstream-unstable test] 21993: regressions - FAIL
...redhat.com> Eric Johnson <ericj@mips.com> Erlon Cruz <erlon.cruz@br.flextronics.com> Evgeny Budilovsky <evgeny.budilovsky@ravellosystems.com> Evgeny Voevodin <e.voevodin@samsung.com> Evgeny Voevodin <evgenyvoevodin@gmail.com> Fabien Chouteau <chouteau@adacore.com> Fam Zheng <famz@redhat.com> Federico Simoncelli <fsimonce@redhat.com> Felipe Franciosi <felipe@paradoxo.org> Gabriel de Perthuis <g2p.code@gmail.com> Gabriel Kerneis <gabriel@kerneis.info> Gal Hammer <ghammer@redhat.com> Gerd Hoffmann <kr...
2009 Jul 21
1
[LLVMdev] x86 unwind support[MESSAGE NOT SCANNED]
On Mon, Jul 20, 2009 at 7:43 AM, Nick Johnson<nicholas.paul.johnson at gmail.com> wrote: > On Mon, Jul 20, 2009 at 10:09 AM, Mark Shannon<marks at dcs.gla.ac.uk> wrote: >> Andrew Haley wrote: >> If you can make your point without any references to any C/C++ specific >> features it might be more convincing ;) > > I did. ?Recall my mention of
2009 Aug 03
1
[LLVMdev] ACATS
Andre Tavares wrote: > Can someone tell me how to use ACATS? I have searched for documentation, > but found none. The ACATS is here: http://www.ada-auth.org/acats.html including various documentation. It stands for "Ada Conformity Assessment Test Suite". - Bob
2009 Aug 05
2
[LLVMdev] ACATS
Andr? Tavares wrote: > Thanks for the link Duff. You're welcome. > I downloaded ACATS, but could not run it on LLVM. Could not find any > instructions that could lead me to do so. Do you know how can do it? Compiler vendors are expected to write their own scripts, which is not a trivial task. The "B Tests" have deliberate errors, marked with "-- ERROR:"
2010 Mar 19
0
[LLVMdev] Idea for Google Summer Code : C Compiler for EFI Byte Code implement in LLVM
> How does EFI describe structures if the pointer size can change? This > shouldn't be a harder problem than C struct -> llvm struct. I assume > the EFI bytecode has some way to describe them. What is it? EFI describe structures almost like C. There are EBC instructions that have two immediates: one for 32bits pointers and one for 64bits pointers.
2010 Mar 31
0
[LLVMdev] Idea for Google Summer Code : C Compiler for EFI Byte Code implement in LLVM
On Mar 30, 2010, at 8:23 PM, Chris Lattner wrote: > > On Mar 30, 2010, at 10:31 AM, 琬菁楊 wrote: > >> What do you mean by "variable sized pointers"? What does: >> >> struct S {void *X; }; >> >> return for sizeof(struct S); ? >> >> I have surveyed the UEFI spec2.3. >> In my opinion, if the EBC VM is running on 32-bit
2010 Apr 06
0
[LLVMdev] Idea for Google Summer Code : C Compiler for EFI Byte Code implement in LLVM
On Apr 3, 2010, at 2:36 PM, Russell Wallace wrote: > On Fri, Apr 2, 2010 at 6:17 PM, Chris Lattner <clattner at apple.com> wrote: >> No, please don't. This is something we specifically do not want to support. The issue is not the parser, the issue is that struct field offsets are no longer constant in this model. > > What about declaring that pointers are always 64