public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ken@msr.mei.co.jp
To: gcc-gnats@gcc.gnu.org
Subject: c/10117: Problem of arm-elf-gcc.
Date: Mon, 17 Mar 2003 02:46:00 -0000	[thread overview]
Message-ID: <20030317023743.6675.qmail@sources.redhat.com> (raw)


>Number:         10117
>Category:       c
>Synopsis:       Problem of arm-elf-gcc.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Mar 17 02:46:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     ken@msr.mei.co.jp
>Release:        gcc-3.1, gcc-3.2.2
>Organization:
>Environment:
RedHat Linux 7.2 and later, Solaris 2.6, Cygwin
>Description:
We used the following sources to build the gcc for ARM.
    gcc-3.1
    binutils-2.12.1
    newlib-1.10.0

After that, when the -march=armv5te option is given to the arm-elf-gcc, the arm-elf-gcc gives the -marmv5te option to the as(assembler).
However, the as will not accept the -marmv5te option.

We would probably think inconsistency of the options between the gcc and the as causes this problem.

The following is an execution log that shows the problem.


/usr/cygnus/arm-3.1/H-i686-pc-linux-gnulibc2.2/bin/arm-elf-gcc -v -c --march=armv5te test.c
Reading specs from /usr/cygnus/arm-3.1/H-i686-pc-linux-gnulibc2.2/lib/gcc-lib/arm-elf/3.1-030221/specs
Configured with: /home/ken/GNU/src/gcc-3.1/configure --enable-languages=c,c++ --with-included-gettext --enable-threads --target=arm-elf --with-newlib --with-cpu=arm9 --prefix=/usr/cygnus/arm-3.1 --exec-prefix=/usr/cygnus/arm-3.1/H-i686-pc-linux-gnulibc2.2
Thread model: single
gcc version 3.1-030221
 /usr/cygnus/arm-3.1/H-i686-pc-linux-gnulibc2.2/lib/gcc-lib/arm-elf/3.1-030221/cc1 -lang-c -v -D__GNUC__=3 -D__GNUC_MINOR__=1 -D__GNUC_PATCHLEVEL__=030221 -D__ELF__ -D__ELF__ -D__NO_INLINE__ -D__STDC_HOSTED__=1 -Acpu=arm -Amachine=arm -D__ARM_ARCH_5TE__ -D__APCS_32__ -D__ARMEL__ -D__ELF__ -D__USES_INITFINI__ -D__arm__
test.c -quiet -dumpbase test.c -march=armv5te -version -o /tmp/ccMZfi0O.s
GNU CPP version 3.1-030221 (cpplib) (ARM/ELF)
GNU C version 3.1-030221 (arm-elf)
        compiled by GNU C version 2.96 20000731 (Red Hat Linux 7.1 2.96-98).
ignoring nonexistent directory "/usr/cygnus/arm-3.1/H-i686-pc-linux-gnulibc2.2/arm-elf/sys-include"
#include "..." search starts here:
#include <...> search starts here:
 /usr/cygnus/arm-3.1/include
 /usr/cygnus/arm-3.1/H-i686-pc-linux-gnulibc2.2/lib/gcc-lib/arm-elf/3.1-030221/include
 /usr/cygnus/arm-3.1/H-i686-pc-linux-gnulibc2.2/arm-elf/include
End of search list.
 /usr/cygnus/arm-3.1/H-i686-pc-linux-gnulibc2.2/lib/gcc-lib/arm-elf/3.1-030221/../../../../arm-elf/bin/as -marmv5te -mno-fpu -o test.o /tmp/ccMZfi0O.s
Assembler messages:
Error: unrecognized option `-marmv5te'
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-03-17  2:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-17  2:46 ken [this message]
2003-03-20 10:23 rearnsha

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=20030317023743.6675.qmail@sources.redhat.com \
    --to=ken@msr.mei.co.jp \
    --cc=gcc-gnats@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).