[Bug target/44531] New: [SuperH] Multilib configuration does not work as expected

2010-06-13 Thread ljsebald at gmail dot com
When building a clean GCC 4.5.0 targeting sh-elf, the multilib configuration of
the compiler does not appear to work at all. For instance, building GCC 4.5.0
with the following set of configure flags:

../gcc-4.5.0/configure --target=sh-elf --prefix=/usr/local/dc2/sh-elf
--with-newlib --enable-languages=c --disable-libssp --disable-tls
--without-headers --disable-nls --with-multilib-list=m4-single-only,m4-nofpu,m4
--with-endian=little --with-cpu=m4-single-only

Results in a compiler that can only compile with -m4-single-only. -m4 and
-m4-nofpu do not work at all, even though they were explicitly specified in the
--with-multilib-list.

Attempting to specify -m4 results in the following error (similar for
-m4-nofpu):
cc1: error: command line option '-m4' is not supported by this configuration

Configuring GCC 4.4.4 with the same set of configure flags results in a
compiler that does support all of -m4, -m4-single-only, and -m4-nofpu (and
defaults to -m4-single-only, as expected).


-- 
   Summary: [SuperH] Multilib configuration does not work as
expected
   Product: gcc
   Version: 4.5.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: ljsebald at gmail dot com
 GCC build triplet: x86_64-apple-darwin10.3.1
  GCC host triplet: x86_64-apple-darwin10.3.1
GCC target triplet: sh-unknown-elf


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44531



[Bug target/44531] [SuperH] Multilib configuration does not work as expected

2010-06-19 Thread ljsebald at gmail dot com


--- Comment #2 from ljsebald at gmail dot com  2010-06-19 15:58 ---
Judging by what I see from my gcc/tm.h file, I'm guessing it might well be a
host-specific problem (I'm on x86_64-apple-darwin10.3.1). Here's the start of
my gcc/tm.h file:

#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

So, from the looks of it, it seems to be a Mac OS X/Darwin host specific issue.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44531



[Bug target/44531] [4.5/4.6 Regression] [SH] Multilib configuration does not work as expected on darwin

2010-06-20 Thread ljsebald at gmail dot com


--- Comment #4 from ljsebald at gmail dot com  2010-06-20 14:01 ---
The patch does indeed work, and everything builds as expected once patched.
Thanks.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44531