* old binutils-2.13-msp.diff and binutils 2.19
@ 2008-11-22 13:55 Andrew Randrianasulu
2008-11-22 20:54 ` Thiemo Seufer
0 siblings, 1 reply; 2+ messages in thread
From: Andrew Randrianasulu @ 2008-11-22 13:55 UTC (permalink / raw)
To: linux-mips
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?
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: old binutils-2.13-msp.diff and binutils 2.19
2008-11-22 13:55 old binutils-2.13-msp.diff and binutils 2.19 Andrew Randrianasulu
@ 2008-11-22 20:54 ` Thiemo Seufer
0 siblings, 0 replies; 2+ messages in thread
From: Thiemo Seufer @ 2008-11-22 20:54 UTC (permalink / raw)
To: Andrew Randrianasulu; +Cc: linux-mips, binutils
Andrew Randrianasulu wrote:
> 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?]
Exactly that, their meaning is documented in include/opcode/mips.h
> 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?
Use binutils@sourceware.org
Thiemo
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2008-11-22 20:54 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-11-22 13:55 old binutils-2.13-msp.diff and binutils 2.19 Andrew Randrianasulu
2008-11-22 20:54 ` Thiemo Seufer
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox