public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: Simon Kallweit <simon.kallweit@intefo.ch>
Cc: ecos-patches@ecos.sourceware.org, Uwe Kindler <uwe_kindler@web.de>
Subject: Re: uSTL 1.4 update
Date: Mon, 28 Jun 2010 09:19:00 -0000	[thread overview]
Message-ID: <4C28692B.9090701@dallaway.org.uk> (raw)
In-Reply-To: <4C24BE22.4040405@intefo.ch>

Hi Simon

Simon Kallweit wrote:

> This patch will update uSTL to the newest 1.4 sources. Minor updates.

It seems that uSTL 1.4 has introduced a portability issue. Building the
tests for target "m5272c3" (for example):

> m68k-elf-gcc -c  -I/var/tmp/ustl-test/install/include -I/var/local/cvs/ecos/packages/language/cxx/ustl/current -I/var/local/cvs/ecos/packages/language/cxx/ustl/current/src -I/var/local/cvs/ecos/packages/language/cxx/ustl/current/tests -I. -I/var/local/cvs/ecos/packages/language/cxx/ustl/current/tests/ -finline-limit=7000 -Wall -Wpointer-arith  -Woverloaded-virtual -Wno-write-strings -mcpu=5272 -malign-int -g -O2 -ffunction-sections -fdata-sections -fno-rtti -fno-exceptions -fomit-frame-pointer -I/var/tmp/ustl-test/install/include/ustl -Wp,-MD,tests/bvt21.tmp -o tests/bvt21.o /var/local/cvs/ecos/packages/language/cxx/ustl/current/tests/bvt21.cpp
> /var/tmp/ustl-test/install/include/ustl/uutility.h: In function ‘void TestUtility()’:
> /var/tmp/ustl-test/install/include/ustl/uutility.h:350: error: impossible constraint in ‘asm’
> /var/tmp/ustl-test/install/include/ustl/uutility.h:350: error: impossible constraint in ‘asm’
> /var/tmp/ustl-test/install/include/ustl/uutility.h:350: error: impossible constraint in ‘asm’
> /var/tmp/ustl-test/install/include/ustl/uutility.h:350: error: impossible constraint in ‘asm’
> /var/tmp/ustl-test/install/include/ustl/uutility.h:350: error: impossible constraint in ‘asm’
> make[1]: *** [tests/bvt21.d] Error 1
> make[1]: Leaving directory `/var/tmp/ustl-test/language/cxx/ustl/current'
> make: *** [tests] Error 2

Are you able to provide a portable implementation of NextPow2() and
submit upstream?

Note also that your patch to include/ustl/uctrstrm.h prevents building
uSTL with "-fno-rtti" and should be omitted.

I'm copying Uwe Kindler to ensure he's aware of your contribution.

John Dallaway
eCos maintainers

  parent reply	other threads:[~2010-06-28  9:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-25 14:33 Simon Kallweit
2010-06-28  8:32 ` John Dallaway
2010-06-28  9:19 ` John Dallaway [this message]
2010-06-28  9:34   ` Simon Kallweit
2010-06-28 12:09     ` Simon Kallweit
2010-06-28 12:59       ` John Dallaway
2010-06-28 13:15         ` Simon Kallweit
2010-06-28 13:51           ` Sergei Gavrikov
2010-06-28 19:21             ` Sergei Gavrikov
2010-06-29  6:34               ` Sergei Gavrikov
2010-06-29  7:17                 ` John Dallaway
2010-06-29  7:23                   ` Simon Kallweit
2010-06-29  8:05       ` John Dallaway

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C28692B.9090701@dallaway.org.uk \
    --to=john@dallaway.org.uk \
    --cc=ecos-patches@ecos.sourceware.org \
    --cc=simon.kallweit@intefo.ch \
    --cc=uwe_kindler@web.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).