From: Thiemo Seufer <ths@networkno.de>
To: wyb@topsec.com.cn
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: unmatched R_MIPS_HI16/LO16 on gcc 3.4.3
Date: Mon, 31 Jul 2006 09:34:31 +0100 [thread overview]
Message-ID: <20060731083431.GG15011@networkno.de> (raw)
In-Reply-To: <000f01c6b444$e1e820e0$0100000a@codingman>
wyb@topsec.com.cn wrote:
>
> Attachment is a testsuit. It costed me a week to make this testsuit.
FWIW, I can't reproduce the failure with Debian's gcc 3.4.6.
ISTR this bug was fixed in later 3.4.x versions.
> If I added -mno-explicit-relocs -mno-split-addresses to makefile, this bug
> disappeared. Is there any performance difference with and without these
> flags ?
-mno-explicit-relocs will degrade the efficiency of the compiler's
instruction scheduling since some macro expansions are left to the
assembler in that case. It will likely affect both execution speed
and code size.
Thiemo
prev parent reply other threads:[~2006-07-31 8:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 2:49 unmatched R_MIPS_HI16/LO16 on gcc 3.4.3 wyb
2006-07-25 2:49 ` wyb
2006-07-25 3:44 ` Ralf Baechle
2006-07-31 1:58 ` wyb
2006-07-31 1:58 ` wyb
2006-07-31 8:34 ` Thiemo Seufer [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=20060731083431.GG15011@networkno.de \
--to=ths@networkno.de \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=wyb@topsec.com.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.