From: David Daney <ddaney.cavm@gmail.com>
To: "Moore, Catherine" <Catherine_Moore@mentor.com>
Cc: "Rozycki, Maciej" <Maciej_Rozycki@mentor.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Richard Sandiford <rdsandiford@googlemail.com>
Subject: Re: Many warnings in MIPS port (Was: [PATCH] [MIPS] microMIPS gcc support)
Date: Sat, 13 Apr 2013 06:36:00 -0000 [thread overview]
Message-ID: <51685B72.8040902@gmail.com> (raw)
In-Reply-To: <FD3DCEAC5B03E9408544A1E416F11242F8F97F1A@NA-MBX-04.mgc.mentorg.com>
On 04/12/2013 10:55 AM, Moore, Catherine wrote:
>
>
>> -----Original Message-----
>> From: Maciej W. Rozycki [mailto:macro@codesourcery.com]
>> Sent: Friday, April 12, 2013 1:03 PM
>> To: David Daney
>> Cc: Moore, Catherine; gcc-patches@gcc.gnu.org; Richard Sandiford
>> Subject: Re: Many warnings in MIPS port (Was: [PATCH] [MIPS] microMIPS
>> gcc support)
>>
>> On Fri, 12 Apr 2013, David Daney wrote:
>>
>>> I just tried to bootstrap on o32 Debian. This system has binutils 2.20.1.
>>>
>>> Here is a sample of the resulting failure when building the libjava
>>> target
>>> libs:
>>> .
>>> .
>>> .
>>> /home/daney/gccsvn/build/./gcc/xgcc -
>> B/home/daney/gccsvn/build/./gcc/
>>> -B/usr/local/mips-unknown-linux-gnu/bin/
>>> -B/usr/local/mips-unknown-linux-gnu/lib/ -isystem
>>> /usr/local/mips-unknown-linux-gnu/include -isystem
>>> /usr/local/mips-unknown-linux-gnu/sys-include -DHAVE_CONFIG_H -I.
>>> -I../../../../trunk/libjava/libltdl -g -O2 -minterlink-mips16 -c
>>> ../../../../trunk/libjava/libltdl/ltdl.c -fPIC -DPIC -o .libs/ltdl.o
>>> /tmp/cckECtVQ.s: Assembler messages:
>>> /tmp/cckECtVQ.s:12: Warning: Tried to set unrecognized symbol:
>>> nomicromips
>>>
>>> /tmp/cckECtVQ.s:115: Warning: Tried to set unrecognized symbol:
>>> nomicromips
>>>
>>> /tmp/cckECtVQ.s:161: Warning: Tried to set unrecognized symbol:
>>> nomicromips .
>>> .
>>> .
>>>
>>> There are literally thousands and thousands of these warnings.
>>
>> Thanks for the report, I guess GCC should:
>>
>> 1. Detect in its `configure' script if GAS supports the pseudo-op and
>> refrain from producing it if it does not (or actually perhaps it may
>> never produce it by default as GAS defaults to the nomicromips mode
>> anyway); we have precedents for that already.
>
> Configure was modified as part of the micromips patch to detect support for the .set <no>micromips pseudo op.
> Do you have a configure log?
Here is the relevant fragment:
.
.
.
configure:25761: checking assembler for .micromips support
configure:25770: /usr/bin/as -o conftest.o conftest.s >&5
conftest.s: Assembler messages:
conftest.s:1: Warning: Tried to set unrecognized symbol: micromips
configure:25773: $? = 0
configure:25784: result: yes
.
.
.
Since it is a warning, it succeeds. I think you need to adjust the test
so that it fails if there is a warning.
>
>>
>
>
>
prev parent reply other threads:[~2013-04-12 19:07 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <FD3DCEAC5B03E9408544A1E416F1124211F9CC2E@NA-MBX-04.mgc.mentorg.com>
2012-07-19 18:51 ` FW: [PATCH] [MIPS] microMIPS gcc support Moore, Catherine
2012-07-20 0:46 ` Richard Sandiford
2013-01-22 20:23 ` Moore, Catherine
2013-01-22 20:27 ` Moore, Catherine
2013-01-23 20:05 ` Richard Sandiford
2013-01-26 3:52 ` Maciej W. Rozycki
2013-01-26 10:17 ` Richard Sandiford
2013-01-27 13:58 ` Maciej W. Rozycki
2013-01-28 10:14 ` Richard Sandiford
2013-02-12 19:00 ` Moore, Catherine
2013-02-13 11:43 ` Richard Sandiford
2013-02-19 16:31 ` Moore, Catherine
2013-02-19 18:25 ` Richard Sandiford
2013-02-19 22:27 ` Maciej W. Rozycki
2013-02-21 2:28 ` Moore, Catherine
2013-02-21 21:20 ` Richard Sandiford
2013-02-24 23:52 ` Moore, Catherine
2013-02-25 9:41 ` Richard Sandiford
2013-02-25 13:55 ` Moore, Catherine
2013-03-04 19:43 ` Moore, Catherine
2013-03-04 20:54 ` Richard Sandiford
2013-03-04 22:47 ` Moore, Catherine
2013-03-05 21:06 ` Richard Sandiford
2013-03-13 20:30 ` Moore, Catherine
2013-03-14 20:55 ` Richard Sandiford
2013-03-15 18:00 ` Moore, Catherine
2013-03-19 19:26 ` Richard Sandiford
2013-03-19 21:23 ` Moore, Catherine
2013-03-19 21:23 ` Richard Sandiford
2013-03-20 20:15 ` Moore, Catherine
2013-03-20 21:48 ` Richard Sandiford
2013-03-20 22:02 ` Moore, Catherine
2013-03-21 8:05 ` Richard Sandiford
2013-03-21 23:04 ` Moore, Catherine
2013-03-22 0:05 ` Richard Sandiford
2013-03-22 18:31 ` Moore, Catherine
2013-03-23 9:07 ` Richard Sandiford
2013-04-12 18:38 ` Many warnings in MIPS port (Was: [PATCH] [MIPS] microMIPS gcc support) David Daney
2013-04-12 20:35 ` Maciej W. Rozycki
2013-04-12 22:08 ` Moore, Catherine
2013-04-13 6:36 ` David Daney [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=51685B72.8040902@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=Catherine_Moore@mentor.com \
--cc=Maciej_Rozycki@mentor.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rdsandiford@googlemail.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).