public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Oleg Endo <oleg.endo@t-online.de>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: Mike Stump <mikestump@comcast.net>,
	Kenneth Zadeck	 <zadeck@naturalbridge.com>,
	GCC Development <gcc@gcc.gnu.org>,
	gcc-patches	 <gcc-patches@gcc.gnu.org>,
	Nick Clifton <nickc@redhat.com>
Subject: Re: iq2000-elf: wide-int fallout (was: we are starting the wide int merge)
Date: Thu, 08 May 2014 23:02:00 -0000	[thread overview]
Message-ID: <1399590130.2892.2.camel@yam-132-YW-E178-FTW> (raw)
In-Reply-To: <20140508224838.GE1877@lug-owl.de>

On Fri, 2014-05-09 at 00:48 +0200, Jan-Benedict Glaw wrote:
> [...]
> 
> Just found this for iq2000:
> 
> g++ -c   -g -O2 -DIN_GCC  -DCROSS_DIRECTORY_STRUCTURE  -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -fno-common  -DHAVE_CONFIG_H -I. -I. -I/home/jbglaw/repos/gcc/gcc -I/home/jbglaw/repos/gcc/gcc/. -I/home/jbglaw/repos/gcc/gcc/../include -I/home/jbglaw/repos/gcc/gcc/../libcpp/include -I/opt/cfarm/gmp-latest/include -I/opt/cfarm/mpfr-latest/include -I/opt/cfarm/mpc-latest/include  -I/home/jbglaw/repos/gcc/gcc/../libdecnumber -I/home/jbglaw/repos/gcc/gcc/../libdecnumber/dpd -I../libdecnumber -I/home/jbglaw/repos/gcc/gcc/../libbacktrace    -o wide-int.o -MT wide-int.o -MMD -MP -MF ./.deps/wide-int.TPo /home/jbglaw/repos/gcc/gcc/wide-int.cc
> /home/jbglaw/repos/gcc/gcc/wide-int.cc:37:56: error: unable to emulate 'TI'
>  typedef unsigned int UTItype __attribute__ ((mode (TI)));
>                                                         ^
> make[1]: *** [wide-int.o] Error 1

I also just ran into that.  Seems to be a host issue.  This one seems to
fix it: http://gcc.gnu.org/ml/gcc-patches/2014-05/msg00527.html

Another wide-int merge fallout I ran into:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61120

Cheers,
Oleg

  reply	other threads:[~2014-05-08 23:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 15:19 we are starting the wide int merge Kenneth Zadeck
2014-05-06 19:21 ` Mike Stump
2014-05-06 21:17   ` Jan-Benedict Glaw
2014-05-06 22:54     ` Mike Stump
2014-05-06 23:03       ` Jan-Benedict Glaw
2014-05-06 23:16       ` Mike Stump
2014-05-06 23:53       ` Mike Stump
2014-05-06 22:59     ` Christophe Lyon
2014-05-07  7:48       ` Andreas Schwab
2014-05-07  9:40         ` Christophe Lyon
2014-05-07  7:07   ` Jan-Benedict Glaw
2014-05-07 10:27     ` Richard Sandiford
2014-05-08 22:48   ` iq2000-elf: wide-int fallout (was: we are starting the wide int merge) Jan-Benedict Glaw
2014-05-08 23:02     ` Oleg Endo [this message]
2014-05-08 23:06     ` UTItype fallout (was: wide-int fallout) Jan-Benedict Glaw
2014-05-10 19:42   ` we are starting the wide int merge Gerald Pfeifer
2014-05-16 16:56     ` Gerald Pfeifer
2014-05-17  8:33       ` Richard Sandiford
2014-05-19  3:08         ` Gerald Pfeifer
2014-05-19  6:47           ` Richard Sandiford
2014-05-19 17:33             ` Richard Sandiford

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=1399590130.2892.2.camel@yam-132-YW-E178-FTW \
    --to=oleg.endo@t-online.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=jbglaw@lug-owl.de \
    --cc=mikestump@comcast.net \
    --cc=nickc@redhat.com \
    --cc=zadeck@naturalbridge.com \
    /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).