From: Andrew Randrianasulu <randrik_a@yahoo.com>
To: linux-mips@linux-mips.org
Subject: old binutils-2.13-msp.diff and binutils 2.19
Date: Sat, 22 Nov 2008 05:55:20 -0800 (PST) [thread overview]
Message-ID: <922652.90789.qm@web59801.mail.ac4.yahoo.com> (raw)
Hello. Sorry for asking this question - but while trying to move forward this patch, i faced with duplicated opcode in opcodes/mips-ops.c One "vmulu" was defined for Octeon, and one - for SGI O2 VICE coprocessor. After commenting out one from Octeon - my [patched] binutils finally was able to pass gcc-3.4.6 compilation. I saw some duplicates in this file, apart from my case, but i'm really unsure what to do in this case? Move patch parts around? But moving them in random order will break assembler, already learned this ....
Also I'm lost in gas/config/tc-mips.c Original patch was designed for (K, m, n) [i don't know what they mean .. some form of internal markers?] and i changed it for (+K, +m,+n). But i'm really lost in those big switches there. Right now my new code disabled, looking at old patch i must add some logic before yet another switch. Where is the best place for discussing this - here or on gcc mail list?
next reply other threads:[~2008-11-22 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 13:55 Andrew Randrianasulu [this message]
2008-11-22 20:54 ` old binutils-2.13-msp.diff and binutils 2.19 Thiemo Seufer
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=922652.90789.qm@web59801.mail.ac4.yahoo.com \
--to=randrik_a@yahoo.com \
--cc=linux-mips@linux-mips.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