From: Kaz Kojima <kkojima@rr.iij4u.or.jp>
To: oleg.endo@t-online.de
Cc: ysato@users.sourceforge.jp, gcc-patches@gcc.gnu.org
Subject: Re: sh-*-linux build failure
Date: Tue, 10 Mar 2015 11:06:00 -0000 [thread overview]
Message-ID: <20150310.200607.264927291.kkojima@rr.iij4u.or.jp> (raw)
In-Reply-To: <1425978340.31283.18.camel@yam-132-YW-E178-FTW>
Oleg Endo <oleg.endo@t-online.de> wrote:
> I think the same should be done in t-sh and in t-linux we could add the
> SH1 little endian exception, too ... just in case (see attached patch).
> I'm not sure whether TM_MULTILIB_EXCEPTIONS_CONFIG is needed in t-linux
> or not. Moreover, I don't understand why t-linux doesn't pick up
> MULTILIB_EXCEPTIONS from t-sh.... any ideas?
Your patch looks OK, though I guess that the current t-linux would
be enough. sh-linux compiler requires libc implementation and some
combinations aren't practical for t-linux in the first place.
Regards,
kaz
prev parent reply other threads:[~2015-03-10 11:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 8:14 Yoshinori Sato
2015-03-08 13:14 ` Oleg Endo
2015-03-08 14:14 ` Kaz Kojima
2015-03-09 8:38 ` Yoshinori Sato
2015-03-09 23:19 ` Kaz Kojima
2015-03-10 9:05 ` Oleg Endo
2015-03-10 11:06 ` Kaz Kojima [this message]
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=20150310.200607.264927291.kkojima@rr.iij4u.or.jp \
--to=kkojima@rr.iij4u.or.jp \
--cc=gcc-patches@gcc.gnu.org \
--cc=oleg.endo@t-online.de \
--cc=ysato@users.sourceforge.jp \
/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).