public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kkojima at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/44531] [SuperH] Multilib configuration does not work as expected
Date: Sat, 19 Jun 2010 09:50:00 -0000 [thread overview]
Message-ID: <20100619095025.14874.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44531-19316@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from kkojima at gcc dot gnu dot org 2010-06-19 09:50 -------
I can't reproduce it on my i686-pc-linux-gnu host with
a similar configuration
/home/kkojima/kaz/xsh-elf-combined-450/combined/configure
--target=sh-unknown-elf --disable-libmudflap --disable-libssp --disable-libgomp
--with-gnu-as --with-gnu-ld --enable-languages=c --disable-shared --with-newlib
--disable-nls --prefix=/home/kkojima/kaz/xsh-elf-combined-450/install
--with-headers=yes --disable-gdbtk --with-mpfr=/opt2/i686-pc-linux-gnu
--with-gmp=/opt2/i686-pc-linux-gnu
--with-multilib-list=m4-single-only,m4-nofpu,m4 --with-endian=little
--with-cpu=m4-single-only
for vanilla gcc-4.5.0 under a usual combined tree setting.
It can be something configuration issue including a host
specific problem. My gcc/tm.h starts like as:
#ifndef GCC_TM_H
#define GCC_TM_H
#define TARGET_CPU_DEFAULT (SELECT_SH4_SINGLE_ONLY)
#ifndef SH_MULTILIB_CPU_DEFAULT
# define SH_MULTILIB_CPU_DEFAULT "m4-single-only"
#endif
#ifndef SUPPORT_SH4_SINGLE_ONLY
# define SUPPORT_SH4_SINGLE_ONLY 1
#endif
#ifndef SUPPORT_SH4_SINGLE_ONLY
# define SUPPORT_SH4_SINGLE_ONLY 1
#endif
#ifndef SUPPORT_SH4_NOFPU
# define SUPPORT_SH4_NOFPU 1
#endif
#ifndef SUPPORT_SH4
# define SUPPORT_SH4 1
#endif
Could you look at how your gcc/tm.h is generated?
--
kkojima at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kkojima at gcc dot gnu dot
| |org
Status|UNCONFIRMED |WAITING
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44531
next prev parent reply other threads:[~2010-06-19 9:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 2:57 [Bug target/44531] New: " ljsebald at gmail dot com
2010-06-19 9:50 ` kkojima at gcc dot gnu dot org [this message]
2010-06-19 15:58 ` [Bug target/44531] " ljsebald at gmail dot com
2010-06-20 10:57 ` [Bug target/44531] [4.5/4.6 Regression] [SH] Multilib configuration does not work as expected on darwin kkojima at gcc dot gnu dot org
2010-06-20 14:01 ` ljsebald at gmail dot com
2010-06-20 22:23 ` kkojima at gcc dot gnu dot org
2010-06-24 21:32 ` rguenth at gcc dot gnu dot org
2010-06-24 21:42 ` rguenth at gcc dot gnu dot org
2010-07-04 22:07 ` kkojima at gcc dot gnu dot org
2010-07-05 22:34 ` kkojima at gcc dot gnu dot org
2010-07-05 22:39 ` kkojima at gcc dot gnu dot org
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=20100619095025.14874.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).