Hi
lm32-rtems fails building C++ with this error:
configure: WARNING: decimal float is not supported for this target, ignored
checking whether fixed-point is supported... no
checking whether to use setjmp/longjmp exceptions... unknown
configure: error: unable to detect exception model
make[1]: *
> Ok, I will do a full build tonight with the testuite and take this "test
> $build = $target" out of the build. I can only do a x86_64 linux test,
> should I send the results to the list?
You obviously need to test on a configuration that exercises the path.
--
Eric Botcazou
On Wed, 2013-01-09 at 08:43 +, Luke A. Guest wrote:
> 1) The latest problem I'm having is that it fails to build
> libgnat-4.6.so, I've managed to track it down to the following code
> inside libada/configure:
>
> # Determine what to build for 'gnatlib'
> if test $build = $target \
>
On Wed, Jan 9, 2013 at 5:33 PM, Ondřej Bílka wrote:
> On Wed, Jan 09, 2013 at 05:12:06PM +0100, Marc Glisse wrote:
>> On Wed, 9 Jan 2013, Ondřej Bílka wrote:
>>
>> >gcc currently does not even optimize following fragment:
>> >
>> >int foo(){
>> > char *x=malloc(64);
>> > free(x);
>> >}
>>
>> Yes i
On Wed, 2013-01-09 at 09:57 +0100, Arnaud Charlet wrote:
> > 2) I also want to point out that inside
> > gcc/ada/gcc-interface/Makefile.in there are lines such as:
> >
> > GNATLIB_SHARED = gnatlib-shared-dual
> >
> > Is these relics?
>
> No, these are correct settings. If there's a mistake,
On Wed, Jan 09, 2013 at 05:12:06PM +0100, Marc Glisse wrote:
> On Wed, 9 Jan 2013, Ondřej Bílka wrote:
>
> >gcc currently does not even optimize following fragment:
> >
> >int foo(){
> > char *x=malloc(64);
> > free(x);
> >}
>
> Yes it does.
> (not that more optimizations aren't possible, but it
On Wed, 9 Jan 2013, Ondřej Bílka wrote:
gcc currently does not even optimize following fragment:
int foo(){
char *x=malloc(64);
free(x);
}
Yes it does.
(not that more optimizations aren't possible, but it does this one)
--
Marc Glisse
Hello,
gcc currently does not even optimize following fragment:
int foo(){
char *x=malloc(64);
free(x);
}
It should be possible to change malloc with small size and there is free
that dominates that malloc into alloca.
Also when size it is not known it could be (perhaps with profiling)
tur
> 1) The latest problem I'm having is that it fails to build
> libgnat-4.6.so, I've managed to track it down to the following code
> inside libada/configure:
>
> # Determine what to build for 'gnatlib'
> if test $build = $target \
>&& test ${enable_shared} = yes ; then
> # No
On Wed, Jan 09, 2013 at 08:43:11AM +, Luke A. Guest wrote:
> Hi,
>
> I'm trying to add GNAT to Yocto and still coming across problems. I have
> a number of questions about GNAT as a cross compiler, I know it wasn't
> designed as one within the GCC tree, but I think it needs to be capable
> of
Hi,
I'm trying to add GNAT to Yocto and still coming across problems. I have
a number of questions about GNAT as a cross compiler, I know it wasn't
designed as one within the GCC tree, but I think it needs to be capable
of building as one to match the other compilers.
1) The latest problem I'm ha
11 matches
Mail list logo
